[Desktop-packages] [Bug 2019976] [NEW] gdm3(8) manual page is actually gdm-screenshot

2023-05-17 Thread Valery Ushakov
Public bug reported:

There is no manual page for gdm3.

The one that is shipped:

$ dpkg-query -S /usr/share/man/man8/gdm3.8.gz 
gdm3: /usr/share/man/man8/gdm3.8.gz

is actually

$ man gdm3 | sed 1q
GDM-SCREENSHOT.1(8)Debian GNU/LinuxGDM-SCREENSHOT.1(8)

(also note bogus .1 at the end of the man page title name).

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

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

Title:
  gdm3(8) manual page is actually gdm-screenshot

Status in gdm3 package in Ubuntu:
  New

Bug description:
  There is no manual page for gdm3.

  The one that is shipped:

  $ dpkg-query -S /usr/share/man/man8/gdm3.8.gz 
  gdm3: /usr/share/man/man8/gdm3.8.gz

  is actually

  $ man gdm3 | sed 1q
  GDM-SCREENSHOT.1(8)Debian GNU/LinuxGDM-SCREENSHOT.1(8)

  (also note bogus .1 at the end of the man page title name).

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


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


[Desktop-packages] [Bug 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::

2022-12-04 Thread Valery Ushakov
I get this when moving my Lenovo T450 between docking stations, one of
them with an external display connected.  In general an external monitor
connected to a docking station seems to be the source of much pain for
22.04LTS (wayland).  The other docking station also used to have a small
external display connected to it that I used to extend the desktop.  I
had to disconnect it, b/c the system was rather unstable and sluggish
with occasional bursts of log spam that required reboot.

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

Title:
  gnome-shell fills syslog: Attempting to run a JS callback during
  garbage collection. This is most likely caused by destroying a Clutter
  actor or GTK widget with ::destroy signal connected, or using the
  destroy(), dispose(), or remove() vfuncs. Because it would crash the
  application, it has been blocked. The offending callback was
  SourceFunc().

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

Bug description:
  Issue is explained in detail here:
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Dec 16 18:56:56 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-01 (258 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym...

2022-10-19 Thread Valery Ushakov
Ubuntu 22.04.  I get this burst of warnings (> 1K of log) for keys <1>
to <9> every time I switch keyboard layout.  It's spamming syslog to the
point of making it useless (8K+ lines of this in the last couple of
days).

What is the point of this warning? The binding is not actually even
changed according to the log!  Something rebinds the number keys (<1>,
<2>, etc) to the keysyms for the digits (0x31, ...) again - why is this
not at notice or debug level?  This is probably some issue in xkb maps
or something - why wear down SSD and battery?

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

Title:
  Window manager warning: Overwriting existing binding of keysym...

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) Gnome 3.34.1
  3) No error.
  4) Error in Ubuntu Logs App.

  Sender: gnome-shell
  Message:
  4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 
GMT-0600 (CST)
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 37 with keysym 37 (keycode 10).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 36 with keysym 36 (keycode f).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 35 with keysym 35 (keycode e).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 34 with keysym 34 (keycode d).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 32 with keysym 32 (keycode b).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 39 with keysym 39 (keycode 12).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 33 with keysym 33 (keycode c).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 38 with keysym 38 (keycode 11).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 31 with keysym 31 (keycode a).
  Audit Session: 2
  Priority: 6

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


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


[Desktop-packages] [Bug 1856908] [NEW] [80SY, Realtek ALC236, Speaker, Internal] Playback problem

2019-12-18 Thread Valery Frolov
Public bug reported:

$lsb_release -rd
Description:Ubuntu 16.04.6 LTS
Release:16.04

$uname -a
Linux fvg 4.15.0-73-generic #82~16.04.1-Ubuntu SMP Tue Dec 3 17:36:08 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

audacious: 3.6.2-2

What happened:
Sometimes my Lenovo v310 freezes completely while playing music (Audacious).
This is something i found in syslog.


