[Bug 1724966] Re: Settings - Display - Primary Display selection does not allow selection of available entries

2019-01-16 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Settings - Display - Primary Display selection does not allow
  selection of available entries

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725455] Re: Login screen invisible / UI hanging when both 4K monitors connected via Displayport MST (docking station)

2019-01-16 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Login screen invisible / UI hanging when both 4K monitors connected
  via Displayport MST (docking station)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725360] Re: Secondary display can not be set

2019-01-16 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Secondary display can not be set

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725949] Re: nouveau drivers fails to start a wayland session and fallback to x11

2019-01-16 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

** Changed in: mutter (Ubuntu)
   Status: New => Won't Fix

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

Title:
  nouveau drivers fails to start a wayland session and fallback to x11

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1721957] Re: Blur on topbar

2019-01-16 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Blur on topbar

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1722974] Re: Wayland xorg not scalling screens properly

2019-01-16 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Wayland xorg not scalling screens properly

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725949] [NEW] nouveau drivers fails to start a wayland session and fallback to x11

2019-01-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have a Nvidia GTX 670. I tried the nouveau driver. At boot, it takes a
unusual long time then finally shows me gdm3 and everything is working
after. But echo $XDG_SESSION_TYPE is set to "x11". Reading the logs, I
can see that after multiple failures to launch wayland, it falls back to
X11.

I added an attachement of journalctl -b -1 where it fails with nouveau
(I'm filling the bug after reinstalling nvidia proprietary driver).

lspci -v
01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 670] 
(rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. GK104 [GeForce GTX 670]
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at f600 (32-bit, non-prefetchable) [size=16M]
Memory at e800 (64-bit, prefetchable) [size=128M]
Memory at f000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [size=128]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: 
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
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
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
 GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
BootLog:
 [  OK  ] Started LSB: Speech Dispatcher.
 [  OK  ] Started LSB: automatic crash report generation.
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 11:37:08 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
 nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK104 [GeForce GTX 670] [10de:1189] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GK104 [GeForce GTX 670] [3842:2678]
InstallationDate: Installed on 2017-09-17 (34 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=567a9b2b-0864-450e-9cfe-dab7a54b9fce ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/28/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V LX2
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0501:bd09/28/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
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.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
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
xserver.bootTime: Sun Oct 22 11:26:32 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.5-0ubuntu2

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: Won't Fix


** Tags: amd64 apport-bug artful ubuntu
-- 
nouveau drivers fails to start a wayland session and fallback to x11

[Bug 1725455] [NEW] Login screen invisible / UI hanging when both 4K monitors connected via Displayport MST (docking station)

2019-01-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I am experiencing serious issues after upgrading to Ubuntu 17.10 (coming
from 17.04 with Gnome, kernel 4.13).

I have 2 x 4K (Asus PB279Q) monitors, connected to a Lenovo Ultra Dock
(containing 2 x Displayport  via MST), where the Lenovo T550 is
connected onto it.  Both monitors were working perfectly fine at 30Hz
simultaneously in an extended desktop, 4K resolution in my old setup
with Gnome for over half a year (since kernel 4.10 blink issues on 4K
were solved, i used this setup since then).

However after upgrading to 17.10 using the new Gnome interface:
When the laptop is connected to the Lenovo Ultra Dock (to work on both 
monitors), the system is hanging and becoming unresponsive.  The mouse pointer 
is freezing and the only way is to do a hard-reboot.  I have checked the 
monitor settings, it's displayed at 60Hz when active, and it appears I am never 
able to use both monitors simultaneously.  When I get 1 monitor working 
(disconnecting the 2nd monitor from the MST port), after rebooting it works 
fine.  I tried to put settings of the 4K manually on 30Hz, reconnecting, but 
the system hangs again.  I have tried several combinations.  It results in a 
blank (purple) screen and hanging mouse (see attachment).

I tried also with the installation-iso to run a fresh 17.10 and tried
the same, the symptoms are similar.  I suspect that must be an issue
with the Displayport MST on dual 4K setups in the new 17.10.

When I connect 1 x 4K monitor to the rear displayport of the Lenovo
Ultra Dock (there are 2 for MST on the rear, so I disconnected the
other) *and* when I connect the other 4K monitor on the separate
displayport of the T550 itself instead, it works 100% fine!

Shortly: based on my knowledge that must definitely be some issue with
the MST displayport functionality itself, that is unable to
recognize/identify both 4K monitors when connected to the dock's both
displayport connections?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
Uname: Linux 4.13.4-041304-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 21:10:50 2017
DistUpgraded: 2017-10-19 21:54:53,162 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 5500 [17aa:2225]
   Subsystem: Lenovo GM108M [GeForce 940M] [17aa:2225]
InstallationDate: Installed on 2017-04-16 (186 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 20CKCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.4-041304-generic 
root=UUID=9fcc7f4c-35c0-4297-9c98-4dac9acee798 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
dmi.bios.date: 09/13/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N11ET42W (1.18 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CKCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T550
dmi.product.name: 20CKCTO1WW
dmi.product.version: ThinkPad T550
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.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
xserver.bootTime: Mon Apr 17 17:36:46 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: modeset

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: Won't Fix


** Tags: amd64 apport-bug artful displayport multimonitor ubuntu wayland-session
-- 
Login screen invisible / UI hanging when both 4K monitors connected via 
Displayport MST (docking station)
https://bugs.launchpad.net/bugs/1725455
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gnome-shell in Ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com

[Bug 1725360] [NEW] Secondary display can not be set

2019-01-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The position of the secondary display can not be applied with scales of 200% 
and 300%.
Can be modified with scale of 100% after modified some other configuration like 
Single Display scale. After set a new position of the secondary display (with 
100% scale) is not possible to change the scale maintaining the actual 
position. 

Using also Nvidia driver 384.90

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
 GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 14:02:12 2017
DistUpgraded: 2017-10-20 13:15:46,366 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3978]
   Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3978]
InstallationDate: Installed on 2017-08-23 (57 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
MachineType: LENOVO 20349
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=0f865fdf-a3ef-4fd1-88f3-80f6ca16ef1c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)
dmi.bios.date: 02/11/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 9ECN37WW(V2.01)
dmi.board.asset.tag: 31900058WIN
dmi.board.name: Lenovo Y50-70 Touch
dmi.board.vendor: LENOVO
dmi.board.version: 31900058WIN
dmi.chassis.asset.tag: 31900058WIN
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Y50-70 Touch
dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN37WW(V2.01):bd02/11/2015:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY50-70Touch:
dmi.product.family: IDEAPAD
dmi.product.name: 20349
dmi.product.version: Lenovo Y50-70 Touch
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
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

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: Won't Fix


** Tags: amd64 apport-bug artful ubuntu
-- 
Secondary display can not be set
https://bugs.launchpad.net/bugs/1725360
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gnome-shell in Ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1724966] [NEW] Settings - Display - Primary Display selection does not allow selection of available entries

2019-01-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Settings - Display - Primary Displayoffers me a choice of 3 displays.
Clicking on any of the non checked displays does nothing.

NOTE: My other 2 displays are currently disabled and likely shouldn't be
showing up in this list.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 13:27:08 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 343522U
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/28/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET99WW (2.59 )
dmi.board.asset.tag: Not Available
dmi.board.name: 343522U
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230 Tablet
dmi.product.name: 343522U
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.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

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: Won't Fix


** Tags: amd64 apport-bug artful ubuntu
-- 
Settings - Display - Primary Display selection does not allow selection of 
available entries
https://bugs.launchpad.net/bugs/1724966
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gnome-control-center in Ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1722974] [NEW] Wayland xorg not scalling screens properly

