date:20181130

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

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

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

Title:
  Login screen freeze on Intel Sandy Bridge i5-2500 GPU

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Since using Ubuntu 18.04.1 LTS on boot at the login screen the screen
  is frozen. I tried both gdm3 and lightdm login managers, with either I
  don't get into the system.

  I am using Intel 2nd generation (Sandy bridge) CPU with on-board GPU:
  HD Graphics 2000. I have an external 24" ASUS display connected with
  VGA (tried HDMI as well but same problem).

  UPDATE: I now use "nomodeset" since that is the only way to get into
  the system. However, graphics are low and there's only 1 screen
  resolution available (1280x1024) which does not suit my screen at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  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: Sun Sep 16 18:16:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd 2nd Generation Core Processor 
Family Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2018-09-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. H67M-UD2H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic 
root=/dev/mapper/ubuntu--vg-root ro nomodeset quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:

  dmi.bios.date: 11/12/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: H67M-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/12/2010:svnGigabyteTechnologyCo.,Ltd.:pnH67M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H67M-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94+git1809150630.283282~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1809160730.149768~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.1.0+git1809141934.80514b~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1809061934.25c9a2~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1807201019.ac8f7b~oibaf~b

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

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

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

2018-11-30 Thread chovy

I've tried everything. Nothing works. I originally booted into windows
once and then installed linux over it. I did not power off I only did a
reboot, some people are saying powering off from windows fixes sound on
linux, which makes me think its some bios setting, but I don't see
anything for sound settings in bios.

I no longer have windows so I can't boot into it.

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

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

  On Windows 10 everything works fine.

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

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

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

[Desktop-packages] [Bug 1789234] Re: Audio Popping when Headphones are plugged into Laptop

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

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

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

Title:
  Audio Popping when Headphones are plugged into Laptop

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  There seems to be a power saving issue where the sound card
  automatically turns off when not in use. When the laptop is off the
  charger, I plug in the headset into the headphone port. Then a sharp
  popping sound is sent through to my earbuds to my eardrums. You often
  have to manually disable the power saving to stop the issue, but this
  impacts the battery life of the laptop. I noticed this issue on Ubuntu
  MATE first and if has occurred on ALL versions of Ubuntu MATE I have
  used {16.04 onwards}. This issue also occurs on other Ubuntu distros.

  
  Here is the specific Audio hardware
  jgj@jgjbuntu-Inspiron-5547:~$ lspci | grep Audio
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)

  Hope this bug can be resolved.

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

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

[Desktop-packages] [Bug 1789234] Re: Audio Popping when Headphones are plugged into Laptop

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

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

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

Title:
  Audio Popping when Headphones are plugged into Laptop

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  There seems to be a power saving issue where the sound card
  automatically turns off when not in use. When the laptop is off the
  charger, I plug in the headset into the headphone port. Then a sharp
  popping sound is sent through to my earbuds to my eardrums. You often
  have to manually disable the power saving to stop the issue, but this
  impacts the battery life of the laptop. I noticed this issue on Ubuntu
  MATE first and if has occurred on ALL versions of Ubuntu MATE I have
  used {16.04 onwards}. This issue also occurs on other Ubuntu distros.

  
  Here is the specific Audio hardware
  jgj@jgjbuntu-Inspiron-5547:~$ lspci | grep Audio
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)

  Hope this bug can be resolved.

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

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

[Desktop-packages] [Bug 1793595] Re: Shell freezes, mostly when running chrome or editing text files.

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

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

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

Title:
  Shell freezes, mostly when running chrome or editing text files.

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Freezes randomly, mostly when running chrome or editing text files.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 20 16:35:29 2018
  DistUpgraded: 2018-08-28 16:25:11,641 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde GL [FirePro W4100] 
[1002:682c] (prog-if 00 [VGA controller])
 Subsystem: Dell Cape Verde GL [FirePro W4100] [1028:2b1e]
  InstallationDate: Installed on 2018-06-04 (108 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Dell Inc. Precision Tower 7810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=fc6e98f8-e80f-4e1c-ba61-e2234c5a9be5 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-08-28 (23 days ago)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A25
  dmi.board.name: 0KJCC5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA25:bd02/02/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Sep 20 16:27:01 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputPixArt Dell MS116 USB Optical Mouse MOUSE, id 8
   inputDell KB216 Wired Keyboard KEYBOARD, id 9
   inputDell KB216 Wired Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

2018-11-30 Thread Justin

** Changed in: mutter (Ubuntu Cosmic)
   Status: Triaged => Fix Released

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

Title:
  144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

Status in Mutter:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  Monitor is set to 144hz, but on Wayland it visually fails to go above
  60Hz. I have confirmed the monitor is running at 144Hz during the
  Wayland session, and that is also the setting in the Settings control
  panel.

  Using the additional NVidia drivers installed using the Ubuntu
  software control panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libwayland-bin (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 08:43:29 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1070] [1462:3301]
  InstallationDate: Installed on 2018-03-30 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed 
root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0610
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0610:bd01/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1753776] Re: Graphics corruption just before login animation to Xorg sessions (Intel gen9 GPUs only)

2018-11-30 Thread Bug Watch Updater

Launchpad has imported 23 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=105518.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-03-15T09:31:00+00:00 Daniel van Vugt wrote:

Xorg sessions are suddenly showing corruption upon login, briefly before
the shell starts up.

This seems to be related to the use of "-background none" by the DM. If
I remove "-background none" from the DM code then the corruption is
replaced by a less bad second or two of blackness.

This problem seems to have started when Mesa 18.0.0 was introduced to
Ubuntu 18.04. I can't seem to correlate it with anything else, and can't
relate it to a specific Xorg update.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/24


On 2018-03-15T09:34:21+00:00 Michel Dänzer wrote:

Please attach the corresponding Xorg log file.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/25


On 2018-03-15T09:37:24+00:00 Daniel van Vugt wrote:

There's a log in the downstream bug:
https://launchpad.net/bugs/1753776

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/27


On 2018-03-15T09:41:27+00:00 Michel Dänzer wrote:

FWIW, you're more likely to get action on this if you reassign to the
Mesa i965 driver.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/29


On 2018-03-15T09:42:48+00:00 Daniel van Vugt wrote:

I'm not sure if the problem is confined to the Mesa i965 driver. It is
possible.

I have verified that the corruption occurs with both Xorg drivers
though: modesetting and intel.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/30


On 2018-03-15T12:54:52+00:00 Timo Aaltonen wrote:

seems to be limited to gen9 (and up?), can't reproduce on BDW but can on
SKL/KBL/CFL

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/32


On 2018-03-16T01:24:54+00:00 Daniel van Vugt wrote:

I agree with that assessment so far. KBL is affected, but HAS is not.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/40


On 2018-03-16T01:42:34+00:00 Daniel van Vugt wrote:

KBL is affected, but HSW is not.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/41


On 2018-03-16T05:53:12+00:00 Daniel van Vugt wrote:

OK, if the problem is only Intel and only gen9 then I am less concerned.
But I will try to bisect this by next week. Certainly sounds like a Mesa
18 bug now.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/42


On 2018-03-19T01:40:58+00:00 Daniel van Vugt wrote:

I can now also confirm in more detail that:

HSW is not affected
BDW is not affected
SKL is affected
KBL is affected

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/46


On 2018-03-19T09:42:52+00:00 Daniel van Vugt wrote:

Bisected:

1efd73df39b39589d26f44d4927d2c65697bbe6e is the first bad commit
commit 1efd73df39b39589d26f44d4927d2c65697bbe6e
Author: Ben Widawsky 
Date:   Tue May 30 17:24:06 2017 +0530

i965: Advertise the CCS modifier

v2: Rename modifier to be more smart (Jason)

FINISHME: Use the kernel's final choice for the fb modifier

bwidawsk@norris2:~/intel-gfx/kmscube (modifiers $) 
~/scripts/measure_bandwidth.sh ./kmscube none
Read bandwidth: 603.91 MiB/s
Write bandwidth: 615.28 MiB/s
bwidawsk@norris2:~/intel-gfx/kmscube (modifiers $) 
~/scripts/measure_bandwidth.sh ./kmscube ytile
Read bandwidth: 571.13 MiB/s
Write bandwidth: 555.51 MiB/s
bwidawsk@norris2:~/intel-gfx/kmscube (modifiers $) 
~/scripts/measure_bandwidth.sh ./kmscube ccs
Read bandwidth: 259.34 MiB/s
Write bandwidth: 337.83 MiB/s

v2: Move all references to the new fourcc code(s) to this patch.
v3: Rebase, remove Yf_CCS (Daniel)

Signed-off-by: Ben Widawsky 
Signed-off-by: Jason Ekstrand 
Acked-by: Daniel Stone 
Reviewed-by: Chad Versace 

:04 04 1770769b4

[Desktop-packages] [Bug 1738164] Re: [snap] U2F doesn't work with yubikey

2018-11-30 Thread Daniel Aleksandersen

This isn’t mentioned in the bug so thought I’d just document it here:

* U2F must be enabled in about:config (security.webauth.u2f;true) before
it will work in Firefox.

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

Title:
  [snap] U2F doesn't work with yubikey

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  (initially reported by Daniel at https://forum.snapcraft.io/t/call-
  for-testing-chromium-62-0-3202-62/2569/50)

« U2F (Universal 2nd Factor) isn’t working when signing into my
  gmail account trying to use my yubikey. This is a USB device which
  IIRC chromium needs bidirectional communication with. »

  This requires investigation, but the yubikey I have is too old and
  doesn't support U2F.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

2018-11-30 Thread Bug Watch Updater

** Changed in: netpbm-free (Fedora)
   Status: Unknown => Fix Committed

** Changed in: netpbm-free (Fedora)
   Importance: Unknown => Undecided

-- 
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:
  Update to 2:10.78.05-0.1

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

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 cosmic

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 1804688]

2018-11-30 Thread Chad Cloman

*** Bug 120942 has been marked as a duplicate of this bug. ***

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

Title:
  libreoffice always crashes when I do this

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I reported the crash using ubuntu-bug and I think it uploaded the .crash but 
then did nothing after.
  Maybe it didn't upload.
  I put it here:
  
http://lockie.ca/libreoffice/_usr_lib_libreoffice_program_soffice.bin.1000.crash

  The way to crash it is to open this file:
  http://lockie.ca/libreoffice/convertible_sofas
  1. select the columns E to G
  2. press control-c to copy them
  3. observe the crash

  If you create a new calc document and try to copy 2 empty columns, it
  freezes but doesn't crash.

  Version: 6.1.2.1
  Build ID: 1:6.1.2-0ubuntu1.1
  CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
  Locale: en-CA (en_CA.UTF-8); Calc: group threaded

  $ apt-cache policy libreoffice
  libreoffice:
Installed: (none)
Candidate: 1:6.1.2-0ubuntu1.1
Version table:
   1:6.1.2-0ubuntu1.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/universe amd64 
Packages
   1:6.1.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Thu Nov 22 13:10:52 2018
  InstallationDate: Installed on 2018-11-15 (7 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1806145] [NEW] [SATELLITE PRO A50-C, Realtek ALC255, Speaker, Internal] Pulseaudio fails to detect card

2018-11-30 Thread Paul Hill

Public bug reported:

I have upgraded to the latest UBUNTU and now my laptop has no sound
output.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: pulseaudio 1:12.2-0ubuntu4
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: MATE
Date: Fri Nov 30 23:10:57 2018
InstallationDate: Installed on 2018-04-28 (216 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Title: [SATELLITE PRO A50-C, Realtek ALC255, Speaker, Internal] Pulseaudio 
fails to detect card
UpgradeStatus: Upgraded to cosmic on 2018-11-30 (0 days ago)
dmi.bios.date: 02/07/2017
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 7.70
dmi.board.asset.tag: 00
dmi.board.name: SATELLITE PRO A50-C
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion7.70:bd02/07/2017:svnTOSHIBA:pnSATELLITEPROA50-C:pvrPS575E-0U106EEN:rvnTOSHIBA:rnSATELLITEPROA50-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.family: 00
dmi.product.name: SATELLITE PRO A50-C
dmi.product.sku: PS575E
dmi.product.version: PS575E-0U106EEN
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug cosmic

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

Title:
  [SATELLITE PRO A50-C, Realtek ALC255, Speaker, Internal] Pulseaudio
  fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have upgraded to the latest UBUNTU and now my laptop has no sound
  output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: MATE
  Date: Fri Nov 30 23:10:57 2018
  InstallationDate: Installed on 2018-04-28 (216 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [SATELLITE PRO A50-C, Realtek ALC255, Speaker, Internal] Pulseaudio 
fails to detect card
  UpgradeStatus: Upgraded to cosmic on 2018-11-30 (0 days ago)
  dmi.bios.date: 02/07/2017
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 7.70
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE PRO A50-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion7.70:bd02/07/2017:svnTOSHIBA:pnSATELLITEPROA50-C:pvrPS575E-0U106EEN:rvnTOSHIBA:rnSATELLITEPROA50-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE PRO A50-C
  dmi.product.sku: PS575E
  dmi.product.version: PS575E-0U106EEN
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1806146] [NEW] /usr/bin/gnome-software:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_slice_alloc0:g_type_create_instance

2018-11-30 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.30.2-0ubuntu8, the problem page at 
https://errors.ubuntu.com/problem/348b9ddb7534cb63fe0dcac29ef8a00549bd3d3e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful bionic cosmic xenial yakkety zesty

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

Title:
  /usr/bin/gnome-
  
software:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_slice_alloc0:g_type_create_instance

Status in gnome-software package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

All that was needed for my Brother DCP-L2550DW was to 'apt purge' the
manually installed drivers:

$ sudo apt --auto-remove purge brscan4 dcpl2550dwpdrv


Then *BE SURE* to use the Brother installer script:  
linux-brprinter-installer-2.2.1-1.gz

(or whatever your current version is from the support.brother.com
website, etc.)

Follow the instructions from the Brother download site and during the
script installation to-the-letter(EXACTLY)!

*** CAVEAT:  use the printer I.P. addy if on a LAN and _NOT_ the auto-
detected mDNS addy if you have an AT&T Fiber residential gateway such as
mine(BGW210-700) which has a ".local" domain hard-coded in the DNS. This
effectively kills mDNS(Avahi) broadcasts and so I'm not able to connect
to the printer using that system.

CUPS Connection:lpd://192.168.1.220/BINARY_P1

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805247] Re: Onscreen Keyboard in Wayland cannot be summoned by swiping up on the screen

2018-11-30 Thread Juan Martinez