Dec 19 03:01:53 localhost kernel: [12615.593931] [ cut here 
]
Dec 19 03:01:53 localhost kernel: [12615.593947] WARN_ON(fbc->active)
Dec 19 03:01:53 localhost kernel: [12615.594285] WARNING: CPU: 0 PID: 14771 at 
/build/linux-hwe-BQMZOc/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_fbc.c:1136 
intel_fbc_enable+0x3ed/0x570 [i915]
Dec 19 03:01:53 localhost kernel: [12615.594289] Modules linked in: ccm rfcomm 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep rtsx_usb_ms memstick intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel kvm 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
snd_hda_codec_realtek snd_hda_codec_generic arc4 aesni_intel aes_x86_64 
crypto_simd glue_helper cryptd snd_soc_skl intel_cstate intel_rapl_perf 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep iwlmvm mac80211 snd_pcm uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_seq_midi 
snd_seq_midi_event videobuf2_core joydev snd_rawmidi input_leds videodev 
serio_raw snd_seq media wmi_bmof snd_seq_device
Dec 19 03:01:53 localhost kernel: [12615.594456]  intel_wmi_thunderbolt 
snd_timer iwlwifi snd soundcore cfg80211 shpchp intel_pch_thermal mei_me mei 
btusb btrtl btbcm btintel bluetooth ecdh_generic mac_hid ideapad_laptop 
sparse_keymap acpi_pad parport_pc ppdev lp parport autofs4 hid_generic 
rtsx_usb_sdmmc usbhid hid rtsx_usb i915 i2c_algo_bit drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops psmouse r8169 drm mii ahci libahci wmi video
Dec 19 03:01:53 localhost kernel: [12615.594572] CPU: 0 PID: 14771 Comm: 
kworker/u8:0 Tainted: G   OE4.15.0-73-generic #82~16.04.1-Ubuntu
Dec 19 03:01:53 localhost kernel: [12615.594576] Hardware name: LENOVO 80SY/, 
BIOS 0ZCN30WW 12/08/2016
Dec 19 03:01:53 localhost kernel: [12615.594768] Workqueue: events_unbound 
intel_atomic_commit_work [i915]
Dec 19 03:01:53 localhost kernel: [12615.594953] RIP: 
0010:intel_fbc_enable+0x3ed/0x570 [i915]
Dec 19 03:01:53 localhost kernel: [12615.594960] RSP: 0018:c23fc1367cb0 
EFLAGS: 00010286
Dec 19 03:01:53 localhost kernel: [12615.594969] RAX:  RBX: 
a06e2a00 RCX: 97e63a28
Dec 19 03:01:53 localhost kernel: [12615.594974] RDX: 0001 RSI: 
0082 RDI: 0202
Dec 19 03:01:53 localhost kernel: [12615.594979] RBP: c23fc1367d00 R08: 
fffa734938d0 R09: 
Dec 19 03:01:53 localhost kernel: [12615.594984] R10: c23fc30e38e8 R11: 
0367 R12: a06c56299000
Dec 19 03:01:53 localhost kernel: [12615.594989] R13: a06d4cbd6b00 R14: 
a06c5629f000 R15: a06e2a00
Dec 19 03:01:53 localhost kernel: [12615.594997] FS:  () 
GS:a06e3ec0() knlGS:
Dec 19 03:01:53 localhost kernel: [12615.595003] CS:  0010 DS:  ES:  
CR0: 80050033
Dec 19 03:01:53 localhost kernel: [12615.595008] CR2: e1ad9000 CR3: 
000210a0a001 CR4: 003626f0
Dec 19 03:01:53 localhost kernel: [12615.595012] Call Trace:
Dec 19 03:01:53 localhost kernel: [12615.595197]  ? 
intel_pre_plane_update+0x12f/0x190 [i915]
Dec 19 03:01:53 localhost kernel: [12615.595371]  intel_update_crtc+0x75/0xa0 
[i915]
Dec 19 03:01:53 localhost kernel: [12615.595526]  skl_update_crtcs+0x1a9/0x1f0 
[i915]
Dec 19 03:01:53 localhost kernel: [12615.595663]  
intel_atomic_commit_tail+0x3c8/0xe00 [i915]
Dec 19 03:01:53 localhost kernel: [12615.595676]  ? __switch_to+0x9b/0x4e0
Dec 19 03:01:53 localhost kernel: [12615.595687]  ? __switch_to_asm+0x35/0x70
Dec 19 03:01:53 localhost kernel: [12615.595819]  
intel_atomic_commit_work+0x12/0x20 [i915]
Dec 19 03:01:53 localhost kernel: [12615.595830]  process_one_work+0x14d/0x410
Dec 19 03:01:53 localhost kernel: [12615.595839]  worker_thread+0x4b/0x460
Dec 19 03:01:53 localhost kernel: [12615.595853]  kthread+0x105/0x140
Dec 19 03:01:53 localhost kernel: [12615.595861]  ? process_one_work+0x410/0x410
Dec 19 03:01:53 localhost kernel: [12615.595867]  ? kthread_bind+0x40/0x40
Dec 19 03:01:53 localhost kernel: [12615.595878]  ret_from_fork+0x35/0x40
Dec 19 03:01:53 localhost kernel: [12615.595885] Code: 4a 03 00 00 00 0f 84 55 
01 00 00 80 bb ca 2c 00 00 00 0f 84 1c ff ff ff 48 c7 c6 5e 54 5e c0 48 c7 c7 
44 54 5e c0 e8 a3 f0 52 d6 <0f> 0b e9 02 ff ff ff 3d 00 08 00 00 ba 00 08 00 00 
0f 4f c2 e9 
Dec 19 03:01:53 localhost kernel: [12615.596031] ---[ end trace 
4627cd6bd9d494bf ]---