2019-01-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When I try scale the screen on my xps 15 9560 core i7 screen 4k the
image start to flap and sometimes the screen stay all black.

I tried use the nvidia driver but still doesn't work and when I try
scale using the settings option, the button "apply" disapear.

Additional monitor used: Dell U2715Hc with 2K resolution.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
 GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu2)
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 12 12:50:54 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:07be]
   Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
InstallationDate: Installed on 2017-10-10 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: Dell Inc. XPS 15 9560
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=cdd76ef8-2ee7-4962-b264-6671cf81976b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/30/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: Won't Fix


** Tags: amd64 apport-bug artful ubuntu
-- 
Wayland xorg not scalling screens properly
https://bugs.launchpad.net/bugs/1722974
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gnome-shell in Ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1721957] [NEW] Blur on topbar

2019-01-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hi,
after dist-upgrade today (07-out-17) , when I touch any window on topbar this 
fonts go blur

Tks!

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct  7 09:47:40 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
 NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GK208 [GeForce GT 710B] [3842:2713]
InstallationDate: Installed on 2017-10-05 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170925)
MachineType: Gigabyte Technology Co., Ltd. H81M-S1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=6b8e8b1b-5097-43df-80ee-a740e4d429bb ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/20/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FF
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-S1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFF:bd06/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S1:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: H81M-S1
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: Won't Fix


** Tags: amd64 apport-bug artful ubuntu
-- 
Blur on topbar
https://bugs.launchpad.net/bugs/1721957
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gnome-shell in Ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2019-01-16 Thread Daniel van Vugt
And to show this bug is also the hottest bug for 18.04 + 18.10 right
now:

https://bugs.launchpad.net/ubuntu/bionic/+bugs?orderby=-heat=0
https://bugs.launchpad.net/ubuntu/cosmic/+bugs?orderby=-heat=0

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2019-01-16 Thread Daniel van Vugt
This bug is certainly hotter than any other recent bug affecting 19.04
(for example) that I can find. So we should give it high priority as we
have. And the fact that it's a security bug is already shown separately
in the top right of the page.