Confirmed same issue exists in Cosmic.  Reported to upstream
(https://gitlab.gnome.org/GNOME/gnome-shell/issues/831)

We don’t intend to deviate from Canonical’s defaults for OEM projects
unless necessary, but want to make sure that all issues are resolved
when the defaults "are" Wayland.

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

Title:
  Onscreen Keyboard in Wayland cannot be summoned by swiping up on the
  screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  -- Ubuntu 18.04 LTS
  -- gnome-shell 3.28.1-0ubuntu2

  When user is logged in using Wayland, swipe-up gesture cannot be used
  to summon the OSK.  Problem is non-existent on Xorg.

  This has been reproduced on multiple devices, leaving the user unable
  to use the OSK in many situations.

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

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

[Desktop-packages] [Bug 1802677] Re: Unmet Dependencies: gnome-settings-daemon

2018-11-30 Thread Jason Trupp

Found the following two entries had been added to /etc/apt/sources.list 
following automatic updates.
deb [trusted=yes] http://ftp.us.debian.org/debian experimental main
deb [trusted=yes] http://ftp.us.debian.org/debian sid main

Commented them out and performed apt update. Then purged the following packages:
apt purge gnome-settings-daemon gdm3 gnome-control-center gnome-initial-setup 
gnome-power-manager gnome-shell uatter ubuntu-desktop ubuntu-session

This removed these packages, then reinstalled all pre-existing packages.

Reboot returned system to normal functionality.

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

Title:
  Unmet Dependencies:  gnome-settings-daemon

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

Bug description:
  I get the following message from Software Updater:

  The Package System is Broken
  Check if you are using third party repositories. If so disable them, since 
they are a common source of problems.
  Furthermore run the following command in a Terminal: apt-get install -f
  Transaction failed: The package system is broken
   The following packages have unmet dependencies:

  gnome-settings-daemon: Depends: libgudev-1.0-0 (>= 146) but 1:232-2 is 
installed
 Depends: libnspr4 (>= 2:4.9-2~) but 2:4.18-1ubuntu1 is 
installed
 Depends: libnss3 (>= 2:3.13.4-2~) but 2:3.35-2ubuntu2 
is installed
 Depends: libxi6 (>= 2:1.2.99.4) but 2:1.7.9-1 is 
installed
 Depends: gnome-settings-daemon-schemas (= 
3.28.1-0ubuntu1.1) but 3.28.1-0ubuntu1 is installed

  I do not believe I am using third party repositories.  How can I fix
  my system?

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 10 15:10:57 2018
  InstallationDate: Installed on 2018-07-05 (127 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account

Ok, i've found that problem I was having had to do with IPv6
connectivity. Usually I disable the IPv6 connection because there are
certain PPAs (archive.ubuntu.com, for example) that for some odd reason,
never load, and they timeout on "sudo apt update". My network provider
has no problem with the IPv6 service, but Ubuntu, usually, cannot load a
PPA through IPv6. Because of that, I only allow IPv4 connectivity to be
active, and that was the issue. It seems that g-i-s and g-c-c only want
to connect via IPv6, even though it was disabled through the g-c-c. I
think that both should first check on how the network is setup up and
then load the webpages as determined by the settings. That is the issue.
I hope it gets fixed.

After I set IPv6 method to "Auto", both g-i-s and g-c-c loaded all log-
in pages without a problem.

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

Title:
  Not able to log in into Google Account, aswell as Microsoft account

Status in gnome-control-center package in Ubuntu:
  New
Status in gnome-initial-setup package in Ubuntu:
  Incomplete

Bug description:
  After the first boot up of Ubuntu 18.10, it invites me to log-in into
  several accounts, including Google and Microsoft accounts. After I
  log-in into Ubuntu One, my next step is to log in my Google Account,
  but the log-in page never loads, and when it does (after a couple of
  minutes), and I insert my log in credentials, it fails the log-in
  process, all of this happens with the Microsoft account too. The
  Ubuntu One account logs-in without a hitch, but the rest does not.

  1) Description:   Ubuntu 18.10
  Release:  18.10

  2) gnome-initial-setup:
Instalado: 3.30.0-1ubuntu3
Candidato: 3.30.0-1ubuntu3.1
Tabela de versão:
   3.30.0-1ubuntu3.1 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
   *** 3.30.0-1ubuntu3 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-initial-setup 3.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 27 11:12:31 2018
  ExecutablePath: /usr/lib/gnome-initial-setup/gnome-initial-setup
  InstallationDate: Installed on 2018-11-27 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1802677] Re: Unmet Dependencies: gnome-settings-daemon

2018-11-30 Thread Jason Trupp

If you reboot after receiving this error you will be unable to get back
into the system. Boot up will hang at "Started Update UTMP about System
Runlevel Changes. Alt-F2 allows you to switch to login prompt. However,
attempts to purge gnome and related dependencies or perform any updates
fail.

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

Title:
  Unmet Dependencies:  gnome-settings-daemon

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

Bug description:
  I get the following message from Software Updater:

  The Package System is Broken
  Check if you are using third party repositories. If so disable them, since 
they are a common source of problems.
  Furthermore run the following command in a Terminal: apt-get install -f
  Transaction failed: The package system is broken
   The following packages have unmet dependencies:

  gnome-settings-daemon: Depends: libgudev-1.0-0 (>= 146) but 1:232-2 is 
installed
 Depends: libnspr4 (>= 2:4.9-2~) but 2:4.18-1ubuntu1 is 
installed
 Depends: libnss3 (>= 2:3.13.4-2~) but 2:3.35-2ubuntu2 
is installed
 Depends: libxi6 (>= 2:1.2.99.4) but 2:1.7.9-1 is 
installed
 Depends: gnome-settings-daemon-schemas (= 
3.28.1-0ubuntu1.1) but 3.28.1-0ubuntu1 is installed

  I do not believe I am using third party repositories.  How can I fix
  my system?

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 10 15:10:57 2018
  InstallationDate: Installed on 2018-07-05 (127 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805039] Re: [SOLVED] Simple Scan segfaults when scanning on "Photo"(24-bit) quality.

See comment #3

** Changed in: simple-scan (Ubuntu)
   Status: New => Invalid

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

Title:
  [SOLVED]  Simple Scan segfaults when scanning on "Photo"(24-bit)
  quality.

Status in simple-scan package in Ubuntu:
  Invalid

Bug description:
  Simple Scan seg-faults when scanning at 24-bit(Photo) depth using the
  latest driver for my:

  Model:  Brother DCP-L2550DW
  Driver:  brscan4-0.4.6-1.amd64.deb

  
  $ grep -i scan /var/log/syslog

  
  Nov 25 12:42:45 CKR-1 systemd-udevd[496]: Invalid rule 
/etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules:9: unknown key 
'SYSFS{idVendor}'
  Nov 25 12:43:18 CKR-1 dbus-daemon[2323]: [session uid=1000 pid=2323] 
Activating via systemd: service name='org.freedesktop.portal.Desktop' 
unit='xdg-desktop-portal.service' requested by ':1.106' (uid=1000 pid=6089 
comm="simple-scan " label="unconfined")
  Nov 25 12:43:26 CKR-1 simple-scan: io/hpmud/model.c 532: no 
ther_dcp-l2550dw_series attributes found in 
/usr/share/hplip/data/models/models.dat
  Nov 25 12:43:26 CKR-1 simple-scan: io/hpmud/model.c 543: no 
ther_dcp-l2550dw_series attributes found in 
/usr/share/hplip/data/models/unreleased/unreleased.dat
  Nov 25 12:43:53 CKR-1 kernel: [  603.879672] scan-thread[6118]: segfault at 
3ec ip 7f9d432b29d2 sp 7f9d43bbd810 error 4 in 
libsane-brother4.so.1.0.7[7f9d4328d000+2e000]
  Nov 25 12:44:00 CKR-1 whoopsie-upload-all[6133]: Collecting info for 
/var/crash/_usr_bin_simple-scan.1000.crash...
  Nov 25 12:44:00 CKR-1 whoopsie-upload-all[6133]: Marking 
/var/crash/_usr_bin_simple-scan.1000.crash for whoopsie upload
  Nov 25 12:44:00 CKR-1 whoopsie[1825]: [12:44:00] Parsing 
/var/crash/_usr_bin_simple-scan.1000.crash.
  Nov 25 12:44:00 CKR-1 whoopsie[1825]: [12:44:00] Uploading 
/var/crash/_usr_bin_simple-scan.1000.crash.
  Nov 25 12:44:09 CKR-1 simple-scan: io/hpmud/model.c 532: no 
ther_dcp-l2550dw_series attributes found in 
/usr/share/hplip/data/models/models.dat
  Nov 25 12:44:09 CKR-1 simple-scan: io/hpmud/model.c 543: no 
ther_dcp-l2550dw_series attributes found in 
/usr/share/hplip/data/models/unreleased/unreleased.dat
  Nov 25 12:44:29 CKR-1 kernel: [  640.437150] scan-thread[7013]: segfault at 
3ec ip 7f7dc012c9d2 sp 7f7dab7fd810 error 4 in 
libsane-brother4.so.1.0.7[7f7dc0107000+2e000]
  <...snip>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: simple-scan 3.30.1.1-1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov 25 12:44:45 2018
  InstallationDate: Installed on 2018-11-23 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP HP Slimline Desktop PC 270-p0xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.35
  dmi.board.asset.tag: CNV7280FKD
  dmi.board.name: 82F2
  dmi.board.vendor: HP
  dmi.board.version: 00
  dmi.chassis.asset.tag: CNV7280FKD
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.35:bd11/01/2018:svnHP:pnHPSlimlineDesktopPC270-p0xx:pvr:rvnHP:rn82F2:rvr00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53311M HP Desktop
  dmi.product.name: HP Slimline Desktop PC 270-p0xx
  dmi.product.sku: Z5N91AA#ABA
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1805039] Re: Simple Scan seg-faults when scnanning on "Photo"(24-bit) quality.

***

SOLVED !!

***


All that was needed was to 'apt purge' the manually installed drivers:

$ sudo apt --auto-remove purge brscan4 dcpl2550dwpdrv


Then *BE SURE* to use the Brother installer script:  
linux-brprinter-installer-2.2.1-1.gz

(or whatever your current version is from the support.brother.com
website, etc.)

Follow the instructions from the Brother download site and during the
script installation to-the-letter(EXACTLY)!

*** CAVEAT:  use the printer I.P. addy if on a LAN and _NOT_ the auto-
detected mDNS addy if you have an AT&T Fiber residential gateway such as
mine(BGW210-700) which has a ".local" domain hard-coded in the DNS. This
effectively kills mDNS(Avahi) broadcasts and so I'm not able to connect
to the printer using that system.

i.e.:

CUPS Connection:lpd://192.168.1.220/BINARY_P1

in my case.


Good Luck !!


** Summary changed:

- Simple Scan seg-faults when scnanning on "Photo"(24-bit) quality.
+ [SOLVED]  Simple Scan seg-faults when scnanning on "Photo"(24-bit) quality.

** Summary changed:

- [SOLVED]  Simple Scan seg-faults when scnanning on "Photo"(24-bit) quality.
+ [SOLVED]  Simple Scan segfaults when scanning on "Photo"(24-bit) quality.

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

Title:
  [SOLVED]  Simple Scan segfaults when scanning on "Photo"(24-bit)
  quality.

Status in simple-scan package in Ubuntu:
  Invalid

Bug description:
  Simple Scan seg-faults when scanning at 24-bit(Photo) depth using the
  latest driver for my:

  Model:  Brother DCP-L2550DW
  Driver:  brscan4-0.4.6-1.amd64.deb

  
  $ grep -i scan /var/log/syslog

  
  Nov 25 12:42:45 CKR-1 systemd-udevd[496]: Invalid rule 
/etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules:9: unknown key 
'SYSFS{idVendor}'
  Nov 25 12:43:18 CKR-1 dbus-daemon[2323]: [session uid=1000 pid=2323] 
Activating via systemd: service name='org.freedesktop.portal.Desktop' 
unit='xdg-desktop-portal.service' requested by ':1.106' (uid=1000 pid=6089 
comm="simple-scan " label="unconfined")
  Nov 25 12:43:26 CKR-1 simple-scan: io/hpmud/model.c 532: no 
ther_dcp-l2550dw_series attributes found in 
/usr/share/hplip/data/models/models.dat
  Nov 25 12:43:26 CKR-1 simple-scan: io/hpmud/model.c 543: no 
ther_dcp-l2550dw_series attributes found in 
/usr/share/hplip/data/models/unreleased/unreleased.dat
  Nov 25 12:43:53 CKR-1 kernel: [  603.879672] scan-thread[6118]: segfault at 
3ec ip 7f9d432b29d2 sp 7f9d43bbd810 error 4 in 
libsane-brother4.so.1.0.7[7f9d4328d000+2e000]
  Nov 25 12:44:00 CKR-1 whoopsie-upload-all[6133]: Collecting info for 
/var/crash/_usr_bin_simple-scan.1000.crash...
  Nov 25 12:44:00 CKR-1 whoopsie-upload-all[6133]: Marking 
/var/crash/_usr_bin_simple-scan.1000.crash for whoopsie upload
  Nov 25 12:44:00 CKR-1 whoopsie[1825]: [12:44:00] Parsing 
/var/crash/_usr_bin_simple-scan.1000.crash.
  Nov 25 12:44:00 CKR-1 whoopsie[1825]: [12:44:00] Uploading 
/var/crash/_usr_bin_simple-scan.1000.crash.
  Nov 25 12:44:09 CKR-1 simple-scan: io/hpmud/model.c 532: no 
ther_dcp-l2550dw_series attributes found in 
/usr/share/hplip/data/models/models.dat
  Nov 25 12:44:09 CKR-1 simple-scan: io/hpmud/model.c 543: no 
ther_dcp-l2550dw_series attributes found in 
/usr/share/hplip/data/models/unreleased/unreleased.dat
  Nov 25 12:44:29 CKR-1 kernel: [  640.437150] scan-thread[7013]: segfault at 
3ec ip 7f7dc012c9d2 sp 7f7dab7fd810 error 4 in 
libsane-brother4.so.1.0.7[7f7dc0107000+2e000]
  <...snip>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: simple-scan 3.30.1.1-1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov 25 12:44:45 2018
  InstallationDate: Installed on 2018-11-23 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP HP Slimline Desktop PC 270-p0xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.35
  dmi.board.asset.tag: CNV7280FKD
  dmi.board.name: 82F2
  dmi.board.vendor: HP
  dmi.board.version: 00
  dmi.chassis.asset.tag: CNV7280FKD
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.35:bd11/01/2018:svnHP:pnHPSlimlineDesktopPC270-p0xx:pvr:rvnHP:rn82F2:rvr00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53311M HP Desktop
  dmi.product.name: HP Slimline Desktop PC 270-p0xx
  dmi.product.sku: Z5N91AA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
ht

[Desktop-packages] [Bug 1560286] Re: Evince displays pdf file fine, but prints colors inverted

2018-11-30 Thread florin

Found this Cairo edit, I have no idea if it is final or committed (some
one here might know):

https://gitlab.freedesktop.org/cairo/cairo/commit/bf597b89288b6271f56031d5a20bfaf59f146d4c

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

Title:
  Evince displays pdf file fine, but prints colors inverted

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  I have several pdf files that when opened by evince, they appear to be fine 
until I try to print them.  When I do, they print with the colors inverted (the 
printout looks like a photograph negative).  This color inversion also occurs 
when viewed in the print preview screen.  If I click on File > Properties, I 
get some information...
  Producer : Adobe Acrobat 15.10 Image Conversion Plug-in
  Creator : Adobe Acrobat 15.10
  ...
  Format : PDF-1.6
  ...

  I am running ubuntu 14.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 21 21:01:45 2016
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2012-07-24 (1336 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago)

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

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

[Desktop-packages] [Bug 1805039] Re: Simple Scan seg-faults when scnanning on "Photo"(24-bit) quality.

Output from simple-scan run in debug mode:


$ simple-scan -d
[+0.00s] DEBUG: simple-scan.vala:638: Starting Simple Scan 3.30.1.1, PID=29211

