[Bug 1872681] [NEW] Overview shortcut does not work on non-latin keyboard layout

2020-04-14 Thread Andrew Kornilov
Public bug reported:

Hello,

Latest Ubuntu 20.04.
After latest upgrade the shortcut key for the Overview (Expose?) function 
doesn't work on non-latin keyboard layout:

1. Switch current input language to Russian
2. Press Super key.
3. Nothing happens
4. Switch language to English
5. Press Super key
6. Windows overview screen is opened

/usr/bin/xev reports the same keyscan for the button, if that matters.
Other Super-  shortcuts (like Super-`) do work in any keyboard layout.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-4ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
Uname: Linux 5.4.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 14 13:00:36 2020
DisplayManager: gdm3
InstallationDate: Installed on 2019-12-11 (124 days ago)
InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  Overview shortcut does not work on non-latin keyboard layout

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

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

[Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking

2020-03-06 Thread Andrew Kornilov
My issue has been marked as duplicate of https://gitlab.gnome.org/GNOME
/gnome-shell/issues/2255  which is already fixed 1 week ago.


** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2255
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/2255

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

Title:
  Disabled animations breaks lock screen and other dialogs, reveals
  information from the screen without unlocking

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

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

[Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking

2020-03-06 Thread Andrew Kornilov
HI,

That was my first thought.  However, Focal repo does not provide the latest 
GNOME Shell version, that it might have been already fixed. So i decided to 
report here first.
So i'll report it now.

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

Title:
  Disabled animations breaks lock screen and other dialogs, reveals
  information from the screen without unlocking

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

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

[Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking

2020-03-06 Thread Andrew Kornilov
lcipcik data

** Attachment added: "lspcik.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866256/+attachment/5334235/+files/lspcik.txt

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

Title:
  Disabled animations breaks lock screen and other dialogs, reveals
  information from the screen without unlocking

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

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

[Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking

2020-03-06 Thread Andrew Kornilov
Could some one please test it and confirm? Just disable animation and then lock 
the screen.
That might be my local issue.

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

Title:
  Disabled animations breaks lock screen and other dialogs, reveals
  information from the screen without unlocking

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

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

[Bug 1817389] Re: GIMP icon sizes small on large and huge setting

2020-02-09 Thread Andrew Kornilov
I can confirm that issue on the latest development version of Ubuntu 20, on 
HiDPI 15" display (3840x2160)
flatpak version looks less or more correct (still not very usable) and icon 
size setting works.
repository version has tiny icons and icon size settings does not work.

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

Title:
  GIMP icon sizes small on large and huge setting

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

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

[Bug 1845809] [NEW] Yaru dark is not completely dark after upgrade 19.04 to 19.10

2019-09-28 Thread Andrew Kornilov
Public bug reported:

Yaru-dark worked fine until upgraded from 19.04 to 19.10.
Now some dropdown menus are always light (see the screenshot). 

Tried to change it to light/default and back - did not help.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: yaru-theme-gnome-shell 19.10.3
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 29 00:31:56 2019
Dependencies:
 
InstallationDate: Installed on 2018-11-13 (319 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: yaru-theme
UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)

** Affects: yaru-theme (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

** Attachment added: "sshot.png"
   https://bugs.launchpad.net/bugs/1845809/+attachment/5292392/+files/sshot.png

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

Title:
  Yaru dark is not completely dark after upgrade 19.04 to 19.10

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

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

[Bug 1832959] Re: [hidpi] Cursor is too small after screensaver

2019-09-10 Thread Andrew Kornilov
The problem disappeared after some time.
Just got it now and nothing helped to restore the cursor size, it's very-very 
small.
I tried to change the cursor size using Settings->Universal access 
(https://vitux.com/how-to-change-cursor-size-on-ubuntu-desktop/), but it was 
not changed.

I tried gsettings set org.gnome.desktop.interface cursor-size 32 and also there 
was no reaction.
I tried to Suspend/Resume the notebook, still no success.

Only after pressing the PrintScreen button it immediately get the right
size.

Very strange.

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

Title:
  [hidpi] Cursor is too small after screensaver

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

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

[Bug 1832959] [NEW] Wrong cursor size after screensaver

2019-06-15 Thread Andrew Kornilov
Public bug reported:

Hi all,
I have a HiDPI screen (2880x1620) with 2x scaling (default). Everything worked 
well for months until some of the upgrades broke something.

The problem is with cursor size. It has 2x or even 4x less size (very small) 
after returning from screensaver/locking screen.
So, for example, if i suspend and then resume my laptop or just lock the screen 
and then type the password to unlock.

Curiously, but the problem becomes fixed if i take a screenshot by
pressing Print Screen. In this case the cursor size immediately becomes
the correct size.

Some more tips:

1. If i press Ctrl-Alt-F1 (where the gdm is running) the cursor has correct 
size.
2. If i then press Ctrl-Alt-F2 and switch back to my current session, it again 
becomes 2x-4x less size.

Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 16 00:24:41 2019
DistUpgraded: 2019-04-02 21:54:52,265 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus: nvidia, 430.26, 5.0.0-16-generic, x86_64: installed
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: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor 
Integrated Graphics Controller [1462:10fd]
   Subsystem: Micro-Star International Co., Ltd. [MSI] GK104M [GeForce GTX 
870M] [1462:10fd]
InstallationDate: Installed on 2018-11-13 (214 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Micro-Star International Co., Ltd. GS60 2PE
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=bc6d974d-dac7-4fef-a6ad-c78c6be040e4 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-02 (74 days ago)
dmi.bios.date: 05/13/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16H2IMS.106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16H2
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.B
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.106:bd05/13/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: GS60 2PE
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco ubuntu

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

Title:
  Wrong cursor size after screensaver

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

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

[Bug 665097] Re: X doesn't work with i915 driver

2010-10-26 Thread Andrew Kornilov
I've been googling/reading lots of information, found similar problems,
then discovered kernel OOPS with intel_ips module:

   1.
  [5.985278] Pid: 408, comm: modprobe Not tainted 2.6.35-22-generic 
#35-Ubuntu K52F/K52F
   2.
  [5.985370] EIP: 0060:[f81da452] EFLAGS: 00010286 CPU: 1
   3.
  [5.985433] EIP is at ips_detect_cpu+0x62/0x180 [intel_ips]
   4.
  [5.985498] EAX: 00c800c8 EBX:  ECX: 00c800c8 EDX: 
   5.
  [5.985562] ESI: f5bbfe04 EDI: f69ae500 EBP: f5bbfe14 ESP: f5bbfde4
   6.
  [5.985626]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
   7.
  [5.985688] Process modprobe (pid: 408, ti=f5bbe000 task=f5ac7230 
task.ti=f5bbe000)
   8.
  [5.985778] Stack:
   9.
  [5.986569]  f81dbefc f81dbe9e f70b6c00 f5bbfe14 c020c441 f5bbfe08 
c05c79e9 f81daeef
  10.
  [5.986810] 0  f69ae500 f7168000 fff4 f5bbfe4c f81daf2a 
c027165d f5bbfe4c
  11.
  [5.987123] 0 c0270c07 f5bbfe4c c027100a f5bbfe38 f7168000 f7168060 
c036bb3e f7168000
  12.
  [5.987485] Call Trace:
  13.
  [5.987548]  [c020c441] ? kmem_cache_alloc_notrace+0x91/0xb0
  14.
  [5.987617]  [c05c79e9] ? mutex_lock+0x19/0x40
  15.
  [5.987677]  [f81daeef] ? ips_probe+0x1f/0x690 [intel_ips]
  16.
  [5.987744]  [f81daf2a] ? ips_probe+0x5a/0x690 [intel_ips]
  17.
  [5.987809]  [c027165d] ? sysfs_add_one+0x1d/0x110
  18.
  [5.987872]  [c0270c07] ? sysfs_new_dirent+0x67/0x100
  19.
  [5.987934]  [c027100a] ? sysfs_addrm_finish+0x1a/0xb0
  20.
  [5.988001]  [c036bb3e] ? pci_match_device+0xbe/0xd0
  21.
  [5.988062]  [c036b9d3] ? local_pci_probe+0x13/0x20
  22.
  [5.988125]  [c036c988] ? pci_device_probe+0x68/0x90
  23.
  [5.988188]  [c0400540] ? really_probe+0x50/0x150
  24.
  [5.988253]  [c0407bb7] ? pm_runtime_barrier+0x57/0xb0
  25.
  [5.988316]  [c040067c] ? driver_probe_device+0x3c/0x60
  26.
  [5.988379]  [c0400721] ? __driver_attach+0x81/0x90
  27.
  [5.988441]  [c03ffb43] ? bus_for_each_dev+0x53/0x80
  28.
  [5.988504]  [c040040e] ? driver_attach+0x1e/0x20
  29.
  [5.988565]  [c04006a0] ? __driver_attach+0x0/0x90
  30.
  [5.988625]  [c03ffdd5] ? bus_add_driver+0xd5/0x280
  31.
  [5.988686]  [c036c8c0] ? pci_device_remove+0x0/0x40
  32.
  [5.988751]  [c0400a1a] ? driver_register+0x6a/0x130
  33.
  [5.988812]  [c036cbc5] ? __pci_register_driver+0x45/0xb0
  34.
  [5.988878]  [f81df017] ? ips_init+0x17/0x19 [intel_ips]
  35.
  [5.988942]  [c0101132] ? do_one_initcall+0x32/0x1a0
  36.
  [5.989006]  [f81df000] ? ips_init+0x0/0x19 [intel_ips]
  37.
  [5.989074]  [c0180c2b] ? sys_init_module+0x9b/0x1e0
  38.
  [5.989140]  [c0218fa2] ? sys_write+0x42/0x70
  39.
  [5.989201]  [c05c9114] ? syscall_call+0x7/0xb
  40.
  [5.989262] Code: 1e f5 c7 90 ba f5 bd 1d f8 b8 0c 52 81 c0 e8 a6 f6 
17 c8 bb 80 c4 1d f8 85 c0 74 35 b8 ac 01 00 00 89 f2 e8 b1 1e f5 c7 90 89 c1 
8b 53 08 c1 e1 12 c1 e
  41.
  9 15 69 c1 e8 03 00 00 39 c2 75 75 89 d8
  42.
  [5.991035] EIP: [f81da452] ips_detect_cpu+0x62/0x180 [intel_ips] 
SS:ESP 0068:f5bbfde4
  43.
  [5.991180] CR2: 0008
  44.
  [5.991307] ---[ end trace 4126c52517df4ed9 ]---


Then i added blacklist intel_ips to the local modprobe config and problem has 
been solved.
Actually, it's a workaround rather then solution.

Shall i post here harware info, logs, etc?

-- 
X doesn't work with i915 driver
https://bugs.launchpad.net/bugs/665097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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


[Bug 665097] [NEW] X doesn't work with i915 driver

2010-10-22 Thread Andrew Kornilov
Public bug reported:

We tried to install 10.10 Desktop on the ASUS A52F notebook and failed.
Installation process went without any problems, but after restart X didn't 
start.
I tried to run it by using startx and so on, then i discovered a problem and 
found the same, reported there:

http://ubuntuforums.org/showthread.php?p=9997946

i915: gave up waiting for init of module intel_agp
i915: Unknown symbol intel_agp_enabled (err -16)

It seems to me that i915 kernel module has been incorrectly built or
some modules aren't being loaded.

The hardware is Intel GMA HD.

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

-- 
X doesn't work with i915 driver
https://bugs.launchpad.net/bugs/665097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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