Andrea has already mentioned in comment #86 that he has a fix, and it
appears to have landed upstream only 5 hours ago:
https://github.com/micheleg/dash-to-dock/pull/868

So fixes to 18.10 and 18.04 should follow soon.

P.S. The release notes are editable here:
https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes
https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseNotes

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2019-01-16 Thread Daniel van Vugt
And I finally figured out how to show this bug is also the hottest bug
for 18.10 right now:

https://bugs.launchpad.net/ubuntu/cosmic/+bugs?orderby=-heat=0

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1812143] Re: gsettings-desktop-schemas 3.31 breaks mutter 3.30

2019-01-16 Thread Jeremy Bicha
** Description changed:

  We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to
  gsettings-desktop-schemas.
  
  Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in
  gdm/gnome-shell being unable to start.
  
  Also, ukwm is a fork of mutter so the Kylin devs need to backport the
  relevant commits from mutter.
  
  The problematic gsettings commit was:
  https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c
  
  I think the mutter commits can be found at
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/133
+ 
+ We could easily add a dummy key with the old name but I'm thinking the
+ way forward is just to package the newer mutter.

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

Title:
  gsettings-desktop-schemas 3.31 breaks mutter 3.30

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1812143/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2019-01-16 Thread Ads20000
In response to comments complaining about fix times etc, I do not think
complaining in comments helps, it just creates noise. There's a button
at the top to mark oneself as affected by the bug as a replacement for
making that kind of comment (one can argue that it should been marked as
Critical rather than High because this is a security issue, however). If
you want to complain about bug response times, I suggest making a new
topic on community.ubuntu.com/c/desktop and make practical suggestions
about how they could be made faster.

Additionally, someone mentioned that this should have been in the
release notes. I think you can mark this bug as affecting the ubuntu-
release-notes project to flag up the fact that you believe that it
should be in the release notes, though I can't remember if release notes
can be amended post-release or not?

I recognize that I'm creating noise myself by posting this comment...

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1812014] Re: keyboard not responding after suspend after some time plus performance problem

2019-01-16 Thread Daniel van Vugt
Next time the keyboard stops responding, please try the workaround
suggested in bug 1807056:

1. Click on Show Applications (bottom left corner).

2. Click on Type to search...

3. Start typing.

If that doesn't work around the problem then next please provide more
information about your system by running:

  apport-collect 1812014

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

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

Title:
  keyboard not responding after suspend after some time plus performance
  problem

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1812143] [NEW] gsettings-desktop-schemas 3.31 breaks mutter 3.30

2019-01-16 Thread Jeremy Bicha
Public bug reported:

We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to
gsettings-desktop-schemas.

Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in
gdm/gnome-shell being unable to start.

Also, ukwm is a fork of mutter so the Kylin devs need to backport the
relevant commits from mutter.

The problematic gsettings commit was:
https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c

I think the mutter commits can be found at
https://gitlab.gnome.org/GNOME/mutter/merge_requests/133

** Affects: gsettings-desktop-schemas (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: mutter (Ubuntu)
 Importance: High
 Status: Triaged

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


** Tags: block-proposed disco

** Changed in: gsettings-desktop-schemas (Ubuntu)
   Status: New => Triaged

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

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

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

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

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

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

Title:
  gsettings-desktop-schemas 3.31 breaks mutter 3.30

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1812143/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

2019-01-16 Thread Daniel van Vugt
Thanks.

I wonder if this bug is directly related to "using Intel graphics on my
hybrid Nvidia laptop". Since regular Intel GPU users never seem to see
such problems. Although this is also one of the first bug reports about
a Coffee Lake GPU I have seen too, so it might be an Intel problem...

1. Can you please try disabling the Nvidia ("discrete") GPU in the
system BIOS and tell us if that fixes it?

2. Can you please also run 'dpkg -l > allpackages.txt' and send us the
resulting file 'allpackages.txt'?

3. If the problem persists (and only if) then please also attach copies
of your Xorg log files (/var/log/Xorg*log). Please also attach a copy of
your Xorg configuration file if you have one (find /etc -name
xorg.conf).

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

Title:
  Tearing and/or flickering when using Intel graphics

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1803527] Re: ubuntu 18.10 fails to restore from suspend if no password

2019-01-16 Thread Daniel van Vugt
Please wait until bug 1769383 is declared fixed for 18.10 and then we
can see if the problem still occurs.

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

Title:
  ubuntu 18.10 fails to restore from suspend if no password

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1809092] Re: gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR: Error: No valid stylesheet found for 'Yaru/gnome-shell.css'

2019-01-16 Thread Daniel van Vugt
I agree the hardcoded theme is not ideal. Regardless, bug closed.

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

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

Title:
  gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR:
  Error: No valid stylesheet found for 'Yaru/gnome-shell.css'

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1803527] Re: ubuntu 18.10 fails to restore from suspend if no password