(simple-scan:29211): Gtk-WARNING **: 14:56:04.684: Failed to register client: 
GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register 
client
[+0.04s] DEBUG: app-window.vala:1715: Loading state from 
/home/chris/.cache/simple-scan/state
[+0.04s] DEBUG: app-window.vala:1672: Restoring window to 600x400 pixels
[+0.04s] DEBUG: app-window.vala:1676: Restoring window to maximized
[+0.04s] DEBUG: autosave-manager.vala:64: Loading autosave information
[+0.04s] DEBUG: autosave-manager.vala:259: Waiting to autosave...
[+0.07s] DEBUG: scanner.vala:1461: sane_init () -> SANE_STATUS_GOOD
[+0.07s] DEBUG: scanner.vala:1467: SANE version 1.0.27
[+0.07s] DEBUG: scanner.vala:1528: Requesting redetection of scan devices
[+0.07s] DEBUG: scanner.vala:806: Processing request
[+0.14s] DEBUG: autosave-manager.vala:281: Autosaving book information
[+0.18s] DEBUG: app-window.vala:1776: Saving state to 
/home/chris/.cache/simple-scan/state
[+8.26s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+8.26s] DEBUG: scanner.vala:353: Device: name="brother4:net1;dev0" 
vendor="Brother" model="*dcp-l2550dw" type="dcp-l2550dw"
[+9.48s] DEBUG: simple-scan.vala:455: Requesting scan at 300 dpi from device 
'brother4:net1;dev0'
[+9.48s] DEBUG: scanner.vala:1576: Scanner.scan ("brother4:net1;dev0", dpi=300, 
scan_mode=ScanMode.COLOR, depth=8, type=ScanType.SINGLE, paper_width=2159, 
paper_height=2794, brightness=0, contrast=0, delay=1ms)
[+9.48s] DEBUG: scanner.vala:806: Processing request
[+10.72s] DEBUG: scanner.vala:867: sane_open ("brother4:net1;dev0") -> 
SANE_STATUS_GOOD
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (0)
[+10.72s] DEBUG: scanner.vala:738: Option 0: name='(null)' title='Number of 
options' type=bool size=4 cap=soft-detect
[+10.72s] DEBUG: scanner.vala:741:   Description: Read-only option that 
specifies how many options a specific devices supports.
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (1)
[+10.72s] DEBUG: scanner.vala:738: Option 1: name='(null)' title='Mode' 
type=group size=4 cap=advanced
[+10.72s] DEBUG: scanner.vala:741:   Description: 
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (2)
[+10.72s] DEBUG: scanner.vala:738: Option 2: name='mode' title='Scan mode' 
type=string size=30 values=["Black & White", "Gray[Error Diffusion]", "True 
Gray", "24bit Color", "24bit Color[Fast]"] cap=soft-select,soft-detect
[+10.72s] DEBUG: scanner.vala:741:   Description: Select the scan mode
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (3)
[+10.72s] DEBUG: scanner.vala:738: Option 3: name='resolution' title='Scan 
resolution' type=int size=4 unit=dpi values=[100, 150, 200, 300, 400, 600, 
1200, 2400, 4800, 9600] cap=soft-select,soft-detect
[+10.72s] DEBUG: scanner.vala:741:   Description: Sets the resolution of the 
scanned image.
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (4)
[+10.72s] DEBUG: scanner.vala:738: Option 4: name='source' title='Scan source' 
type=string size=64 values=["FlatBed", "Automatic Document Feeder(left 
aligned)", "Automatic Document Feeder(left aligned,Duplex)", "Automatic 
Document Feeder(centrally aligned)", "Automatic Document Feeder(centrally 
aligned,Duplex)"] cap=soft-select,soft-detect
[+10.72s] DEBUG: scanner.vala:741:   Description: Selects the scan source (such 
as a document-feeder).
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (5)
[+10.72s] DEBUG: scanner.vala:738: Option 5: name='brightness' 
title='Brightness' type=fixed size=4 unit=percent min=-50.00, 
max=50.00, quant=65536 cap=soft-select,soft-detect,inactive
[+10.72s] DEBUG: scanner.vala:741:   Description: Controls the brightness of 
the acquired image.
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (6)
[+10.72s] DEBUG: scanner.vala:738: Option 6: name='contrast' title='Contrast' 
type=fixed size=4 unit=percent min=-50.00, max=50.00, quant=65536 
cap=soft-select,soft-detect,inactive
[+10.72s] DEBUG: scanner.vala:741:   Description: Controls the contrast of the 
acquired image.
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (7)
[+10.72s] DEBUG: scanner.vala:738: Option 7: name='(null)' title='Geometry' 
type=group size=4 cap=advanced
[+10.72s] DEBUG: scanner.vala:741:   Description: 
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (8)
[+10.72s] DEBUG: scanner.vala:738: Option 8: name='tl-x' title='Top-left x' 
type=fixed size=4 unit=mm min=0.00, max=215.84, quant=6553 
cap=soft-select,soft-detect
[+10.72s] DEBUG: scanner.vala:741:   Description: Top-left x position of scan 
area.
[+10.72s] DEBUG: scanner.vala:888: sane_get_option_descriptor (9)
[+10.72s] DEBUG: scanner.vala:738: Option 9: name='tl-y' title='Top-left y' 
type=fixed size=4 unit=mm min=0.00, max=355.51, quant=6553 
cap=

[Desktop-packages] [Bug 1787989] Re: adwaita icon them not found

2018-11-30 Thread Emmanuel

If the Inherits line in index.theme is changed to 
Inherits=Adwaita,gnome,hicolor,breeze

then kphotoalbum looks better but there's still some missing icons.

is there a way to check that all icons are available in a theme ?

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

Title:
  adwaita icon them not found

Status in adwaita-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  The installed version is xubuntu 18.04 fully updated

  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  $ apt-cache policy kphotoalbum
  kphotoalbum:
Installé : 5.3-1
Candidat : 5.3-1
   Table de version :
   *** 5.3-1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  When launched from shell, kphotoalbum indicate : 
  Icon theme "adwaita" not found.

  As a result, there's missing icons on kphotoalbum
  Expected result is to have all icons displayed on kphotoalbum

  The following package are installed :

  $ apt list --installed | grep adwaita
  adwaita-icon-theme/bionic,bionic,now 3.28.0-1ubuntu1 all  [installé]
  adwaita-icon-theme-full/bionic,bionic,now 3.28.0-1ubuntu1 all  [installé]
  adwaita-qt/bionic,now 1.0-2 amd64  [installé]

  $ apt list --installed | grep gtk
  adobe-flash-properties-gtk/bionic,now 1:20180814.1-0ubuntu0.18.04.2 amd64  
[installé, automatique]
  apport-gtk/bionic-security,bionic-security,now 2.20.9-0ubuntu7.1 all  
[installé]
  gir1.2-gtk-3.0/bionic,now 3.22.30-1ubuntu1 amd64  [installé]
  gir1.2-gtkclutter-1.0/bionic,now 1.8.4-3 amd64  [installé]
  gir1.2-gtksource-3.0/bionic,now 3.24.7-1 amd64  [installé, automatique]
  gir1.2-javascriptcoregtk-4.0/bionic-security,now 2.20.5-0ubuntu0.18.04.1 
amd64  [installé]
  greybird-gtk-theme/bionic,bionic,now 3.22.8-1 all  [installé]
  gstreamer1.0-gtk3/bionic,now 1.14.0-1ubuntu1 amd64  [installé, automatique]
  gtk-update-icon-cache/bionic,now 3.22.30-1ubuntu1 amd64  [installé]
  gtk2-engines-murrine/bionic,now 0.98.2-2ubuntu1 amd64  [installé]
  gtk2-engines-pixbuf/bionic,now 2.24.32-1ubuntu1 amd64  [installé]
  libcanberra-gtk3-0/bionic,now 0.30-5ubuntu1 amd64  [installé]
  libcanberra-gtk3-module/bionic,now 0.30-5ubuntu1 amd64  [installé]
  libclutter-gtk-1.0-0/bionic,now 1.8.4-3 amd64  [installé]
  libdbusmenu-gtk3-4/bionic,now 16.04.1+18.04.20171206-0ubuntu1 amd64  
[installé]
  libdbusmenu-gtk4/bionic,now 16.04.1+18.04.20171206-0ubuntu1 amd64  [installé]
  libgtk-3-0/bionic,now 3.22.30-1ubuntu1 amd64  [installé]
  libgtk-3-bin/bionic,now 3.22.30-1ubuntu1 amd64  [installé]
  libgtk-3-common/bionic,bionic,now 3.22.30-1ubuntu1 all  [installé]
  libgtk2-perl/bionic,now 2:1.24992-1build1 amd64  [installé, automatique]
  libgtk2.0-0/bionic,now 2.24.32-1ubuntu1 amd64  [installé]
  libgtk2.0-bin/bionic,now 2.24.32-1ubuntu1 amd64  [installé]
  libgtk2.0-common/bionic,bionic,now 2.24.32-1ubuntu1 all  [installé]
  libgtk3-perl/bionic,bionic,now 0.032-1 all  [installé]
  libgtkmm-2.4-1v5/bionic,now 1:2.24.5-2 amd64  [installé, automatique]
  libgtkmm-3.0-1v5/bionic,now 3.22.2-2 amd64  [installé]
  libgtksourceview-3.0-1/bionic,now 3.24.7-1 amd64  [installé]
  libgtksourceview-3.0-common/bionic,bionic,now 3.24.7-1 all  [installé]
  libgtkspell0/bionic,now 2.0.16-1.2 amd64  [installé]
  libjavascriptcoregtk-4.0-18/bionic-security,now 2.20.5-0ubuntu0.18.04.1 amd64 
 [installé]
  libreoffice-gtk3/bionic,now 1:6.0.3-0ubuntu1 amd64  [installé]
  libwebkit2gtk-4.0-37/bionic-security,now 2.20.5-0ubuntu0.18.04.1 amd64  
[installé]
  libwxgtk3.0-0v5/bionic,now 3.0.4+dfsg-3 amd64  [installé, automatique]
  lightdm-gtk-greeter/bionic,now 2.0.5-0ubuntu1 amd64  [installé]
  lightdm-gtk-greeter-settings/bionic,bionic,now 1.2.2-1 all  [installé]
  numix-gtk-theme/bionic,bionic,now 2.6.7-3 all  [installé]
  pinentry-gtk2/bionic,now 1.1.0-1 amd64  [installé]
  python-gtk2/bionic,now 2.24.0-5.1ubuntu2 amd64  [installé, automatique]
  python3-aptdaemon.gtk3widgets/bionic,bionic,now 1.1.1+bzr982-0ubuntu19 all  
[installé]
  qt5-gtk-platformtheme/bionic,now 5.9.5+dfsg-0ubuntu1 amd64  [installé, 
automatique]
  software-properties-gtk/bionic,bionic,now 0.96.24.32.1 all  [installé]
  transmission-gtk/bionic,now 2.92-3ubuntu2 amd64  [installé]
  ubuntu-release-upgrader-gtk/bionic,bionic,now 1:18.04.17 all  [installé]
  xdg-user-dirs-gtk/bionic,now 0.10-2 amd64  [installé]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1787989/+subscriptions

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

[Desktop-packages] [Bug 1806118] [NEW] graphics bug

2018-11-30 Thread mo2c

Public bug reported:

3d graphics rendered not created by hardware

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri Nov 30 21:29:18 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:1670]
InstallationDate: Installed on 2018-11-29 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:b721 Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 04f2:b52b Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X541UAK
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=402003c5-5857-4de0-8bcd-824a634ec153 ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X541UAK.301
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X541UAK
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.:bvrX541UAK.301:bd12/26/2016:svnASUSTeKCOMPUTERINC.:pnX541UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X541UAK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
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 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/1806118

Title:
  graphics bug

Status in xorg package in Ubuntu:
  New

Bug description:
  3d graphics rendered not created by hardware

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Nov 30 21:29:18 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:1670]
  InstallationDate: Installed on 2018-11-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b721 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 04f2:b52b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X541UAK
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=402003c5-5857-4de0-8bcd-824a634ec153 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541UAK.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541UAK
  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.:bvrX541UAK.301:bd12/26/2016:svnASUSTeKCOMPUTERINC.:pnX541UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.pro

[Desktop-packages] [Bug 1787989] Re: adwaita icon them not found

2018-11-30 Thread Emmanuel

Hi all,
I finally found a part of the problem.
In the file /usr/share/icons/elementary-xfce/index.theme
There's the line :
Inherits=adwaita,gnome,hicolor

if it's replaced by (notice a to A change in adwaita)
Inherits=Adwaita,gnome,hicolor

That's because the directory of Adwaita had a "A" not a "a"

kphotoalbum do not complain any more.
So part of the problem is on elementary-xfce theme

however, icons are still not displayed for "Events", "Media Type",
"Geolocalisation", and some other in settings menu...

To be continued.. any idea welcome

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

Title:
  adwaita icon them not found

Status in adwaita-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  The installed version is xubuntu 18.04 fully updated

  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  $ apt-cache policy kphotoalbum
  kphotoalbum:
Installé : 5.3-1
Candidat : 5.3-1
   Table de version :
   *** 5.3-1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  When launched from shell, kphotoalbum indicate : 
  Icon theme "adwaita" not found.

  As a result, there's missing icons on kphotoalbum
  Expected result is to have all icons displayed on kphotoalbum

  The following package are installed :

  $ apt list --installed | grep adwaita
  adwaita-icon-theme/bionic,bionic,now 3.28.0-1ubuntu1 all  [installé]
  adwaita-icon-theme-full/bionic,bionic,now 3.28.0-1ubuntu1 all  [installé]
  adwaita-qt/bionic,now 1.0-2 amd64  [installé]

  $ apt list --installed | grep gtk
  adobe-flash-properties-gtk/bionic,now 1:20180814.1-0ubuntu0.18.04.2 amd64  
[installé, automatique]
  apport-gtk/bionic-security,bionic-security,now 2.20.9-0ubuntu7.1 all  
[installé]
  gir1.2-gtk-3.0/bionic,now 3.22.30-1ubuntu1 amd64  [installé]
  gir1.2-gtkclutter-1.0/bionic,now 1.8.4-3 amd64  [installé]
  gir1.2-gtksource-3.0/bionic,now 3.24.7-1 amd64  [installé, automatique]
  gir1.2-javascriptcoregtk-4.0/bionic-security,now 2.20.5-0ubuntu0.18.04.1 
amd64  [installé]
  greybird-gtk-theme/bionic,bionic,now 3.22.8-1 all  [installé]
  gstreamer1.0-gtk3/bionic,now 1.14.0-1ubuntu1 amd64  [installé, automatique]
  gtk-update-icon-cache/bionic,now 3.22.30-1ubuntu1 amd64  [installé]
  gtk2-engines-murrine/bionic,now 0.98.2-2ubuntu1 amd64  [installé]
  gtk2-engines-pixbuf/bionic,now 2.24.32-1ubuntu1 amd64  [installé]
  libcanberra-gtk3-0/bionic,now 0.30-5ubuntu1 amd64  [installé]
  libcanberra-gtk3-module/bionic,now 0.30-5ubuntu1 amd64  [installé]
  libclutter-gtk-1.0-0/bionic,now 1.8.4-3 amd64  [installé]
  libdbusmenu-gtk3-4/bionic,now 16.04.1+18.04.20171206-0ubuntu1 amd64  
[installé]
  libdbusmenu-gtk4/bionic,now 16.04.1+18.04.20171206-0ubuntu1 amd64  [installé]
  libgtk-3-0/bionic,now 3.22.30-1ubuntu1 amd64  [installé]
  libgtk-3-bin/bionic,now 3.22.30-1ubuntu1 amd64  [installé]
  libgtk-3-common/bionic,bionic,now 3.22.30-1ubuntu1 all  [installé]
  libgtk2-perl/bionic,now 2:1.24992-1build1 amd64  [installé, automatique]
  libgtk2.0-0/bionic,now 2.24.32-1ubuntu1 amd64  [installé]
  libgtk2.0-bin/bionic,now 2.24.32-1ubuntu1 amd64  [installé]
  libgtk2.0-common/bionic,bionic,now 2.24.32-1ubuntu1 all  [installé]
  libgtk3-perl/bionic,bionic,now 0.032-1 all  [installé]
  libgtkmm-2.4-1v5/bionic,now 1:2.24.5-2 amd64  [installé, automatique]
  libgtkmm-3.0-1v5/bionic,now 3.22.2-2 amd64  [installé]
  libgtksourceview-3.0-1/bionic,now 3.24.7-1 amd64  [installé]
  libgtksourceview-3.0-common/bionic,bionic,now 3.24.7-1 all  [installé]
  libgtkspell0/bionic,now 2.0.16-1.2 amd64  [installé]
  libjavascriptcoregtk-4.0-18/bionic-security,now 2.20.5-0ubuntu0.18.04.1 amd64 
 [installé]
  libreoffice-gtk3/bionic,now 1:6.0.3-0ubuntu1 amd64  [installé]
  libwebkit2gtk-4.0-37/bionic-security,now 2.20.5-0ubuntu0.18.04.1 amd64  