ProblemType: Bug

[Desktop-packages] [Bug 1712200] Re: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland

2017-09-26 Thread Valery
** Also affects: firefox
   Importance: Undecided
   Status: New

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

Title:
  Changing keyboard layout with alt+shift always triggers
  "ui.key.menuAccessKey" on Wayland

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  I'm on Ubuntu 17.10 with artful-proposed enabled.

  Changing keyboard layout with alt+shift always triggers "show menu"on
  Wayland, which makes firefox unusable for users who don't know how to
  disable the value "ui.key.menuAccessKeyFocuses" from about:config.

  Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses"
  to false  by default?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 54.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  thanos25842 F pulseaudio
   /dev/snd/controlC0:  thanos25842 F pulseaudio
   /dev/snd/controlC1:  thanos25842 F pulseaudio
  BuildID: 20170616154447
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Mon Aug 21 23:42:26 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-08-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  IpRoute:
   default via 192.168.2.1 dev wlp4s7 proto static metric 600 
   169.254.0.0/16 dev wlp4s7 scope link metric 1000 
   192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/09/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7d
  dmi.board.name: GA-970A-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-970A-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Desktop-packages] [Bug 1575139] Re: in gedit app search-form close when change language

2016-05-17 Thread Valery
** Description changed:

- search-form closed when change language
+ In gedit app search-form closed when change language
+ 
+ Everything perfectly works in the version gedit 3.4.1
+ The problem is watched in version 3.10.4 and later on Ubuntu 14.04, 15,10 and 
16.04
+ 
+ Problem steps:
+ 1. Open gedit
+ 2. Open search-form (ctrl+s)
+ 3. Change languages from English to Russian or any other languages (alt+shift 
or any other combination key)
+ 4. The window this appears
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 26 14:51:06 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-18 (7 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
-  LANGUAGE=ru
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=ru_RU.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=ru
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=ru_RU.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (4 days ago)

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

Title:
  in gedit app search-form close when change language

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  In gedit app search-form closed when change language

  Everything perfectly works in the version gedit 3.4.1
  The problem is watched in version 3.10.4 and later on Ubuntu 14.04, 15,10 and 
16.04

  Problem steps:
  1. Open gedit
  2. Open search-form (ctrl+s)
  3. Change languages from English to Russian or any other languages (alt+shift 
or any other combination key)
  4. The window this appears

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 26 14:51:06 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-18 (7 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (4 days ago)

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

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


[Desktop-packages] [Bug 1575139] [NEW] in gedit app search-form close when change language

2016-04-26 Thread Valery
Public bug reported:

search-form closed when change language

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gedit 3.18.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 26 14:51:06 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-18 (7 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcEnviron:
 LANGUAGE=ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
UpgradeStatus: Upgraded to xenial on 2016-04-21 (4 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  in gedit app search-form close when change language

Status in gedit package in Ubuntu:
  New

Bug description:
  search-form closed when change language

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 26 14:51:06 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-18 (7 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (4 days ago)

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

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


[Desktop-packages] [Bug 1401484] [NEW] Europe/Moscow timezone if out of date

2014-12-11 Thread Valery Ushakov
Public bug reported:

xul-ext-lightning 1:31.3.0+build1-0ubuntu0.12.04.1 still has old
timezone info for Europe/Moscow:

BEGIN:VTIMEZONE
TZID:Europe/Moscow
X-LIC-LOCATION:Europe/Moscow
BEGIN:STANDARD
TZOFFSETFROM:+0400
TZOFFSETTO:+0400
TZNAME:MSK
DTSTART:19700101T00
END:STANDARD
END:VTIMEZONE

Russia has changed its timezones recently, so Moscow now has 3 hours
delta, not 4.

This have been addressed in tzdata 2014f.

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

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

Title:
  Europe/Moscow timezone if out of date

Status in thunderbird package in Ubuntu:
  New

Bug description:
  xul-ext-lightning 1:31.3.0+build1-0ubuntu0.12.04.1 still has old
  timezone info for Europe/Moscow:

  BEGIN:VTIMEZONE
  TZID:Europe/Moscow
  X-LIC-LOCATION:Europe/Moscow
  BEGIN:STANDARD
  TZOFFSETFROM:+0400
  TZOFFSETTO:+0400
  TZNAME:MSK
  DTSTART:19700101T00
  END:STANDARD
  END:VTIMEZONE

  Russia has changed its timezones recently, so Moscow now has 3 hours
  delta, not 4.

  This have been addressed in tzdata 2014f.

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

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


[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

2013-10-19 Thread Valery Kozlov
Having the same issue. I've upgraded from 13.04 where I had alt+shift toggling 
between En and Ru and belarusian as system language. Current behavior is:
1. I can change layouts between En and Be via alt+shift without updating the 
indicator (but i can see current layout on lock screen).
2. I can change layouts between En and Ru via ctrl+space, but hotkeys on 
russian layout doesn't work.

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Ubuntu:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “indicator-keyboard” package in Ubuntu:
  Confirmed

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

2013-10-18 Thread Valery
** Changed in: indicator-keyboard (Ubuntu)
   Status: Invalid = Confirmed

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Indicator keyboard:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  In Progress
Status in “gnome-settings-daemon” package in Ubuntu:
  In Progress
Status in “indicator-keyboard” package in Ubuntu:
  Confirmed

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+subscriptions

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


[Desktop-packages] [Bug 1232211] [NEW] package gconf2 3.2.6-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed)

2013-09-27 Thread valery karpenko
Public bug reported:

package gconf2 3.2.6-0ubuntu1 failed to install/upgrade: subprocess
installed post-installation script was killed by signal (Killed)

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: gconf2 3.2.6-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Fri Sep 27 22:04:37 2013
DuplicateSignature: package:gconf2:3.2.6-0ubuntu1:subprocess installed 
post-installation script was killed by signal (Killed)
ErrorMessage: subprocess installed post-installation script was killed by 
signal (Killed)
InstallationDate: Installed on 2013-09-11 (16 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130911)
MarkForUpload: True
SourcePackage: gconf
Title: package gconf2 3.2.6-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script was killed by signal (Killed)
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.xdg.autostart.gsettings.data.convert.desktop: 
2013-09-11T18:19:29.867513

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


** Tags: amd64 apport-package saucy

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

Title:
  package gconf2 3.2.6-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script was killed by signal (Killed)

Status in “gconf” package in Ubuntu:
  New

Bug description:
  package gconf2 3.2.6-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script was killed by signal (Killed)

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: gconf2 3.2.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 27 22:04:37 2013
  DuplicateSignature: package:gconf2:3.2.6-0ubuntu1:subprocess installed 
post-installation script was killed by signal (Killed)
  ErrorMessage: subprocess installed post-installation script was killed by 
signal (Killed)
  InstallationDate: Installed on 2013-09-11 (16 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130911)
  MarkForUpload: True
  SourcePackage: gconf
  Title: package gconf2 3.2.6-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script was killed by signal (Killed)
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.gsettings.data.convert.desktop: 
2013-09-11T18:19:29.867513

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

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


[Desktop-packages] [Bug 1224542] [NEW] session termination takes too much time

2013-09-12 Thread valery karpenko
Public bug reported:

session termination takes too much time

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: lightdm 1.7.15-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Thu Sep 12 18:18:07 2013
InstallationDate: Installed on 2013-09-11 (1 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130911)
LightdmConfig:
 [SeatDefaults]
 autologin-guest=false
 autologin-user=valery
 autologin-user-timeout=0
 autologin-session=lightdm-autologin
MarkForUpload: True
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug gnome3-ppa saucy third-party-packages

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

Title:
  session termination takes too much time

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  session termination takes too much time

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.15-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Thu Sep 12 18:18:07 2013
  InstallationDate: Installed on 2013-09-11 (1 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130911)
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user=valery
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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