2019-01-16 Thread Daniel van Vugt
> The left panel is over the purple-like lock screen and unusable (the
only thing is that icons illuminate with mouse movement but they don't
respond on click.

I believe that is bug 1769383. And in fact some similar bugs to this
that are different to the original bug 1769383 have already been grouped
into that one.

P.S. If you've still got anything on screen and no relevant crash
reports in /var/crash then please don't use the word "crash" because
it's not and that just causes confusion.

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

Title:
  ubuntu 18.10 fails to restore from suspend if no password

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1730229] Re: Desktop stops accepting input from mouse, keyboard, touchpad, or touchscreen, but topbar and dock still accept input

2019-01-16 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1181666 ***
https://bugs.launchpad.net/bugs/1181666

Even if the original reporter agrees that the duplicate status is wrong,
then this bug would still be closed because 17.10 is past end-of-life.

So if you experience ongoing problems and think they are different to
bug 1181666 then please open a new bug by running:

  ubuntu-bug gnome-shell

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

Title:
  Desktop stops accepting input from mouse, keyboard, touchpad, or
  touchscreen, but topbar and dock still accept input

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1763940] Re: Pressing Print Screen in keyboard makes Rhythmbox go to sleep

2019-01-16 Thread Daniel van Vugt
** Description changed:

+ https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/8
+ 
+ ---
+ 
  Steps:
  
  1. Start Rhythmbox and play music
  2. Press Print Screen in keyboard
  3. Music stops and cannot be played again in Rhythmbox
  4. If the music does not stop from the first time try step 2 again and again 
until it stops
  
  I can navigate the UI of Rhythmbox, but I cannot play music. I have to
  kill the sleeping process in order to play music.
  
  I can reproduce this bug in Totem and Clementine too.
  
  Clementine and Totem present this error:
  
  pa_stream_writable_size() failed: Connection terminated
  
  This bug affects Bionic too.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  amr9438 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  amr9438 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 14 14:42:55 2018
  InstallationDate: Installed on 2017-06-21 (296 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-07-04T15:49:08
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2017-06-22T13:08:09

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

Title:
  Pressing Print Screen in keyboard makes Rhythmbox go to sleep

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-01-16 Thread Daniel van Vugt
Interesting that I don't see any reports of this bug from 18.10 and
later. Is that correct?

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1799714] Re: gnome-shell crashed with SIGTRAP in gjs_callback_closure() from ffi_closure_unix64_inner() from ffi_closure_unix64() from _meta_idle_monitor_watch_fire() from idle_monitor_dispatch_t

2019-01-16 Thread Daniel van Vugt
** Tags added: disco

** Tags added: bionic

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

Title:
  gnome-shell crashed with SIGTRAP in gjs_callback_closure() from
  ffi_closure_unix64_inner() from ffi_closure_unix64() from
  _meta_idle_monitor_watch_fire() from idle_monitor_dispatch_timeout()
  while logging {"Function IdleMonitorWatchFunc terminated with
  uncatchable exception"}

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1812132] [NEW] Does not return results with files that have hyphens in the filename

2019-01-16 Thread Alex Cabal
Public bug reported:

On Ubuntu 18.04 using the `vanilla-gnome-desktop` session (i.e. Gnome
Shell), tracker does not return any files if there is a hyphen (-) in
the search string.

To recreate:

- Create a file named `foo-bar`.

- Press  to open Overview.

- Type foo. Observe that the `foo-bar` file appears.

- Type foo-. Observe that the overview says "No results."

This is a regression as files with hyphens in the filename were included
in search results in 16.04.

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

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

Title:
  Does not return results with files that have hyphens in the filename

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2019-01-16 Thread Jefferson H. Xavier
Same issue in here on Ubuntu 18.04.1 LTS. I have a Dell G3 3579 with Nvidia 
Geforce 1050TI. I've tried to use a Samsung SmartTV as a secondary display 
connected to HDMI port but Gnome settings only shows laptop display. I've 
tested drivers 390, 396, 410, and 415 without success. This issue doesn't 
occurs using lightdm instead of gdm3.
I think developers have to solve this issue that has been reporting since 
2017-09-13 and people who wants do use a external HDMI TV/Monitor to play 
games, like me, will face this issue.

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

Title:
  gdm3, hybrid nvidia with modeset=1, no external monitors detected

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1730229] Re: Desktop stops accepting input from mouse, keyboard, touchpad, or touchscreen, but topbar and dock still accept input

2019-01-16 Thread Mike Willems
*** This bug is a duplicate of bug 1181666 ***
https://bugs.launchpad.net/bugs/1181666

And, ftr, I agree that the duplicate status is wrong!

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

Title:
  Desktop stops accepting input from mouse, keyboard, touchpad, or
  touchscreen, but topbar and dock still accept input

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1730229] Re: Desktop stops accepting input from mouse, keyboard, touchpad, or touchscreen, but topbar and dock still accept input