[installé]
  libwxgtk3.0-0v5/bionic,now 3.0.4+dfsg-3 amd64  [installé, automatique]
  lightdm-gtk-greeter/bionic,now 2.0.5-0ubuntu1 amd64  [installé]
  lightdm-gtk-greeter-settings/bionic,bionic,now 1.2.2-1 all  [installé]
  numix-gtk-theme/bionic,bionic,now 2.6.7-3 all  [installé]
  pinentry-gtk2/bionic,now 1.1.0-1 amd64  [installé]
  python-gtk2/bionic,now 2.24.0-5.1ubuntu2 amd64  [installé, automatique]
  python3-aptdaemon.gtk3widgets/bionic,bionic,now 1.1.1+bzr982-0ubuntu19 all  
[installé]
  qt5-gtk-platformtheme/bionic,now 5.9.5+dfsg-0ubuntu1 amd64  [installé, 
automatique]
  software-properties-gtk/bionic,bionic,now 0.96.24.32.1 all  [installé]
  transmission-gtk/bionic,now 2.92-3ubuntu2 amd64  [installé]
  ubuntu-release-upgrader-gtk/bionic,bionic,now 1:18.04.17 all  [installé]
  xdg-user-dirs-gtk/bionic,now 0.10-2 amd64  [installé]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1787989/+subscriptions

-- 
Mailing list: htt

[Desktop-packages] [Bug 1560286] Re: Evince displays pdf file fine, but prints colors inverted

2018-11-30 Thread florin

This is page 7 printed as PDF, exactly as it gets out of the printer.

** Attachment added: "Aubert_Brumm_etal_2014_Sulawesi_Indonezia-pag-7+v2.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1560286/+attachment/5217756/+files/Aubert_Brumm_etal_2014_Sulawesi_Indonezia-pag-7+v2.pdf

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

Title:
  Evince displays pdf file fine, but prints colors inverted

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  I have several pdf files that when opened by evince, they appear to be fine 
until I try to print them.  When I do, they print with the colors inverted (the 
printout looks like a photograph negative).  This color inversion also occurs 
when viewed in the print preview screen.  If I click on File > Properties, I 
get some information...
  Producer : Adobe Acrobat 15.10 Image Conversion Plug-in
  Creator : Adobe Acrobat 15.10
  ...
  Format : PDF-1.6
  ...

  I am running ubuntu 14.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 21 21:01:45 2016
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2012-07-24 (1336 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago)

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

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

[Desktop-packages] [Bug 1560286] Re: Evince displays pdf file fine, but prints colors inverted

2018-11-30 Thread florin

I add a pdf I get this in Ubuntu 18.10. Printing page 7 (and on), images
look inverted. Only images, text is good. I printed as PDF and they turn
dark (inverted I guess). Then I printed as Postscript (.ps) and they
look fine, so a workaround would be to print files as postscript and
then print them on the paper, but it is not a real solution.

** Attachment added: "from page 7 images are printed inverted in this pdf"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1560286/+attachment/5217755/+files/Aubert_Brumm_etal_2014_Sulawesi_Indonezia-pag-7+.pdf

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

Title:
  Evince displays pdf file fine, but prints colors inverted

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  I have several pdf files that when opened by evince, they appear to be fine 
until I try to print them.  When I do, they print with the colors inverted (the 
printout looks like a photograph negative).  This color inversion also occurs 
when viewed in the print preview screen.  If I click on File > Properties, I 
get some information...
  Producer : Adobe Acrobat 15.10 Image Conversion Plug-in
  Creator : Adobe Acrobat 15.10
  ...
  Format : PDF-1.6
  ...

  I am running ubuntu 14.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 21 21:01:45 2016
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2012-07-24 (1336 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago)

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

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

[Desktop-packages] [Bug 1799205] Re: Ubuntu wayland sessions are not migrated to yaru

This bug was fixed in the package gnome-session - 3.30.1-1ubuntu1

---
gnome-session (3.30.1-1ubuntu1) disco; urgency=medium

  [ Iain Lane ]
  * Merge with Debian, remaining changes:
- debian/control.in:
  + Recommend session-migration
  + Move xwayland dependency to gnome-session and make gnome-session
Arch: any
  + Split gnome-startup-applications to a separate binary package so
that it can be uninstalled without breaking the system
  + Add unity-session
- Split ubuntu-session out of gnome-session.
- Add upstart user session and systemd user session:
  debian/data, debian/gnome-session-bin.user-session.upstart
- debian/gnome-session-bin.postinst, debian/gnome-session-bin.prerm:
   Moved registering gnome-session binary as a session manager to
   gnome-session-bin package
- Add gnome-session-wayland transitional package
- don't install gnome-mimeapps.list (installed by desktop-file-utils in
  Ubuntu):
  debian/gnome-session-common.dirs, gnome-session-common.install,
  gnome-session-common.maintscript, gnome-session-common.postinst
- debian/patches/103_kill_the_fail_whale.patch:
  + Kill the Fail Whale as it tends to be more annoying than helpful
- debian/patches/22_support_autostart_delay.patch:
  + Bugzilla patch to support adding a delay to autostart apps, using
a "X-GNOME-Autostart-Delay" key in the desktop file
- debian/patches/50_ubuntu_sessions.patch:
  + Add ubuntu session tweaks
- debian/patches/51_remove_session_saving_from_gui.patch:
  + Add GNOME_SESSION_SAVE environment variable for people wanting to
use the save session still, knowing that it can break your system
if used unwisely
- debian/patches/53_add_sessionmigration.patch:
  + launch session-migration if present at the start of the session.
This sync tool runns different session migration scripts that can be
provided in various desktop packages.
- debian/patches/95_dbus_request_shutdown.patch:
  + Add "RequestShutdown" and "RequestReboot" DBus methods to allow
other applications to shutdown or reboot the machine via the session
manager.
- debian/patches/ignore_gsettings_region.patch:
  + Ignore the "region" gsettings value - users' setting of LC_*
variables saved in ~/.pam_environment.
- debian/patches/revert_remove_gnome_session_properties.patch:
  + Don't merge translations into gnome-session-properties.desktop
  * debian/patches/50_ubuntu_sessions.patch:
- moved to debian/patches/ubuntu/ubuntu-sessions.patch (using gbp topic)
  * ubuntu/ignore_gsettings_region.patch: Refresh

  [ Marco Trevisan (Treviño) ]
  * debian/ubuntu-settings-migrate-to-defaults.18.10.0.py:
- renamed to ubuntu-settings-migrate-to-defaults.18.10.1.py
  + Also run in ubuntu-wayland desktop session (LP: #1799205)

gnome-session (3.30.1-1) unstable; urgency=medium

  * Team upload
  * New upstream release
  * Bump Standards-Version to 4.2.1
  * d/rules: Remove gnome-get-source.mk (please use uscan instead)
  * Set Rules-Requires-Root to no

gnome-session (3.30.0-2) unstable; urgency=medium

  * Team upload
  * Release to unstable
- d/gbp.conf, d/control: Set branch back to debian/master
- d/watch: Only watch for upstream stable (even-numbered) releases

gnome-session (3.30.0-1) experimental; urgency=medium

  * Team upload

  [ Iain Lane ]
  * debian/gbp.conf: Don't use patch numbers
  * d/p/debian/Revert-main-Remove-GNOME_DESKTOP_SESSION_ID-envvar.patch: Mark
as not-needed upstream

  [ Raphaël Hertzog ]
  * Update gnome-mimeapps.list for evince's renamed desktop file
(Closes: #908177)

  [ Simon McVittie ]
  * d/gbp.conf: Add standard post-import hook
  * New upstream release
  * d/copyright: Update

 -- Iain Lane   Fri, 30 Nov 2018 16:32:53 +

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

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

Title:
  Ubuntu wayland sessions are not migrated to yaru

Status in gnome-session package in Ubuntu:
  Fix Released

Bug description:
  [ Description ]

  Running ubuntu in wayland won't migrate to yaru

  [ Test case ]

  1. Run bionic with ubuntu wayland session
  2. Upgrade to cosmic
  3. Login (in wayland mode), default theme should be now Yaru

  [ Regression potential ]

  No migration is done to yaru at all in any environment

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

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

[Desktop-packages] [Bug 1802677] Re: Unmet Dependencies: gnome-settings-daemon

2018-11-30 Thread Jason Trupp

Affecting Ubuntu 18 since updates on 11/27. Update log file attached.

/opt/symas/share/man/man1$ uname -a
Linux launchpad.*.*** 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 
UTC 2018 x86_64 GNU/Linux

sudo apt-get install gnome-settings-daemon-schemas
Reading package lists... Done
Building dependency tree
Reading state information... Done
gnome-settings-daemon-schemas is already the newest version (3.28.1-0ubuntu1.1).
gnome-settings-daemon-schemas set to manually installed.
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 gnome-settings-daemon : Depends: gnome-settings-daemon-schemas (= 
3.28.1-0ubuntu1) but 3.28.1-0ubuntu1.1 is to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  greybird-gtk-theme grub-gfxpayload-lists iputils-arping libart-2.0-2 
libasn1-8-heimdal
  libfile-copy-recursive-perl libgcrypt20:i386 libgssapi3-heimdal 
libhcrypto4-heimdal
  libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal 
libkrb5-26-heimdal
  liblz4-1:i386 libpcre3:i386 libroken18-heimdal libselinux1:i386 libsysmetrics1
  libthunarx-2-0 libwind0-heimdal networkd-dispatcher python3-macaroonbakery 
python3-nacl
  python3-protobuf python3-pymacaroons python3-rfc3339 python3-tz thunar-data
  xubuntu-icon-theme zlib1g:i386
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  gnome-settings-daemon
The following packages will be upgraded:
  gnome-settings-daemon
1 upgraded, 0 newly installed, 0 to remove and 477 not upgraded.
1098 not fully installed or removed.
Need to get 0 B/856 kB of archives.
After this operation, 4,219 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 299204 files and directories currently installed.)
Preparing to unpack .../gnome-settings-daemon_3.30.1.2-1_amd64.deb ...
Unpacking gnome-settings-daemon (3.30.1.2-1) over (3.28.1-0ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/gnome-settings-daemon_3.30.1.2-1_amd64.deb (--unpack):
 trying to overwrite '/lib/udev/rules.d/61-gnome-settings-daemon-rfkill.rules', 
which is also in package gnome-settings-daemon-schemas 3.28.1-0ubuntu1.1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/gnome-settings-daemon_3.30.1.2-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

** Attachment added: "Update Log File"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1802677/+attachment/5217740/+files/dpkg.log

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

Title:
  Unmet Dependencies:  gnome-settings-daemon

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

Bug description:
  I get the following message from Software Updater:

  The Package System is Broken
  Check if you are using third party repositories. If so disable them, since 
they are a common source of problems.
  Furthermore run the following command in a Terminal: apt-get install -f
  Transaction failed: The package system is broken
   The following packages have unmet dependencies:

  gnome-settings-daemon: Depends: libgudev-1.0-0 (>= 146) but 1:232-2 is 
installed
 Depends: libnspr4 (>= 2:4.9-2~) but 2:4.18-1ubuntu1 is 
installed
 Depends: libnss3 (>= 2:3.13.4-2~) but 2:3.35-2ubuntu2 
is installed
 Depends: libxi6 (>= 2:1.2.99.4) but 2:1.7.9-1 is 
installed
 Depends: gnome-settings-daemon-schemas (= 
3.28.1-0ubuntu1.1) but 3.28.1-0ubuntu1 is installed

  I do not believe I am using third party repositories.  How can I fix
  my system?

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 10 15:10:57 2018
  InstallationDate: Installed on 2018-07-05 (127 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https:

[Desktop-packages] [Bug 461836] Re: Nautilus does not remember passwords to SMB shares in MS-Windows domain

2018-11-30 Thread Bug Watch Updater

** Changed in: gvfs
   Status: New => Expired

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

Title:
  Nautilus does not remember passwords to SMB shares in MS-Windows
  domain

Status in gvfs:
  Expired
Status in gvfs package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nautilus

  When opening an SMB share (using the URL smb://user@server/share),
  Nautilus pops up a password dialog with the fields "domain" (pre-
  filled with "WORKGROUP") and "password" and the standard "remember
  password" radio buttons.

  After filling in domain name and password and selecting "remember
  password forever", the share is mounted. If I now disconnect the share
  and try to reconnect it, the password dialog appears again - basically
  disregarding my request to remember the password.

  If I go into the passwords and encryption keys application (seahorse)
  and look for the SMB password, I can see it is stored correctly,
  including the correct domain name under the "details" tab.

  I believe the problem is that Nautilus does not know which domain to
  login under as the domain is not part of the SMB URL, and so fails to
  locate the correct stored password. If I omit the user part of the URL
  and if my local user name is not identical to the remote user name,
  then the password dialog would also include a user name entry which
  would probably also complicates things.

  I think that Nautilus should lookup all the keys that match the
  details provided in the URL (whether its just protocol and server or
  protocol, user and server) and if only one stored password is listed
  then use that automatically. If there are more then one then its a UI
  issue that has to be though out: show a list? show the password dialog
  with one password pre-populated?

  I also think that its a shame that nautilus does not store the share
  address in the keyring as people may want to provide different
  credentials for different shares on the same server, but that is a
  different report and one that does not interest me personally at this
  time.

  ProblemType: Bug
  Architecture: amd64
  Date: Tue Oct 27 12:59:30 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/nautilus
  Package: nautilus 1:2.28.0-0ubuntu7
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: nautilus
  Uname: Linux 2.6.31-14-generic x86_64

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

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

[Desktop-packages] [Bug 1802677] Re: Unmet Dependencies: gnome-settings-daemon

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

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

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

Title:
  Unmet Dependencies:  gnome-settings-daemon

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

Bug description:
  I get the following message from Software Updater:

  The Package System is Broken
  Check if you are using third party repositories. If so disable them, since 
they are a common source of problems.
  Furthermore run the following command in a Terminal: apt-get install -f
  Transaction failed: The package system is broken
   The following packages have unmet dependencies:

  gnome-settings-daemon: Depends: libgudev-1.0-0 (>= 146) but 1:232-2 is 
installed
 Depends: libnspr4 (>= 2:4.9-2~) but 2:4.18-1ubuntu1 is 
installed
 Depends: libnss3 (>= 2:3.13.4-2~) but 2:3.35-2ubuntu2 
is installed
 Depends: libxi6 (>= 2:1.2.99.4) but 2:1.7.9-1 is 
installed
 Depends: gnome-settings-daemon-schemas (= 
3.28.1-0ubuntu1.1) but 3.28.1-0ubuntu1 is installed

  I do not believe I am using third party repositories.  How can I fix
  my system?

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 10 15:10:57 2018
  InstallationDate: Installed on 2018-07-05 (127 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1794953] Re: GNOME Calculator snap has wrong theme in live session

2018-11-30 Thread Zygmunt Krynicki

** Changed in: snapd (Ubuntu)
 Assignee: Zygmunt Krynicki (zyga) => (unassigned)

** Changed in: snapd (Ubuntu Cosmic)
 Assignee: Zygmunt Krynicki (zyga) => (unassigned)

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

Title:
  GNOME Calculator snap has wrong theme in live session

Status in snapd:
  Fix Released
Status in gnome-calculator package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in gnome-calculator source package in Cosmic:
  Invalid
Status in snapd source package in Cosmic:
  Confirmed

Bug description:
  Running GNOME Calculator (or System Monitor, for example) runs the app
  with Adwaita theme instead of Yaru when in the live session.  This
  seems to resolve itself when used in the real session.

  Steps to reproduce:

  * Launch a live USB stick in a VM (note: you might need to use nomodeset 
until that is fixed)
  * Open any of the seeded snaps and note that the theme is wrong.

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

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

[Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

2018-11-30 Thread W-barath-hotmail

This bug has been around since 14.04 and persists in 18.04

This bug causes unexpected filesystem corruption
 - hit the power button to suspend the laptop and put it in your suitcase.  
Take a flight and find it dead and corrupt on arrival.

This bug causes lost work
  - Suspend the laptop, suspend fails, work you didn't save is lost because the 
system unexpectedly loses power.

This bug causes permanent degradation of laptop batteries
 - Power policy set to power off at 20% capacity to extend laptop battery.  
Fails, battery is drained until it is flat, resulting in permanent damage and 
reduced capacity.

This bug causes security violations
 - Suspend the laptop.  Suspend never happens.  Someone else comes and uses it 
because it never locked even though you hit the button.

These are serious issues.

The policy should be terminated immediately.  Its purpose was to prevent
lost work.  Instead, it is causing lost work, lost hardware stability,
lost security.

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

Title:
  Screen doesn't lock or go to sleep when certain Chrome tabs are open

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy gnome-session-bin
  gnome-session-bin:
    Installed: 3.18.1.2-1ubuntu1.16.04.1
    Candidate: 3.18.1.2-1ubuntu1.16.04.1
    Version table:
   *** 3.18.1.2-1ubuntu1.16.04.1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.1.2-1ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I'm using gnome-session-flashback

  What happens:
  The screen doesn't lock when having certain pages in Chrome tabs

  Expected:
  The screen should lock after the configured timeout in settings.

  I've been having this issue sice before 14.04, which I recently
  upgraded (fresh install) to 16.04.

  After fresh install, the screen would turn down and lock the computer
  after 10 minutes (or whatever time I setup). At one point it stopped
  working. The screen never shuts down unless I manually lock the
  session with CTRL-ALT-L.

  I've followed the steps in
  https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure

  The culprit seems to be that Chrome issues some suspend inhibitions
  through dbus when doing certain operations. Many people find this
  problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
  pretty sure that Chrome is doing something else of what i've found
  out.

  1) Gnome screen saver works correctly. I can trigger it manually with:
  $ gnome-screensaver-command -a

  2) Gnome screen saver never receives the "session idle" status
  callback.

  3) When Chrome is not running, I can manually inhibit the idle status:
  $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" 
--inhibit-only --inhibit idle:suspend
  Inhibiting until Ctrl+C is pressed...

  4) I can query the inhibitors:
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return 
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 
reply_serial=2
     array [
    object path "/org/gnome/SessionManager/Inhibitor1686"
     ]
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetAppId
  ('test',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetReason
  ('manual idle inhibit',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetFlags
  (uint32 12,)

  12=4(suspend) + 8(idle)

  5) When testing, I can inhibit for 70 seconds, idle timeout being 60
  (1 minute). After these 70 seconds pass, the screen locks.

  6) Regarding Chrome, this is the information I get when querying the 
inhibitor:
  GetAppId: ('/usr/bin/google-chrome-stable',)
  GetReason: ('Uploading data to 10.200.0.163',)
  GetFlags: (uint32 4,)

  The flags just inhibits suspend, not locking or entering powersaving
  mode.

  This inhibitor seems to stay for 10-15 seconds, then goes away for
  another 30-60 seconds. The screen NEVER locks when this tab is open.
  No matter the inhibitor is present or not.

  I'm not sure where to go on. If it's a Chrome bug it must be using
  other mechanisms to prevent the idle timeout. Any ideas on what to
  look for?

  Julian.

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

-- 
Mailing list: https://launchpad.ne

[Desktop-packages] [Bug 1806090] [NEW] package xdg-user-dirs 0.15-2ubuntu6 [modified: usr/share/locale/an/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/bs/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale

2018-11-30 Thread alessio

Public bug reported:

...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: xdg-user-dirs 0.15-2ubuntu6 [modified: 
usr/share/locale/an/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/bs/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/de/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/eu/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/gd/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/id/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/is/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/jv/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/kn/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/kw/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/mr/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/ne/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/nl/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/pl/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/si/LC_MESSAGES/xdg-user-dirs.mo]
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
Date: Fri Nov 30 18:04:04 2018
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu10
 libgcc1 1:6.0.1-0ubuntu1
ErrorMessage: il pacchetto xdg-user-dirs non è pronto per la configurazione  
impossibile configurarlo (stato corrente "half-installed")
InstallationDate: Installed on 2016-06-23 (890 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: xdg-user-dirs
Title: package xdg-user-dirs 0.15-2ubuntu6 [modified: 
usr/share/locale/an/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/bs/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/de/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/eu/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/gd/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/id/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/is/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/jv/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/kn/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/kw/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/mr/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/ne/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/nl/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/pl/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/si/LC_MESSAGES/xdg-user-dirs.mo] failed to install/upgrade: il 
pacchetto xdg-user-dirs non è pronto per la configurazione  impossibile 
configurarlo (stato corrente "half-installed")
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xdg-user-dirs (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package xdg-user-dirs 0.15-2ubuntu6 [modified:
  usr/share/locale/an/LC_MESSAGES/xdg-user-dirs.mo
  usr/share/locale/bs/LC_MESSAGES/xdg-user-dirs.mo
  usr/share/locale/de/LC_MESSAGES/xdg-user-dirs.mo
  usr/share/locale/eu/LC_MESSAGES/xdg-user-dirs.mo
  usr/share/locale/gd/LC_MESSAGES/xdg-user-dirs.mo
  usr/share/locale/id/LC_MESSAGES/xdg-user-dirs.mo
  usr/share/locale/is/LC_MESSAGES/xdg-user-dirs.mo
  usr/share/locale/jv/LC_MESSAGES/xdg-user-dirs.mo
  usr/share/locale/kn/LC_MESSAGES/xdg-user-dirs.mo
  usr/share/locale/kw/LC_MESSAGES/xdg-user-dirs.mo
  usr/share/locale/mr/LC_MESSAGES/xdg-user-dirs.mo
  usr/share/locale/ne/LC_MESSAGES/xdg-user-dirs.mo
  usr/share/locale/nl/LC_MESSAGES/xdg-user-dirs.mo
  usr/share/locale/pl/LC_MESSAGES/xdg-user-dirs.mo
  usr/share/locale/si/LC_MESSAGES/xdg-user-dirs.mo] failed to
  install/upgrade: il pacchetto xdg-user-dirs non è pronto per la
  configurazione  impossibile configurarlo (stato corrente "half-
  installed")

Status in xdg-user-dirs package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: xdg-user-dirs 0.15-2ubuntu6 [modified: 
usr/share/locale/an/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/bs/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/de/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/eu/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/gd/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/id/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/is/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/jv/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/kn/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/kw/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/mr/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/ne/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/nl/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/pl/LC_MESSAGES/xdg-user-dirs.mo 
usr/share/locale/si/LC_MESSAGES/xdg-user-dirs.mo]
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  Date: Fri Nov 30 18:04:04 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:

[Desktop-packages] [Bug 1806080] [NEW] [snap] Chromium snap crashes when trying to access fs

2018-11-30 Thread Tejeev Patel

Public bug reported:

When I attempt to upload or save on certain pages it crashes the browser.  Some 
examples below.
Does not happen on Google Drive.  Looks like it's trying to query the fs and 
dies when it can't.


No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.5 LTS
Release:16.04
Codename:   xenial
Kernel: 4.15.0-39-generic
Chromium:   Version 70.0.3538.110 (Official Build) snap (64-bit)


# Right click on blank page "save as"
Nov 30 16:31:00 $HOSTNAME kernel: [35208.515968] audit: type=1400 
audit(1543595460.939:151): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/etc/fstab" pid=30734 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

# Restart browser
Nov 30 16:31:04 $HOSTNAME dbus[1899]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/freedesktop/secrets" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name="org.freedesktop.secrets" pid=32093 label="snap.chromium.chromium" 
peer_pid=1823 peer_label="unconfined"
Nov 30 16:31:04 $HOSTNAME kernel: [35212.081247] audit: type=1107 
audit(1543595464.507:152): pid=1384 uid=106 auid=4294967295 ses=4294967295 
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=31991 label="snap.chromium.chromium" 
peer_pid=24826 peer_label="unconfined"
Nov 30 16:31:05 $HOSTNAME kernel: [35213.238692] audit: type=1400 
audit(1543595465.663:153): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c99:0" pid=31991 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Nov 30 16:31:05 $HOSTNAME kernel: [35213.274048] audit: type=1400 
audit(1543595465.699:154): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c6:0" pid=31991 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

# Right click on blank page "save as" #2
Nov 30 16:31:08 $HOSTNAME kernel: [35216.557849] audit: type=1400 
audit(1543595468.983:155): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/etc/fstab" pid=31991 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

# Restart browser
Nov 30 16:31:13 $HOSTNAME dbus[1899]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/freedesktop/secrets" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name="org.freedesktop.secrets" pid=32646 label="snap.chromium.chromium" 
peer_pid=1823 peer_label="unconfined"
Nov 30 16:31:14 $HOSTNAME kernel: [35221.656759] audit: type=1107 
audit(1543595474.083:156): pid=1384 uid=106 auid=4294967295 ses=4294967295 
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=32544 label="snap.chromium.chromium" 
peer_pid=24826 peer_label="unconfined"
Nov 30 16:31:23 $HOSTNAME kernel: [35230.641856] audit: type=1400 
audit(1543595483.067:157): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c99:0" pid=32544 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Nov 30 16:31:23 $HOSTNAME kernel: [35230.660955] audit: type=1400 
audit(1543595483.087:158): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c6:0" pid=32544 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0


# Upload to Salesforce case #2
Nov 30 16:31:46 $HOSTNAME kernel: [35253.816946] audit: type=1400 
audit(1543595506.243:159): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/etc/fstab" pid=32544 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

# Restart browser
Nov 30 16:31:56 $HOSTNAME dbus[1899]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/freedesktop/secrets" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name="org.freedesktop.secrets" pid=938 label="snap.chromium.chromium" 
peer_pid=1823 peer_label="unconfined"
Nov 30 16:31:56 $HOSTNAME kernel: [35264.509009] audit: type=1107 
audit(1543595516.935:160): pid=1384 uid=106 auid=4294967295 ses=4294967295 
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=835 label="snap.chromium.chromium" 
peer_pid=24826 peer_label="unconfined"
Nov 30 16:31:58 $HOSTNAME kernel: [35265.833723] audit: type=1400 
audit(1543595518.259:161): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c99:0" pid=835 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Nov 30 16:31:58 $HOSTNAME kernel: [35265.863889

[Desktop-packages] [Bug 1805438] Re: Print settings present two distinct interfaces for adding printers

2018-11-30 Thread Casey

Yes.

grep lpadmin /etc/group

lpadmin:x:116:casey

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

Title:
Print settings present two distinct interfaces for adding printers

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

Bug description:
1. Running stock 18.04.1
2. gnome-control-center 3.28.2-0ubuntu0.18.04.2

As shown in the first screenshot below, the print settings panel shows
an "Add..." in the headerbar as well as "Add a printer..." and
"Additional printer settings" in the main area.

The first two buttons are highlighted and would naturally seem to be
the first options to try, but they didn't actually work. While I was
able to browse the list of printers attached to the print server,
attempting to actually add the printer ended in an uninformative error
message as shown in the second screenshot.

On the other hand, "Additional printer settings" launches the old
system-config-printer utility which did succeed in adding my desired
printer.

It is not at all obvious without trial and error which option one
should choose to add a new printer.

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

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

[Desktop-packages] [Bug 1755305] Re: .xsession-errors filled with entries

2018-11-30 Thread Gabor

18.04.1 LTS (Bionic Beaver) 64-bit
Confirm

The first thing I did is to install unity-desktop (not sure the problem
existed earlier)

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

Title:
  .xsession-errors filled with entries

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

Bug description:
  I hope I am in the right place for this. My .xsession-errors file is
  filled with entries in the following format, in that order/sequence,
  over and over and continuously:

  (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion
  'GTK_IS_WIDGET (widget)' failed

  (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion
  'GTK_IS_WIDGET (widget)' failed

  (nm-applet:1839): Gtk-WARNING **: Can't set a parent on widget which
  has a parent

  Ubuntu MATE 17.10

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

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

[Desktop-packages] [Bug 1805438] Re: Print settings present two distinct interfaces for adding printers

2018-11-30 Thread Till Kamppeter

Is your user account in the lpadmin group in /etc/group (this is default
for the first user created during installation)?

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

Title:
  Print settings present two distinct interfaces for adding printers

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

Bug description:
  1. Running stock 18.04.1
  2. gnome-control-center 3.28.2-0ubuntu0.18.04.2

  As shown in the first screenshot below, the print settings panel shows
  an "Add..." in the headerbar as well as "Add a printer..." and
  "Additional printer settings" in the main area.

  The first two buttons are highlighted and would naturally seem to be
  the first options to try, but they didn't actually work. While I was
  able to browse the list of printers attached to the print server,
  attempting to actually add the printer ended in an uninformative error
  message as shown in the second screenshot.

  On the other hand, "Additional printer settings" launches the old
  system-config-printer utility which did succeed in adding my desired
  printer.

  It is not at all obvious without trial and error which option one
  should choose to add a new printer.

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

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

[Desktop-packages] [Bug 1806074] [NEW] package libpolkit-backend-1-0:i386 0.105-14.1ubuntu0.1 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw

2018-11-30 Thread Niek Houtman

Public bug reported:

After remove and after that installing Nautilus

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpolkit-backend-1-0:i386 0.105-14.1ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
AptOrdering:
 libpolkit-backend-1-0: Configure
 NULL: ConfigurePending
Architecture: i386
Date: Fri Nov 30 16:16:54 2018
DpkgTerminalLog:
 dpkg: fout bij verwerken van pakket libpolkit-backend-1-0:i386 (--configure):
  pakket verkeert in een heel slechte en inconsistente staat; u zou het
  opnieuw moeten installeren alvorens het te configureren.
ErrorMessage: pakket verkeert in een heel slechte en inconsistente staat; u zou 
het  opnieuw moeten installeren alvorens het te configureren.
InstallationDate: Installed on 2017-04-20 (588 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.29
SourcePackage: policykit-1
Title: package libpolkit-backend-1-0:i386 0.105-14.1ubuntu0.1 failed to 
install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u 
zou het  opnieuw moeten installeren alvorens het te configureren.
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package libpolkit-backend-1-0:i386 0.105-14.1ubuntu0.1 failed to
  install/upgrade: pakket verkeert in een heel slechte en inconsistente
  staat; u zou het  opnieuw moeten installeren alvorens het te
  configureren.

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  After remove and after that installing Nautilus

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpolkit-backend-1-0:i386 0.105-14.1ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   libpolkit-backend-1-0: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Fri Nov 30 16:16:54 2018
  DpkgTerminalLog:
   dpkg: fout bij verwerken van pakket libpolkit-backend-1-0:i386 (--configure):
pakket verkeert in een heel slechte en inconsistente staat; u zou het
opnieuw moeten installeren alvorens het te configureren.
  ErrorMessage: pakket verkeert in een heel slechte en inconsistente staat; u 
zou het  opnieuw moeten installeren alvorens het te configureren.
  InstallationDate: Installed on 2017-04-20 (588 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29
  SourcePackage: policykit-1
  Title: package libpolkit-backend-1-0:i386 0.105-14.1ubuntu0.1 failed to 
install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u 
zou het  opnieuw moeten installeren alvorens het te configureren.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1806074/+subscriptions

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

[Desktop-packages] [Bug 1806069] [NEW] vpn (pptp) connection fails

2018-11-30 Thread Eduard Drenth

Public bug reported:

I know we should abandon pptp in favor of for example openvpn, but not
in place yet

Relevant logging:

Nov 30 16:33:52 eduard-X756UB NetworkManager[1106]:   [1543592032.0374] 
vpn-connection[0x561e9011c5a0,0e7e3fc4-0f4f-48c0-a86e-5b96dcc832e0,"VPN 
connection 1",0]: Started the VPN service, PID 5684
Nov 30 16:33:52 eduard-X756UB NetworkManager[1106]:   [1543592032.0478] 
vpn-connection[0x561e9011c5a0,0e7e3fc4-0f4f-48c0-a86e-5b96dcc832e0,"VPN 
connection 1",0]: Saw the service appear; activating connection
Nov 30 16:33:52 eduard-X756UB NetworkManager[1106]:   [1543592032.1933] 
vpn-connection[0x561e9011c5a0,0e7e3fc4-0f4f-48c0-a86e-5b96dcc832e0,"VPN 
connection 1",0]: VPN connection: (ConnectInteractive) reply received
Nov 30 16:33:52 eduard-X756UB NetworkManager[1106]:   [1543592032.2137] 
vpn-connection[0x561e9011c5a0,0e7e3fc4-0f4f-48c0-a86e-5b96dcc832e0,"VPN 
connection 1",0]: VPN plugin: state changed: starting (3)
Nov 30 16:33:52 eduard-X756UB pppd[5691]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Nov 30 16:33:52 eduard-X756UB NetworkManager[1106]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Nov 30 16:33:52 eduard-X756UB pppd[5691]: pppd 2.4.7 started by root, uid 0
Nov 30 16:33:52 eduard-X756UB systemd-udevd[5695]: link_config: autonegotiation 
is unset or enabled, the speed and duplex are not writable.
Nov 30 16:33:52 eduard-X756UB NetworkManager[1106]: Using interface ppp0
Nov 30 16:33:52 eduard-X756UB NetworkManager[1106]: Connect: ppp0 <--> 
/dev/pts/1
Nov 30 16:33:52 eduard-X756UB pppd[5691]: Using interface ppp0
Nov 30 16:33:52 eduard-X756UB pppd[5691]: Connect: ppp0 <--> /dev/pts/1
Nov 30 16:33:52 eduard-X756UB pptp[5696]: nm-pptp-service-5684 
log[main:pptp.c:353]: The synchronous pptp option is NOT activated
Nov 30 16:33:52 eduard-X756UB NetworkManager[1106]:   [1543592032.2256] 
manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/17)
Nov 30 16:33:52 eduard-X756UB NetworkManager[1106]:   [1543592032.2331] 
devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Nov 30 16:33:52 eduard-X756UB NetworkManager[1106]:   [1543592032.2331] 
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown 
configuration found.
Nov 30 16:33:52 eduard-X756UB pptp[5708]: nm-pptp-service-5684 
log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 1 
'Start-Control-Connection-Request'
Nov 30 16:33:52 eduard-X756UB pptp[5708]: nm-pptp-service-5684 
log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply
Nov 30 16:33:52 eduard-X756UB pptp[5708]: nm-pptp-service-5684 
log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established.
Nov 30 16:33:53 eduard-X756UB pptp[5708]: nm-pptp-service-5684 
log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 7 
'Outgoing-Call-Request'
Nov 30 16:33:53 eduard-X756UB pptp[5708]: nm-pptp-service-5684 
log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply.
Nov 30 16:33:53 eduard-X756UB pptp[5708]: nm-pptp-service-5684 
log[ctrlp_disp:pptp_ctrl.c:919]: Our outgoing call request [callid 53083] has 
not been accepted.
Nov 30 16:33:53 eduard-X756UB pptp[5708]: nm-pptp-service-5684 
log[ctrlp_error:pptp_ctrl.c:207]: Result code is 2 'General Error'. Error code 
is 4, Cause code is 0
Nov 30 16:33:53 eduard-X756UB NetworkManager[1106]: Terminated
Nov 30 16:33:53 eduard-X756UB pptp[5708]: nm-pptp-service-5684 
log[ctrlp_error:pptp_ctrl.c:217]: Error is '(No-Resource)', Error message: 
'Insufficient resources to handle this command now'
Nov 30 16:33:53 eduard-X756UB NetworkManager[1106]: Modem hangup
Nov 30 16:33:53 eduard-X756UB NetworkManager[1106]: Connection terminated.
Nov 30 16:33:53 eduard-X756UB pptp[5708]: nm-pptp-service-5684 
log[call_callback:pptp_callmgr.c:84]: Closing connection (call state)
Nov 30 16:33:53 eduard-X756UB pptp[5708]: nm-pptp-service-5684 
log[call_callback:pptp_callmgr.c:84]: Closing connection (call state)
Nov 30 16:33:53 eduard-X756UB pppd[5691]: Modem hangup
Nov 30 16:33:53 eduard-X756UB pppd[5691]: Connection terminated.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pptp-linux 1.9.0+ds-2
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 30 16:43:14 2018
InstallationDate: Installed on 2016-09-01 (820 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: pptp-linux
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pptp-linux (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 pptp-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806069

Title:
  vpn (pptp) connection fails

Status in pptp-linux package in Ubuntu:
  New

Bug description:
  I know we

[Desktop-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-30 Thread Dan Streetman

uploaded hwdata and gnome-desktop3 to trusty, thanks!

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Trusty:
  In Progress
Status in hwdata source package in Trusty:
  In Progress
Status in unity-settings-daemon source package in Trusty:
  Invalid
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in hwdata source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in hwdata source package in Cosmic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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

[Desktop-packages] [Bug 1805438] Re: Print settings present two distinct interfaces for adding printers

2018-11-30 Thread Casey

Thanks for your followup.

journalctl | grep cups-pk-helper

yields exactly two entries from that day:

Nov 26 11:08:22 localhost.localdomain gnome-control-c[27707]: cups-pk-helper: 
addition of printer 1002 failed: client-error-not-authorized
Nov 26 16:33:53 localhost.localdomain gnome-control-c[7361]: cups-pk-helper: 
addition of printer 1002 failed: client-error-not-authorized

I can consistently reproduce this behavior. If I try to add another
printer the same error results and yields the journalctl entry

Nov 30 07:41:32 localhost.localdomain gnome-control-c[13550]: cups-pk-
helper: addition of printer 958_small failed: client-error-not-
authorized


Is there a way to run cups-pk-helper in a verbose or debugging mode?

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

Title:
  Print settings present two distinct interfaces for adding printers

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

Bug description:
  1. Running stock 18.04.1
  2. gnome-control-center 3.28.2-0ubuntu0.18.04.2

  As shown in the first screenshot below, the print settings panel shows
  an "Add..." in the headerbar as well as "Add a printer..." and
  "Additional printer settings" in the main area.

  The first two buttons are highlighted and would naturally seem to be
  the first options to try, but they didn't actually work. While I was
  able to browse the list of printers attached to the print server,
  attempting to actually add the printer ended in an uninformative error
  message as shown in the second screenshot.

  On the other hand, "Additional printer settings" launches the old
  system-config-printer utility which did succeed in adding my desired
  printer.

  It is not at all obvious without trial and error which option one
  should choose to add a new printer.

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

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

[Desktop-packages] [Bug 1749672] Re: [MIR] xdg-desktop-portal

2018-11-30 Thread Ken VanDine

** Also affects: xdg-desktop-portal (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: xdg-desktop-portal (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  [MIR] xdg-desktop-portal

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Xenial:
  New
Status in xdg-desktop-portal source package in Bionic:
  New

Bug description:
  Availability
  
  In sync with Debian.

  Built for all supported architectures.

  Rationale
  =
  Required for snaps.

  Security
  
  No known security issues, but due to the nature of this package, a security 
review is probably needed.

  https://security-tracker.debian.org/tracker/source-package/xdg-desktop-portal
  https://launchpad.net/xdg-desktop-portal/+cve

  Quality assurance
  =
  - The Desktop Packages bug team is subscribed.

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

  Upstream build tests (new) are run with dh_auto_test (failure would
  fail the build).

  autopkgtests are passing
  https://autopkgtest.ubuntu.com/packages/xdg-desktop-portal
  https://ci.debian.net/packages/x/xdg-desktop-portal/unstable/amd64/

  Dependencies
  
  No universe binary dependencies

  Standards compliance
  
  4.1.3

  debhelper compat 11, dh 7 style simple rules

  Maintenance
  ===
  - Actively developed upstream. Last release was 0.10 yesterday
  https://github.com/flatpak/xdg-desktop-portal/commits/master

  Well-maintained in Debian by Simon McVittie (Debian's Flatpak maintainer). 
Team-maintained.
  https://salsa.debian.org/debian/xdg-desktop-portal

  Background information
  ==
  xdg-desktop-portal was originally created to allow Flatpak apps to request 
access outside the sandbox. It's useful technology that can be used by Snap 
too, which simplifies work for app developers to support both next generation 
packaging formats. For instance, see 
https://blogs.gnome.org/alexl/2018/02/14/moving-a-portal/

  See also the MIR xdg-desktop-portal-gtk LP: #1750069.

  Presumably, we'll want to backport these packages to be snap
  dependencies in 16.04 LTS (maybe 14.04 LTS too).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672/+subscriptions

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

[Desktop-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

2018-11-30 Thread Vivien GUEANT

How to activate log to understand what blocks the wifi connection ?

I watched "dmesg," but i saw nothing.

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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

[Desktop-packages] [Bug 1725779] Re: Gnome network manager cannot find authentication binary

2018-11-30 Thread Wilfried Jonker

I had a fresh Ubuntu 18.04 install and was effected by this bug. Running

sudo dpkg-reconfigure network-manager-pptp-gnome

Solved the problem.

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

Title:
  Gnome network manager cannot find authentication binary

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

Bug description:
  From logs:

  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7424] audit: 
op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" 
name="Library" pid=2510 uid=1000 result="success"
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7473] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Started the VPN service, PID 6934
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7518] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Saw the service appear; activating connection
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V NetworkManager[5935]:  [1508608443.7698] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Failed to request VPN secrets #3: No agents were available for t
  his request.
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7708] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 VPN plugin: state changed: stopped (6)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-pptp-gnome 1.2.4-4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 21 14:07:06 2017
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-pptp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

I have also verified unity-settings-daemon
15.04.1+16.04.20160701-0ubuntu3 for Xenial.

After connecting a faulty-EDID display - I saw the product name. With a
display device with correct dimensions in EDID - screen diagonal in
inches was displayed.

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Trusty:
  In Progress
Status in hwdata source package in Trusty:
  In Progress
Status in unity-settings-daemon source package in Trusty:
  Invalid
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in hwdata source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in hwdata source package in Cosmic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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

[Desktop-packages] [Bug 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account

I should note that the page does "load", but it takes around 4 to 5
minutes to get anything on the screen. After the wait, when something
shows in the screen, I type my username, and proceed to type my password
it says that an error has ocurred. On the VM ("disco" VM) there is no
wait time, and everything happens without a hitch. I'll test now with
the "cosmic" VM.

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

Title:
  Not able to log in into Google Account, aswell as Microsoft account

Status in gnome-control-center package in Ubuntu:
  New
Status in gnome-initial-setup package in Ubuntu:
  Incomplete

Bug description:
  After the first boot up of Ubuntu 18.10, it invites me to log-in into
  several accounts, including Google and Microsoft accounts. After I
  log-in into Ubuntu One, my next step is to log in my Google Account,
  but the log-in page never loads, and when it does (after a couple of
  minutes), and I insert my log in credentials, it fails the log-in
  process, all of this happens with the Microsoft account too. The
  Ubuntu One account logs-in without a hitch, but the rest does not.

  1) Description:   Ubuntu 18.10
  Release:  18.10

  2) gnome-initial-setup:
Instalado: 3.30.0-1ubuntu3
Candidato: 3.30.0-1ubuntu3.1
Tabela de versão:
   3.30.0-1ubuntu3.1 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
   *** 3.30.0-1ubuntu3 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-initial-setup 3.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 27 11:12:31 2018
  ExecutablePath: /usr/lib/gnome-initial-setup/gnome-initial-setup
  InstallationDate: Installed on 2018-11-27 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account

So, i changed the language to english on my machine, but the same thing
happens, it just won't load the page. And yes, i used the same machine
to run the VM. I'm downloading the 18.10 ISO to install in a VM and see
if it loads there. But this is a interesting situation, because it loads
in a VM (at least in "disco"), but not the real machine. I'm going to
test it on the new 18.10 VM and post any new comments here.

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

Title:
  Not able to log in into Google Account, aswell as Microsoft account

Status in gnome-control-center package in Ubuntu:
  New
Status in gnome-initial-setup package in Ubuntu:
  Incomplete

Bug description:
  After the first boot up of Ubuntu 18.10, it invites me to log-in into
  several accounts, including Google and Microsoft accounts. After I
  log-in into Ubuntu One, my next step is to log in my Google Account,
  but the log-in page never loads, and when it does (after a couple of
  minutes), and I insert my log in credentials, it fails the log-in
  process, all of this happens with the Microsoft account too. The
  Ubuntu One account logs-in without a hitch, but the rest does not.

  1) Description:   Ubuntu 18.10
  Release:  18.10

  2) gnome-initial-setup:
Instalado: 3.30.0-1ubuntu3
Candidato: 3.30.0-1ubuntu3.1
Tabela de versão:
   3.30.0-1ubuntu3.1 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
   *** 3.30.0-1ubuntu3 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-initial-setup 3.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 27 11:12:31 2018
  ExecutablePath: /usr/lib/gnome-initial-setup/gnome-initial-setup
  InstallationDate: Installed on 2018-11-27 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1725779] Re: Gnome network manager cannot find authentication binary

2018-11-30 Thread Wilfried Jonker

I can confirm this bug. When using the nm-applet there is nog problem.

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

Title:
  Gnome network manager cannot find authentication binary

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

Bug description:
  From logs:

  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7424] audit: 
op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" 
name="Library" pid=2510 uid=1000 result="success"
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7473] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Started the VPN service, PID 6934
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7518] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Saw the service appear; activating connection
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V NetworkManager[5935]:  [1508608443.7698] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Failed to request VPN secrets #3: No agents were available for t
  his request.
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7708] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 VPN plugin: state changed: stopped (6)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-pptp-gnome 1.2.4-4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 21 14:07:06 2017
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-pptp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805438] Re: Print settings present two distinct interfaces for adding printers

2018-11-30 Thread Till Kamppeter

For cups-pk-helper problems we need appropriate log files, as Sebastien
already asked for.

For the buttons, the "Additional printer settings" is not for adding
printers but for getting into an advanced interface (system-config-
printer). Perhaps one could rename it into "Advanced printer settings"?

The "Add a printer..." in the center of the screen only appears if there
is no printer set up at all. The "Add" button at the top is always
there, to be able to add more printers when there is already at least
one set up. I do not know whether one could improve the design here. I
would leave this to the GUI experts.

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

Title:
Print settings present two distinct interfaces for adding printers

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

Bug description:
1. Running stock 18.04.1
2. gnome-control-center 3.28.2-0ubuntu0.18.04.2

As shown in the first screenshot below, the print settings panel shows
an "Add..." in the headerbar as well as "Add a printer..." and
"Additional printer settings" in the main area.

On the other hand, "Additional printer settings" launches the old
system-config-printer utility which did succeed in adding my desired
printer.

It is not at all obvious without trial and error which option one
should choose to add a new printer.

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

[Desktop-packages] [Bug 1791991] Re: Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff)

2018-11-30 Thread Sebastien Bacher

The ppa is maintained by Ubuntu GNOME and not an official Ubuntu archive

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

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

Title:
  Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff)

Status in Ubuntu GNOME:
  New

Bug description:
  Nautilus version 3.30.0-0ubuntu1~cosmic1 in Gnome3 Staging PPA will not start.
  I am using Gnome-shell environment.
  And I also installed the new tracker version 2.1.3-1~cosmic1 from Gnome3 
Staging PPA.

  This is the error message when trying to start Nautilus from terminal:

  Tracker-ERROR **: 20:33:14.659: Unable to find default domain ontology
  rule /usr/share/tracker/domain-ontologies/default.rule

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

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

[Desktop-packages] [Bug 1805438] Re: Print settings present two distinct interfaces for adding printers

2018-11-30 Thread Sebastien Bacher

Thanks, that looks normal. I'm Ccing Till who looks after printing in
Ubuntu, maybe he has an idea what could be wrong/why cups-pk-helper
errors out. You didn't attach your journalctl log around the time of the
error, could you do that, it could include clues

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

Title:
Print settings present two distinct interfaces for adding printers

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

Bug description:
1. Running stock 18.04.1
2. gnome-control-center 3.28.2-0ubuntu0.18.04.2

As shown in the first screenshot below, the print settings panel shows
an "Add..." in the headerbar as well as "Add a printer..." and
"Additional printer settings" in the main area.

On the other hand, "Additional printer settings" launches the old
system-config-printer utility which did succeed in adding my desired
printer.

It is not at all obvious without trial and error which option one
should choose to add a new printer.

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

[Desktop-packages] [Bug 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account

2018-11-30 Thread Sebastien Bacher

Hum, do you use the same locale in the vm? Did you try a cosmic in a VM?
Disco didn't have much changes in its desktop stack yet so it would
weird to have it fixed there. Could have to do with the translations
maybe? Could you try on your machine by switching the language to
english?

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

Title:
  Not able to log in into Google Account, aswell as Microsoft account

Status in gnome-control-center package in Ubuntu:
  New
Status in gnome-initial-setup package in Ubuntu:
  Incomplete

Bug description:
  After the first boot up of Ubuntu 18.10, it invites me to log-in into
  several accounts, including Google and Microsoft accounts. After I
  log-in into Ubuntu One, my next step is to log in my Google Account,
  but the log-in page never loads, and when it does (after a couple of
  minutes), and I insert my log in credentials, it fails the log-in
  process, all of this happens with the Microsoft account too. The
  Ubuntu One account logs-in without a hitch, but the rest does not.

  1) Description:   Ubuntu 18.10
  Release:  18.10

  2) gnome-initial-setup:
Instalado: 3.30.0-1ubuntu3
Candidato: 3.30.0-1ubuntu3.1
Tabela de versão:
   3.30.0-1ubuntu3.1 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
   *** 3.30.0-1ubuntu3 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-initial-setup 3.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 27 11:12:31 2018
  ExecutablePath: /usr/lib/gnome-initial-setup/gnome-initial-setup
  InstallationDate: Installed on 2018-11-27 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account

I`m now running a virtual machine with "disco" and i`ve been able to
connect all of my accounts without a problem. This bug seems to be
affecting mainly "cosmic" (I don't know about "bionic"). So, it seems
like the issue has been fixed on "disco", or my install of "cosmic" has
a problem. But it is interesting that this is affecting some colleagues
of mine, so it looks like the issue is not on my install of "cosmic".

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

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

Title:
  Not able to log in into Google Account, aswell as Microsoft account

Status in gnome-control-center package in Ubuntu:
  New
Status in gnome-initial-setup package in Ubuntu:
  Incomplete

Bug description:
  After the first boot up of Ubuntu 18.10, it invites me to log-in into
  several accounts, including Google and Microsoft accounts. After I
  log-in into Ubuntu One, my next step is to log in my Google Account,
  but the log-in page never loads, and when it does (after a couple of
  minutes), and I insert my log in credentials, it fails the log-in
  process, all of this happens with the Microsoft account too. The
  Ubuntu One account logs-in without a hitch, but the rest does not.

  1) Description:   Ubuntu 18.10
  Release:  18.10

  2) gnome-initial-setup:
Instalado: 3.30.0-1ubuntu3
Candidato: 3.30.0-1ubuntu3.1
Tabela de versão:
   3.30.0-1ubuntu3.1 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
   *** 3.30.0-1ubuntu3 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-initial-setup 3.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 27 11:12:31 2018
  ExecutablePath: /usr/lib/gnome-initial-setup/gnome-initial-setup
  InstallationDate: Installed on 2018-11-27 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805576] Re: package python3-gdbm:amd64 3.6.7-1~18.04 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

2018-11-30 Thread Till Kamppeter

This looks like something is messed up on your system, as dpkg tells
that you have hplip-data installed ans also the file
/usr/share/python3/runtime.d/hplip-data.rtupdate is present, but the
directory /usr/share/hplip/ui5/ and its files, which are also part of
this package, are missing.

Please re-install the package via

sudo apt install --reinstall hplip-data

to recover the lost files. Please tell whether this eliminates the
problems you have reported here.

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

Title:
  package python3-gdbm:amd64 3.6.7-1~18.04 failed to install/upgrade:
  Abhängigkeitsprobleme - verbleibt unkonfiguriert

Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  No update

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-gdbm:amd64 3.6.7-1~18.04
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   git:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Nov 28 06:38:14 2018
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  InstallationDate: Installed on 2018-06-21 (159 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: python3-stdlib-extensions
  Title: package python3-gdbm:amd64 3.6.7-1~18.04 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-30 Thread Dan Streetman

** Also affects: hwdata (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Also affects: unity-settings-daemon (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: unity-settings-daemon (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: hwdata (Ubuntu Xenial)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

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

** Changed in: hwdata (Ubuntu Bionic)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

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

** Changed in: hwdata (Ubuntu Cosmic)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

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

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

** Changed in: hwdata (Ubuntu Trusty)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

** Changed in: gnome-desktop3 (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: gnome-desktop3 (Ubuntu Trusty)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

** Changed in: gnome-desktop3 (Ubuntu Trusty)
   Status: New => In Progress

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

** Changed in: gnome-desktop3 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Trusty:
  In Progress
Status in hwdata source package in Trusty:
  In Progress
Status in unity-settings-daemon source package in Trusty:
  Invalid
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in hwdata source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in hwdata source package in Cosmic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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

[Desktop-packages] [Bug 1791991] Re: Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff)

Does the thumnailer still work on 32 bit with nautilus 3.30 from this
ppa: https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/nautilus330/

 If it does not then it's better to file a bug in debian.

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

Title:
  Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff)

Status in nautilus package in Ubuntu:
  New

Bug description:
  Nautilus version 3.30.0-0ubuntu1~cosmic1 in Gnome3 Staging PPA will not start.
  I am using Gnome-shell environment.
  And I also installed the new tracker version 2.1.3-1~cosmic1 from Gnome3 
Staging PPA.

  This is the error message when trying to start Nautilus from terminal:

  Tracker-ERROR **: 20:33:14.659: Unable to find default domain ontology
  rule /usr/share/tracker/domain-ontologies/default.rule

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

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

[Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

2018-11-30 Thread Sharaf Zaman

** Description changed:

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  
  $ apt-cache policy gnome-session-bin
  gnome-session-bin:
-   Installed: 3.18.1.2-1ubuntu1.16.04.1
-   Candidate: 3.18.1.2-1ubuntu1.16.04.1
-   Version table:
-  *** 3.18.1.2-1ubuntu1.16.04.1 500
- 500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  3.18.1.2-1ubuntu1 500
- 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+   Installed: 3.18.1.2-1ubuntu1.16.04.1
+   Candidate: 3.18.1.2-1ubuntu1.16.04.1
+   Version table:
+  *** 3.18.1.2-1ubuntu1.16.04.1 500
+ 500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  3.18.1.2-1ubuntu1 500
+ 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  
  I'm using gnome-session-flashback
  
  What happens:
  The screen doesn't lock when having certain pages in Chrome tabs
  
  Expected:
  The screen should lock after the configured timeout in settings.
- 
  
  I've been having this issue sice before 14.04, which I recently upgraded
  (fresh install) to 16.04.
  
  After fresh install, the screen would turn down and lock the computer
  after 10 minutes (or whatever time I setup). At one point it stopped
  working. The screen never shuts down unless I manually lock the session
  with CTRL-ALT-L.
  
  I've followed the steps in
  https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure
  
  The culprit seems to be that Chrome issues some suspend inhibitions
  through dbus when doing certain operations. Many people find this
  problem when using Yahoo Mail. I can reproduce it with Odoo. I'm pretty
  sure that Chrome is doing something else of what i've found out.
  
  1) Gnome screen saver works correctly. I can trigger it manually with:
  $ gnome-screensaver-command -a
  
  2) Gnome screen saver never receives the "session idle" status callback.
  
  3) When Chrome is not running, I can manually inhibit the idle status:
  $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" 
--inhibit-only --inhibit idle:suspend
  Inhibiting until Ctrl+C is pressed...
  
  4) I can query the inhibitors:
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return 
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 
reply_serial=2
-array [
-   object path "/org/gnome/SessionManager/Inhibitor1686"
-]
- $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetAppId 
+    array [
+   object path "/org/gnome/SessionManager/Inhibitor1686"
+    ]
+ $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetAppId
  ('test',)
- $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetReason 
+ $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetReason
  ('manual idle inhibit',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetFlags
  (uint32 12,)
  
  12=4(suspend) + 8(idle)
  
  5) When testing, I can inhibit for 70 seconds, idle timeout being 60 (1
  minute). After these 70 seconds pass, the screen locks.
  
  6) Regarding Chrome, this is the information I get when querying the 