2019-01-16 Thread Mike Willems
*** This bug is a duplicate of bug 1181666 ***
https://bugs.launchpad.net/bugs/1181666

Hi Justin, did you ever find a resolution to this? I'm on 18.04
experiencing the exact same issue.

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

Title:
  Desktop stops accepting input from mouse, keyboard, touchpad, or
  touchscreen, but topbar and dock still accept input

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1812125] [NEW] Xubuntu 18.04 LTS had no gvfs-bin installed by default, as a result until manually installed, icons get disarranged every reboot in other PC configurations

2019-01-16 Thread David Gil
Public bug reported:

lsb_release -rd

Description:Ubuntu 18.04.1 LTS
Release:18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gvfs-bin 1.36.1-0ubuntu1.2
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jan 17 06:23:36 2019
InstallationDate: Installed on 2019-01-16 (0 days ago)
InstallationMedia: Moment Plus OS amd64 3.8.0 "Gratitude" (20181126)
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

(NOTE: This used a custom version of Xubuntu but the screenshot came
direct from the official Xubuntu version "xubuntu-18.04.1-desktop-
amd64.iso")

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


** Tags: amd64 apport-bug bionic

** Attachment added: "xubuntu-18.04.1-livediskSrc-bug.png"
   
https://bugs.launchpad.net/bugs/1812125/+attachment/5229781/+files/xubuntu-18.04.1-livediskSrc-bug.png

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

Title:
  Xubuntu 18.04 LTS had no gvfs-bin installed by default, as a result
  until manually installed, icons get disarranged every reboot in other
  PC configurations

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1812125] Re: Xubuntu 18.04 LTS had no gvfs-bin installed by default, as a result until manually installed, icons get disarranged every reboot in other PC configurations

2019-01-16 Thread David Gil
(NOTICE: This used a custom version of Xubuntu)

** Description changed:

  lsb_release -rd
  
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-bin 1.36.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jan 17 06:23:36 2019
  InstallationDate: Installed on 2019-01-16 (0 days ago)
  InstallationMedia: Moment Plus OS amd64 3.8.0 "Gratitude" (20181126)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
+ 
+ (NOTE: This used a custom version of Xubuntu but the screenshot came
+ direct from the official Xubuntu version "xubuntu-18.04.1-desktop-
+ amd64.iso")

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

Title:
  Xubuntu 18.04 LTS had no gvfs-bin installed by default, as a result
  until manually installed, icons get disarranged every reboot in other
  PC configurations

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1085706] Re: pam_ecryptfs: seteuid error

2019-01-16 Thread Alexander McColl
Affected on Mint 19.1 running i3lock
locks and unlocks fine, but systemd reports:

"pam_ecryptfs: seteuid error"

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

Title:
  pam_ecryptfs: seteuid error

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1665554] Re: Rhythmbox GUI is flickering and not usable

2019-01-16 Thread Sebastien Bacher
Thank you for your bug report, is that still an issue in newer Ubuntu
versions?

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

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

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

Title:
  Rhythmbox GUI is flickering and not usable

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1750141] Re: rhythmbox crashed with SIGABRT in g_assertion_message()

2019-01-16 Thread Sebastien Bacher
https://errors.ubuntu.com/problem/edc91a5e55a32a4483bcf051a36a7c7b8123cbf3

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

Title:
  rhythmbox crashed with SIGABRT in g_assertion_message()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1737741] Re: rhythmbox-client --seek fails at more than 2148 seconds

2019-01-16 Thread Sebastien Bacher
Upstream is https://gitlab.gnome.org/GNOME/rhythmbox/issues/1618

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

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

Title:
  rhythmbox-client --seek fails at more than 2148 seconds

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725480] Re: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

2019-01-16 Thread Sebastien Bacher
https://errors.ubuntu.com/problem/8ae0367905ba05bf620d0194fb83f741a7e717de

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

Title:
  rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1763940] Re: Pressing Print Screen in keyboard makes Rhythmbox go to sleep

2019-01-16 Thread Sebastien Bacher
** Changed in: rhythmbox (Ubuntu)
   Status: New => Invalid

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

Title:
  Pressing Print Screen in keyboard makes Rhythmbox go to sleep

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1760345] Re: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

2019-01-16 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1725480 ***
https://bugs.launchpad.net/bugs/1725480

** This bug is no longer a duplicate of private bug 1726398
** This bug has been marked a duplicate of bug 1725480
   rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

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

Title:
  rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1761367] Re: found solution rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

2019-01-16 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1725480 ***
https://bugs.launchpad.net/bugs/1725480

** This bug is no longer a duplicate of private bug 1726398
** This bug has been marked a duplicate of bug 1725480
   rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

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

Title:
  found solution rhythmbox crashed with SIGSEGV in
  gtk_tree_view_get_column()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1790624] Re: rhythmbox periodically hangs during playback via SFTP

2019-01-16 Thread Sebastien Bacher
Thank you for your bug report. How is the sftp mounting done? Do you use the 
gvfs location or a fuse mount or similar? Can you access/Read from that mount 
using e.g nautilus when rhythmbox is blocking?
In any case that's probably an upstream issue and should be reported on 
https://gitlab.gnome.org/GNOME/rhythmbox/issues/new

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

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

Title:
  rhythmbox periodically hangs during playback via SFTP

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1768364] Re: Combo boxes close immediately after opening

2019-01-16 Thread Sebastien Bacher
** Changed in: rhythmbox (Ubuntu)
   Status: New => Invalid

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

Title:
  Combo boxes close immediately after opening

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1768364/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1780444] Re: rhythmbox on Ubuntu 18.04 does not adopt CSD even when default alternative toolbar plugin is ON

2019-01-16 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1720649 ***
https://bugs.launchpad.net/bugs/1720649

** This bug has been marked a duplicate of bug 1720649
   unity patch makes a menubar displays when GNOME-app-menu is disabled

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

Title:
  rhythmbox on Ubuntu 18.04 does not adopt CSD even when default
  alternative toolbar plugin is ON

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1775909] Re: Anytime when i start the Programm. It Closed and Crashed

2019-01-16 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

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

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

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

Title:
  Anytime when i start the Programm. It Closed and Crashed

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1788005] Re: print-playing-formats %aa and %aA report wrong value

2019-01-16 Thread Sebastien Bacher
Thanks, that has been now reported upstream on
https://gitlab.gnome.org/GNOME/rhythmbox/issues/1688

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

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

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

Title:
  print-playing-formats %aa and %aA report wrong value

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

2019-01-16 Thread Sebastien Bacher
the gnome-shell error is a bit weird, maybe there is an issue on this
component

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

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

2019-01-16 Thread Sebastien Bacher
Could those having the issue add their journalctl log from the boot
which showed the bug? Also comment #6 is about
org.gnome.SettingsDaemon.Keyboard.desktop which is a different component
(and it looks like xorg got issue and that impacted other components
too)

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

Title:
  Unrecoverable failure in required component
  org.gnome.SettingsDaemon.Color.desktop

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1812014] Re: keyboard not responding after suspend after some time plus performance problem

2019-01-16 Thread Sebastien Bacher
the description sounds a bit similar to bug #1807056

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

Title:
  keyboard not responding after suspend after some time plus performance
  problem

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1803527] Re: ubuntu 18.10 fails to restore from suspend if no password

2019-01-16 Thread Fusion
I manage to record the crash. I resume from suspend 5 hours later (pc
was suspended for about 5h) and the following behavior happened:

First video: exactly after I resume from suspend. I can press buttons but 
nothing happens. Finally I press suspend again.
https://mega.nz/#!joQ0WK7Q!5dXLMBzUr3yboqH5k6FtoeIIN3JDwVBGbKBzPLLErCI


Second video: I resume after a few seconds from the previous suspend (video 1). 
Ubuntu were not responding at all. When I move the mouse screen opens in black 
and then closes again. Also ctrl+alt+F1 does not work.
https://mega.nz/#!CkIGGKrY!mu5P4eW0275oJuxwv7CI7-flJUJgExqADVfP07XIdTU

I also tried to copy as more lines as I could from the results of
"journalctl -b 0" command on terminal. The results are here:
https://pastebin.com/PCccKQDh

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

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

Title:
  ubuntu 18.10 fails to restore from suspend if no password

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-01-16 Thread Lev Levchenko
And bug reproduces again. +WIN key blocked again at that moment.
Interesting observation: unplug-plug mouse helps, hit becomes correct and WIN 
key working again.

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 937054] Re: Allow renaming all files when copying or moving files

2019-01-16 Thread Helder
Reported at https://gitlab.gnome.org/GNOME/nautilus/issues/835.

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

Title:
  Allow renaming all files when copying or moving files

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1812014] [NEW] keyboard not responding after suspend after some time plus performance problem

2019-01-16 Thread Krzysztof
Public bug reported:

I work on Lenovo laptop y-700. When I resume system after suspend,
keyboards stop working, and sometimes there are performance problems
visible when playing videos. It happens not immediately but after a few
minutes or even a few hours of working. Restart or shutdown does not
finish correctly and I need to hold the power button for a few seconds.

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

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

Title:
  keyboard not responding after suspend after some time plus performance
  problem

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

2019-01-16 Thread Andrei
Happens to me as well with the same error. Thought it might be related
to the Nvidia driver, but the initial reporter clearly mentions it only
started to happen after upgrading to 18.04. Have any of you guys managed
to track down the issue or find a workaround?

Thanks!

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

Title:
  Unrecoverable failure in required component
  org.gnome.SettingsDaemon.Color.desktop

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1809092] Re: gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR: Error: No valid stylesheet found for 'Yaru/gnome-shell.css'

2019-01-16 Thread Christian Sarrasin
Hi Daniel,