inhibitor:
  GetAppId: ('/usr/bin/google-chrome-stable',)
  GetReason: ('Uploading data to 10.200.0.163',)
  GetFlags: (uint32 4,)
  
  The flags just inhibits suspend, not locking or entering powersaving
  mode.
  
  This inhibitor seems to stay for 10-15 seconds, then goes away for
  another 30-60 seconds. The screen NEVER locks when this tab is open. No
  matter the inhibitor is present or not.
  
- 
  I'm not sure where to go on. If it's a Chrome bug it must be using other
  mechanisms to prevent the idle timeout. Any ideas on what to look for?
  
  Julian.

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

Title:
  Screen doesn't lock or go to sleep when certain Chrome tabs are open

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy gnome-session-bin
  gnome-session-bin:
    Installed: 3.18.1.2-1ubuntu1.16.04.1
    Candidate: 3.18.1.2-1ubuntu1.16.04.1
    Version table:
   *** 3.18.1.2-1ubuntu1.16.04.1 500
  500 http://es.ar

[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen

2018-11-30 Thread Andrea Azzarone

** Description changed:

+ [Impact]
+ When entering the lock-screen mode, gnome-shell disables all the extensions. 
It can happen that under certain conditions ubuntu-dock re-enables itself, 
causing the ubuntu-dock to appear in the lock-screen, exposing sensitive 
information. One possible way to reproduce this is to enable dash-to-dock and 
ubuntu-dock at the same time.
+ 
+ [Test Case]
+ 1. Make sure ubuntu-dock is enabled
+ 2. Enable dash-to-dock too
+ 3. Lock the screen
+ 4. Make sure the dock does not appear on the lock screen
+ 5. Make sure there is no warning is the journal
+ 
+ [Possible Regressions]
+ Even if it's something we don't really support please make sure that you can 
use dash-to-dock without uninstalling ubuntu-dock.
+ 
+ [Original Bug]
+ 
  After an update from ubuntu 16.04 to 18.04 the dock is aviable on the 
lockscreen after user login.
  I did not configure this knowingly. Also i can start every application which 
is available on the dock.
  Settings, virtual box, visualstudio code and so on.
  
  After the update to 18.04 i just configure the screen frequency to 144Hz
  and the night mode on. And attach the dock on bottom.
  
  I later undid these customizations back to configuration before, but the
  dock is stil aviable on lockscreen.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 18:30:16 2018
  InstallationDate: Installed on 2018-04-08 (27 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago)
- --- 
+ ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (27 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell-extension-ubuntu-dock 0.9.1
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

Title:
  Ubuntu dock/launcher is shown on the lock screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Bionic:
  In Progress
Status in gnome-shell source package in Cosmic:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Cosmic:
  In Progress
Status in gnome-shell source package in Disco:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Disco:
  Fix Released

Bug description:
  [Impact]
  When entering the lock-screen mode, gnome-shell disables all the extensions. 
It can happen that under certain conditions ubuntu-dock re-enables itself, 
causing the ubuntu-dock to appear in the lock-screen, exposing sensitive 
information. One possible way to reproduce this is to enable dash-to-dock and 
ubuntu-dock at the same time.

  [Test Case]
  1. Make sure ubuntu-dock is enabled
  2. Enable dash-to-dock too
  3. Lock the screen
  4. Make sure the dock does not appear on the lock screen
  5. Make sure there is no warning is the journal

  [Possible Regressions]
  Even if it's something we don't really support please make sure that you can 
use dash-to-dock without uninstalling ubuntu-dock.

  [Original Bug]

  After an update from ubuntu 16.04 to 18.04 the dock is aviable on the 
lockscreen after user login.
  I did not configure this knowingly. Also i can start every application which 
is available on the dock.
  Settings, virtual box, visualstudio code and so on.

  After the update to 18.04 i just configure the screen frequency to
  144Hz and the night mode on. And attach the dock on bottom.

  I later undid these customiz

[Desktop-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

unity-settings-daemon should NOT be nominated for trusty, but I can't
fix that.

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in gnome-desktop3 package in Ubuntu:
  New
Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in hwdata source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in hwdata source package in Cosmic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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

[Desktop-packages] [Bug 1805148] ProcCpuinfoMinimal.txt

2018-11-30 Thread Paul Chambre

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1805148/+attachment/5217661/+files/ProcCpuinfoMinimal.txt

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

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

Title:
  [radeon] Lock screen corrupt since upgrade to 18.04.01

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  Immediately after upgrade to 18.04.01 from 16.04.01, the lock screen of this 
laptop (an HP 6910p) became corrupt. When logged in and using the system, video 
display is fine, but the lock screen is consistently garbled as in the attached 
photo. Switching to Wayland made no difference in this behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.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 2016-01-23 (1038 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (104 days ago)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.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 2016-01-23 (1041 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Package: mesa
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (107 days ago)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1805148] Re: [radeon] Lock screen corrupt since upgrade to 18.04.01

2018-11-30 Thread Paul Chambre

apport information

** Description changed:

  Immediately after upgrade to 18.04.01 from 16.04.01, the lock screen of this 
laptop (an HP 6910p) became corrupt. When logged in and using the system, video 
display is fine, but the lock screen is consistently garbled as in the attached 
photo. Switching to Wayland made no difference in this behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.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 2016-01-23 (1038 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (104 days ago)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 18.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 2016-01-23 (1041 days ago)
+ InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
+ Package: mesa
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
+ Tags:  bionic wayland-session
+ Uname: Linux 4.15.0-39-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2018-08-14 (107 days ago)
+ UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  [radeon] Lock screen corrupt since upgrade to 18.04.01

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  Immediately after upgrade to 18.04.01 from 16.04.01, the lock screen of this 
laptop (an HP 6910p) became corrupt. When logged in and using the system, video 
display is fine, but the lock screen is consistently garbled as in the attached 
photo. Switching to Wayland made no difference in this behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.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 2016-01-23 (1038 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (104 days ago)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.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 2016-01-23 (1041 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Package: mesa
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (107 days ago)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True

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

[Desktop-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

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

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in gnome-desktop3 package in Ubuntu:
  New
Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in hwdata source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in hwdata source package in Cosmic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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

[Desktop-packages] [Bug 1806020] Re: package texlive-fonts-recommended (not installed) failed to install/upgrade: unable to open '/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg

2018-11-30 Thread Ceri WIlliams

** Description changed:

  The following install failed due to an error on the *dpkg-new file:
  
  $ sudo apt-get install asciidoc libcurl4-openssl-dev libxml2-dev xclip
  
  ErrorMessage:
-  unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
+  unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
  
  $ sudo ls -lad /usr/share/texlive/texmf-dist/fonts/tfm/adobe
  ls: cannot access '/usr/share/texlive/texmf-dist/fonts/tfm/adobe': No such 
file or directory
  
  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: texlive-fonts-recommended (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 30 10:41:47 2018
  DuplicateSignature:
-  package:texlive-fonts-recommended:(not installed)
-  Unpacking texlive-fonts-recommended (2017.20180305-1) ...
-  dpkg: error processing archive 
/tmp/apt-dpkg-install-Fh2hOk/08-texlive-fonts-recommended_2017.20180305-1_all.deb
 (--unpack):
-   unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
+  package:texlive-fonts-recommended:(not installed)
+  Unpacking texlive-fonts-recommended (2017.20180305-1) ...
+  dpkg: error processing archive 
/tmp/apt-dpkg-install-Fh2hOk/08-texlive-fonts-recommended_2017.20180305-1_all.deb
 (--unpack):
+   unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2018-11-04 (25 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
-  dpkg 1.19.0.5ubuntu2.1
-  apt  1.6.6
+  dpkg 1.19.0.5ubuntu2.1
+  apt  1.6.6
  SourcePackage: texlive-base
  Title: package texlive-fonts-recommended (not installed) failed to 
install/upgrade: unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)
+ 
+ Running apt-get -f install resolved the issue:
+ $ dpkg -l texlive-fonts-recommended | tail -n1
+ ii  texlive-fonts-recommended 2017.20180305-1 all  TeX Live: 
Recommended fonts

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

Title:
  package texlive-fonts-recommended (not installed) failed to
  install/upgrade: unable to open '/usr/share/texlive/texmf-
  dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': Operation not
  permitted

Status in texlive-base package in Ubuntu:
  New

Bug description:
  The following install failed due to an error on the *dpkg-new file:

  $ sudo apt-get install asciidoc libcurl4-openssl-dev libxml2-dev xclip

  ErrorMessage:
   unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted

  $ sudo ls -lad /usr/share/texlive/texmf-dist/fonts/tfm/adobe
  ls: cannot access '/usr/share/texlive/texmf-dist/fonts/tfm/adobe': No such 
file or directory

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: texlive-fonts-recommended (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 30 10:41:47 2018
  DuplicateSignature:
   package:texlive-fonts-recommended:(not installed)
   Unpacking texlive-fonts-recommended (2017.20180305-1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-Fh2hOk/08-texlive-fonts-recommended_2017.20180305-1_all.deb
 (--unpack):
    unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2018-11-04 (25 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: texlive-base
  Title: package texlive-fonts-recommended (not installed) failed to 
install/upgrade: unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new':

[Desktop-packages] [Bug 1768996] Re: Nautilus "Software caused connection abort" when copying file from smb share

2018-11-30 Thread niniendowarrior

I have a similar issue but some slight differences.  For example:
gio copy file.log smb://1.10.2.1/folder/
gio: file:///home/user/file.log: Network dropped connection on reset

When I copy, I get this error. On an old Linux Mint, I had the same
issue and rolling samba back to 4.3.9 fixed it.

My hard disk is connected to a D-Link DIR-636L.

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

Title:
  Nautilus "Software caused connection abort" when copying file from smb
  share

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  When copying a directory from a samba share on a NAS (Synology
  DS216j), it fails with "Software caused connection abort" after
  copying a few files.

  Expected to happen:
  Nautilus succesfully copies entire directory.

  What happens instead:
  Nautilus stops copying after a few files with the error "Software caused 
connection abort".

  Version:
  - Ubuntu 18.04. Behavior did not occur on 16.04.
  - samba version is 2:4.7.6+dfsg~ubuntu-0ubuntu2
  - gvfs version is 1.36.1-0ubuntu1

  
  - It seems related to 
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1312362.
  - It also does not seem to happen when using gio copy from the terminal.
  - I am also not sure whether this bug is in nautilus, gvfs, or samba.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri May  4 00:16:03 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'367'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x547+215+203'"
  InstallationDate: Installed on 2018-05-01 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1802589] Re: No image preview when adding a custom wallpaper

** Branch linked: lp:~khurshid-alam/unity-control-center/fix-image-
preview

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

Title:
  No image preview when adding a custom wallpaper

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

Bug description:
  How to reproduce,

  1) Go to unity-control-center->appearance

  2) Click on + icon, select a valid image

  3) (Expected) GtkFileChooser dialog shows a small preview of the
  image,

  4) (Actual) No, preview. Instead a icon (dialog-question) is shown.

  This is same for user accounts panel when user tries to add a custom
  avatar.

  This reason is in https://bazaar.launchpad.net/~unity-control-center-
  team/unity-control-center/trunk/view/head:/panels/appearance/cc-
  appearance-panel.c#L1303

  it uses g_file_info_get_content_type which returns an internal string
  and hence mime_type is always NULL.

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

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

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

[Desktop-packages] [Bug 1806020] Re: package texlive-fonts-recommended (not installed) failed to install/upgrade: unable to open '/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg

2018-11-30 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package texlive-fonts-recommended (not installed) failed to
  install/upgrade: unable to open '/usr/share/texlive/texmf-
  dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': Operation not
  permitted

Status in texlive-base package in Ubuntu:
  New

Bug description:
  The following install failed due to an error on the *dpkg-new file:

  $ sudo apt-get install asciidoc libcurl4-openssl-dev libxml2-dev xclip

  ErrorMessage:
   unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted

  $ sudo ls -lad /usr/share/texlive/texmf-dist/fonts/tfm/adobe
  ls: cannot access '/usr/share/texlive/texmf-dist/fonts/tfm/adobe': No such 
file or directory

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: texlive-fonts-recommended (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 30 10:41:47 2018
  DuplicateSignature:
   package:texlive-fonts-recommended:(not installed)
   Unpacking texlive-fonts-recommended (2017.20180305-1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-Fh2hOk/08-texlive-fonts-recommended_2017.20180305-1_all.deb
 (--unpack):
unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2018-11-04 (25 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: texlive-base
  Title: package texlive-fonts-recommended (not installed) failed to 
install/upgrade: unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1806020/+subscriptions

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

[Desktop-packages] [Bug 1188569] Re: Some keyboard shortcuts randomly stop working

** Branch linked: lp:~khurshid-alam/unity-settings-daemon/media-keys-fix

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

Title:
  Some keyboard shortcuts randomly stop working

Status in GNOME Shell:
  New
Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  Certain shortcuts randomly stops working in my computer. They are Super+s 
(workspace switcher), Super+Up (switch to workspace above) and Super+Down 
(switch to workspace below). Other shortcuts work fine.

  A few notes that might help:
  1- Reassigning shortcuts make them work again except for Super+s.
  2- Rebooting make shortcuts work.
  3- I have been using these shortcuts with many previous ubuntu versions and 
my preferences are old.
  4- I am not sure of certain steps that produces the problem. The shortcuts 
sometimes stop working but once they stop, they do not work unless I reassign 
them or reboot.

  I am using Ubuntu 13.04.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,grid,mousepoll,place,wall,snap,resize,vpswitch,session,animation,gnomecompat,imgpng,commands,move,workarounds,fade,unitymtgrabhandles,expo,scale,ezoom,unityshell]
  Date: Fri Jun  7 13:40:06 2013
  InstallationDate: Installed on 2013-05-27 (11 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load

** Branch linked: lp:~khurshid-alam/unity-settings-daemon/media-keys-fix

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

Title:
  /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
  fails to load

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  $ dconf dump /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
  [custom1]
  binding='BackSpace'
  command='gnome-session-quit --power-off'
  name='gnome-session-quit --power-off'

  [custom0]
  binding='g'
  command='gnome-terminal --geometry=80x99-0+0'
  name='gnome-terminal --geometry=80x99-0+0'
  $

  In spite of the above, time to time, not always, but since 18.04 much
  much more frequently this settings fails to become active just after
  booting, ... my account is logged in automatically just after boot.

  If I log out and log in again, then these key bindings work.

  If I go to the system settings, and define again, then these work
  again.

  Earlier, before 18.04 this phenomenon was rare, namely once a week at
  most.

  But since 18.04 it is almost guaranteed, not deterministic, but highly
  probable, that after an initial boot or a warm reboot these key
  bindings will not work.

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

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

[Desktop-packages] [Bug 1806020] [NEW] package texlive-fonts-recommended (not installed) failed to install/upgrade: unable to open '/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dp

2018-11-30 Thread Ceri WIlliams

Public bug reported:

The following install failed due to an error on the *dpkg-new file:

$ sudo apt-get install asciidoc libcurl4-openssl-dev libxml2-dev xclip

ErrorMessage:
 unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted

$ sudo ls -lad /usr/share/texlive/texmf-dist/fonts/tfm/adobe
ls: cannot access '/usr/share/texlive/texmf-dist/fonts/tfm/adobe': No such file 
or directory

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: texlive-fonts-recommended (not installed)
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Fri Nov 30 10:41:47 2018
DuplicateSignature:
 package:texlive-fonts-recommended:(not installed)
 Unpacking texlive-fonts-recommended (2017.20180305-1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-Fh2hOk/08-texlive-fonts-recommended_2017.20180305-1_all.deb
 (--unpack):
  unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
ErrorMessage: unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
InstallationDate: Installed on 2018-11-04 (25 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: texlive-base
Title: package texlive-fonts-recommended (not installed) failed to 
install/upgrade: unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: texlive-base (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package texlive-fonts-recommended (not installed) failed to
  install/upgrade: unable to open '/usr/share/texlive/texmf-
  dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': Operation not
  permitted

Status in texlive-base package in Ubuntu:
  New

Bug description:
  The following install failed due to an error on the *dpkg-new file:

  $ sudo apt-get install asciidoc libcurl4-openssl-dev libxml2-dev xclip

  ErrorMessage:
   unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted

  $ sudo ls -lad /usr/share/texlive/texmf-dist/fonts/tfm/adobe
  ls: cannot access '/usr/share/texlive/texmf-dist/fonts/tfm/adobe': No such 
file or directory

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: texlive-fonts-recommended (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 30 10:41:47 2018
  DuplicateSignature:
   package:texlive-fonts-recommended:(not installed)
   Unpacking texlive-fonts-recommended (2017.20180305-1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-Fh2hOk/08-texlive-fonts-recommended_2017.20180305-1_all.deb
 (--unpack):
unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2018-11-04 (25 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: texlive-base
  Title: package texlive-fonts-recommended (not installed) failed to 
install/upgrade: unable to open 
'/usr/share/texlive/texmf-dist/fonts/tfm/adobe/courier/pcrbc8t.tfm.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1806020/+subscriptions

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

[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend

2018-11-30 Thread Yogish Kulkarni

Okay. Looks like this is the case for mutter-3.30.1. In the current
version in bionic mutter-3.28.3, I don't see "Wayland EGLStream:
${have_wayland_eglstream}" option in configure.

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

Title:
  [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with
  EGLDevice backend

Status in mutter package in Ubuntu:
  New

Bug description:
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice
  backend due to following missing changes in mutter
  3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

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

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

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

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

[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend

2018-11-30 Thread Yogish Kulkarni

I think on aarch64 mutter is compiled with EGLDevice backend enabled. I
have opened this bug NVIDIA Tegra SoC.

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

Title:
  [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with
  EGLDevice backend

Status in mutter package in Ubuntu:
  New

Bug description:
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice
  backend due to following missing changes in mutter
  3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

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

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

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

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

[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend

Yes, Ubuntu builds with EGLDevice support always enabled. But you can't
explicitly select the "Wayland EGLStream" option - that's automatically
detected.

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

Title:
  [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with
  EGLDevice backend

Status in mutter package in Ubuntu:
  New

Bug description:
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice
  backend due to following missing changes in mutter
  3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

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

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

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

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

[Desktop-packages] [Bug 1805444] Re: Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend

** Tags added: nvidia

** Summary changed:

- Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend
+ [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice 
backend

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

Title:
  [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with
  EGLDevice backend

Status in mutter package in Ubuntu:
  New

Bug description:
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice
  backend due to following missing changes in mutter
  3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

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

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

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

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

[Desktop-packages] [Bug 1805444] Re: Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend

... so even when you do get EGLDevice working, you don't have EGLStreams
and so will be stuck with software rendering.

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

Title:
  [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with
  EGLDevice backend

Status in mutter package in Ubuntu:
  New

Bug description:
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice
  backend due to following missing changes in mutter
  3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

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

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

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

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

[Desktop-packages] [Bug 1805444] Re: Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend

The bigger problem (than any missing commits) is that Ubuntu builds of
mutter don't support EGLStreams:

mutter-3.30.1

prefix:   /usr/local
source code location: .
compiler: gcc

Startup notification: yes
libcanberra:  yes
libwacom: yes
gudev yes
Introspection:yes
Session management:   yes
Wayland:  yes
Wayland EGLStream:no  <--
Native (KMS) backend: yes
EGLDevice:yes
Remote desktop:   no

I think the missing build-dep isn't even in main. I can only find it in
https://github.com/NVIDIA/egl-wayland but would love to be proven wrong.

This is a problem on Ubuntu even when building upstream mutter with the
"missing" commits. The required file wayland-eglstream-protocols.pc and
friends is still missing from the Ubuntu distro.

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

Title:
  [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with
  EGLDevice backend

Status in mutter package in Ubuntu:
  New

Bug description:
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice
  backend due to following missing changes in mutter
  3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

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

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

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

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

[Desktop-packages] [Bug 1638395] Re: Unable to locate remote printer when printing

2018-11-30 Thread Shriv Commedia

Shriv ComMedia Solutions (SCMS) is a custom ERP software development company in 
India. The skilled team at SCMS is equipped with incredible tools to deliver 
ERP software development and ERP software solutions to the clients. We provide 
quality assured and cost-effective ERP software development services in India.

https://www.commediait.com

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

Title:
  Unable to locate remote printer when printing

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  My printer (EPSON Stylus Photo RX520) is connected to a  Yakkety station 
called "paris" which is the printing server. 
  Printing is fine from the server.

  When i configure another Yakkety station to print via this server, the 
printer is detected OK via dnssd, the driver is installed OK. But i can't 
print. 
  I get the following message "Unable to locate printer "paris.local"."

  I used to work on xenial but the connection was through ipps. I tried
  to configure the connection as in xenial, to no avail ...

  What i did: 
  add "192.168.1.4 paris.local" in /etc/hosts
  remove printer from cups, reinstalled it and i finally was able to print on 
the remote printer!

  Don't know if this problem is related to cups or avahi ...

  Ubuntu 16.10
  cups 2.2.0-2

  What i expected to happen: printing successful
  What happened: client cannot locate remote printer, add to add a line in 
/etc/hosts to make it work

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

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

[Desktop-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

gnome-desktop SRU proposal for trusty

** Patch removed: "trusty_gnome-desktop3_3.8.4-0ubuntu3.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+attachment/5217608/+files/trusty_gnome-desktop3_3.8.4-0ubuntu3.3.debdiff

** Patch added: "trusty_gnome-desktop3_3.8.4-0ubuntu3.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+attachment/5217619/+files/trusty_gnome-desktop3_3.8.4-0ubuntu3.3.debdiff

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in hwdata source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in hwdata source package in Cosmic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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

[Desktop-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

gnome-desktop SRU proposal for trusty.

** Patch added: "trusty_gnome-desktop3_3.8.4-0ubuntu3.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+attachment/5217608/+files/trusty_gnome-desktop3_3.8.4-0ubuntu3.3.debdiff

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in hwdata source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in hwdata source package in Cosmic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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

[Desktop-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

hwdata SRU proposal for trusty

** Patch added: "trusty_hwdata_0.249-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+attachment/5217607/+files/trusty_hwdata_0.249-1ubuntu1.debdiff

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in hwdata source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in hwdata source package in Cosmic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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

[Desktop-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center