Thanks to the pointer.  I now have 3.30.1-2ubuntu1.18.10.2 and it seems
the issue is resolved (not sure if this is the new version or the manual
fix below, which I applied thanks to your pointer).

I'd installed the Pop theme manually (through apt) atop stock 18.10.
The slightly unorthodox thing I'd done was a soft-link from /usr/share
/gnome-shell/theme/Yaru/gnome-shell.css onto ../gnome-shell.css, which
is itself a soft-link to /usr/share/themes/Pop/gnome-shell/gnome-
shell.css  This would consistent theming of the lock screen, which
doesn't appear to obey the control panel setting.  Using the soft-links
also makes it easier to spot when those files get overwritten by
updates.

So it looks like the changes introduced in 3.30.1-2ubuntu1.18.10.1 makes
it impossible to follow symlinks from /usr/share/gnome-shell/theme/Yaru
/gnome-shell.css ?  I guess it's perhaps debatable whether the standard
gnome-shell package should reference a hardcoded theme (or maybe that's
a GNOME limitation?)

Anyway, since I've worked around this issue, I guess this bug can be
closed.

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

Title:
  gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR:
  Error: No valid stylesheet found for 'Yaru/gnome-shell.css'

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1726688] Re: totem media player in the Ubuntu dock right click menu does not work, rewind does not work, nor full screen works

2019-01-16 Thread Jeremy Bicha
Yes, verifying the SRU requires verifying that the .desktop works and
that the Actions work.

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

Title:
  totem media player in the Ubuntu dock right click menu does not work,
  rewind does not work, nor full screen works

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1799430] Re: Icon dock visible on lock screen

2019-01-16 Thread MN
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383

effects me either :/ the dock is visible, and extensions are not re-
enabled after login...

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

Title:
  Icon dock visible on lock screen

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1726688] Please test proposed package

2019-01-16 Thread Robie Basak
Hello David, or anyone else affected,

Accepted totem into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/totem/3.26.0-0ubuntu6.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: totem (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-cosmic

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

Title:
  totem media player in the Ubuntu dock right click menu does not work,
  rewind does not work, nor full screen works

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1726688] Please test proposed package

2019-01-16 Thread Robie Basak
Hello David, or anyone else affected,

Accepted totem into cosmic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/totem/3.26.2-1ubuntu3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  totem media player in the Ubuntu dock right click menu does not work,
  rewind does not work, nor full screen works

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1726688] Re: totem media player in the Ubuntu dock right click menu does not work, rewind does not work, nor full screen works

2019-01-16 Thread Robie Basak
Accepting, but "there isn't really any regression risk here" isn't OK as
documented at https://wiki.ubuntu.com/StableReleaseUpdates - see "It's
just a one-line change!" and the documentation of this entry in the
Procedure section. Please could you fix this?

For example, what if this SRU inadvertently breaks
data/org.gnome.Totem.desktop.in.in somehow (eg. a syntax error that
we've missed)? Or if we trigger some latent bug by expanding src/totem-
menu.c:app_entries? During SRU verification, can we make sure that the
existing functionality being modified here still works?

** Changed in: totem (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  totem media player in the Ubuntu dock right click menu does not work,
  rewind does not work, nor full screen works

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

2019-01-16 Thread Josh Holland
Removing gstreamer1.0-vaapi doesn't appear to help.

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

Title:
  Tearing and/or flickering when using Intel graphics

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

2019-01-16 Thread Josh Holland
** Attachment added: "Output of `vainfo`"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229623/+files/vainfo

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

Title:
  Tearing and/or flickering when using Intel graphics

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

2019-01-16 Thread Josh Holland
** Attachment added: "Output of `lspci -k`"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229624/+files/lspci

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

Title:
  Tearing and/or flickering when using Intel graphics

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

2019-01-16 Thread Josh Holland
** Attachment added: "Output of `lscpu`"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229622/+files/lscpu

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

Title:
  Tearing and/or flickering when using Intel graphics

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1803527] Re: ubuntu 18.10 fails to restore from suspend if no password

2019-01-16 Thread Fusion
ps. there is a catch. Since my previous comment I am trying to reproduce
the error. In the beginning it asks password no matter what. After that
I tried this: "gsettings set org.gnome.desktop.screensaver ubuntu-lock-
on-suspend false" that I found it here:
"https://askubuntu.com/questions/1029696/disable-password-request-from-
from-suspend-18-04". So the password is gone again. But I test it
without addons installed (as in the first place (with the photo of my
screen I sent above) and with the two addons I use (Advanced Volume
Mixer by Hatell and GSConnect by andyholmes). The problem seems not to
be reproducible. Although today morning as the day before, it was there.
I suspend and resume over 10 times now, and it seems to be ok. I will
try to let it more on stand by and let you know (I cannot understand the
causes - like no logic at all).

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

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

Title:
  ubuntu 18.10 fails to restore from suspend if no password

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1807056] Re: Occasional Keyboard freeze

2019-01-16 Thread Dilip
As suggested by @Daniel, I have removed all extensions and been using
default Ubuntu DE all day. Sadly, the keyboard freeze is annoyingly
present in default Ubuntu session as well.The workaround fixes the issue
as discussed before.

PS : I also removed the Yaru install through Ubuntu Software to make
sure that it is not interfering. The freeze is still there, but much
less annoying than in the Yaru session.

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

Title:
  Occasional Keyboard freeze

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1441474] Re: gnome-keyring-daemon uses a lot of memory

2019-01-16 Thread James Niland
This is for Ubuntu-gnome
DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"
that also uses gnome shell although I am not sure why as it seems it does not 
work either
Both Opera browser and any version of Chrome or google-chrome demand it. 
However at start just below gnome-panel it is the second highest use of memory 
at startup. Currently sitting at over 32Mb real and 384 virtual memory. There 
is only one login is [Passwords and Keys]. Others seem unhappy with 1mb of ram, 
I however wish I could get it this low.
/usr/bin/gnome-keyring-daemon --daemonize --login is the command loaded.
Version gnome-keyring 3.10.1-1ubuntu4.3
Killing the process my system is entirely more responsive

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

Title:
  gnome-keyring-daemon uses a lot of memory

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 340668] Re: bug opening a new shell tab

2019-01-16 Thread Paul White
Bug did not expire due assignment
Report almost 10 years old and refers to GNOME 2


** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/340668

Title:
  bug opening a new shell tab

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1779615] Re: Shell text and some icons have sharp edges during zoom

2019-01-16 Thread Treviño
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)

** Changed in: mutter (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Shell text and some icons have sharp edges during zoom

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_

2019-01-16 Thread Treviño
** Changed in: mutter (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell crashed with SIGSEGV in
  cogl_texture_get_height(texture=0x0) from
  clutter_offscreen_effect_real_paint_target() from
  clutter_offscreen_effect_paint_texture() from
  clutter_offscreen_effect_paint() from clutter_actor_continue_paint()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect

2019-01-16 Thread Treviño
** Changed in: mutter (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell assert failure: double free or corruption (fasttop) in
  g_free() from g_error_free() from cogl_error_free() from
  cogl_texture_new_with_size() from
  clutter_offscreen_effect_real_create_texture()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1803527] Re: ubuntu 18.10 fails to restore from suspend if no password

2019-01-16 Thread Fusion
ps. on /var/crash there is only a "_user_bin_variety.1000.crash" and
some variety and rhythmbox .uploaded

With the "journalctl -b 0" log may I have a little more details? I
should suspend, return and then ctrl+alt+F1 , login and write
"journalctl -b 0" on terminal? how can I export it on file? or just
copy-paste the results? Thanks again and forgive my ignorance.

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

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

Title:
  ubuntu 18.10 fails to restore from suspend if no password

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1803527] Re: ubuntu 18.10 fails to restore from suspend if no password

2019-01-16 Thread Fusion
This is not the same bug. After resuming from suspend with a new
installation of ubuntu 18.10 and no extensions installed this happened:

https://i.postimg.cc/XJqGb1xy/photo-2019-01-16-11-54-12.jpg

The left panel is over the purple-like lock screen and unusable (the only thing 
is that icons illuminate with mouse movement but they don't respond on click.
The top panel respond but it has only suspend option enabled.

So, the solution for me is:
1. ctrl+alt+F1 , put my password and see all opened windows once again (without 
restart)
2. restart
3. enable asking password after suspend*


*to explain that (because of the other bug): 
The change I did is to disable from gnome-settings the privacy/lock 
screen/automatic lock screen option.

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

Title:
  ubuntu 18.10 fails to restore from suspend if no password

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1811717] Re: Changing Dock icon size (Settings-Dock-Icon size) the icons on desktop disappear

2019-01-16 Thread Iain Lane
thx

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Changing Dock icon size (Settings-Dock-Icon size) the icons on desktop
  disappear

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1810929] Re: totem crashed with SIGSEGV in_cogl_context_get_gl_extensions() from _cogl_driver_update_features() from _cogl_winsys_context_init()

2019-01-16 Thread Daniel van Vugt
** Changed in: cogl (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  totem crashed with SIGSEGV in_cogl_context_get_gl_extensions() from
  _cogl_driver_update_features() from _cogl_winsys_context_init()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1810929] Re: totem crashed with SIGSEGV in_cogl_context_get_gl_extensions() from _cogl_driver_update_features() from _cogl_winsys_context_init()

2019-01-16 Thread preethi
Thank you Daniel!

Reinstalling the nvidia-340 driver resolved the issue.

It was causing us a significant delay in our work. Thank you for helping
in resolution.

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

Title:
  totem crashed with SIGSEGV in_cogl_context_get_gl_extensions() from
  _cogl_driver_update_features() from _cogl_winsys_context_init()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs