[Desktop-packages] [Bug 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)

2019-12-20 Thread vlad
Same problem on Lenovo Ideapad 320-15IKB

** Changed in: alsa-driver (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  [meta-bug] Inverted Internal microphone (phase inversion)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  This is a metabug for all machines that are having phase inverted
  internal microphones.

  If your internal mic is either completely silent (no signal), or you
  can possibly pick a very small sound, with much background noise, even
  though you have set gain to maximum, there is something you could try.

  Install the pavucontrol application, start it and go to the "Input Devices" 
tab. Unlock the channels (there is a keylock icon), then mute the right channel 
while keeping the left channel at the volume you want.
  If the internal mic is now working correctly, you have an inverted internal 
mic, so that your right channel cancels out the left one.

  (If you're not running PulseAudio, you can try doing the same through
  AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try
  changing "Capture" level or "Internal Mic" or "Internal Mic Boost"
  using the Q,E,Z,C keys.)

  If so, please file a separate bug against the alsa-driver for your
  issue, make sure hardware info gets attached to it (either alsa-info
  as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones
  that follows when you do "ubuntu-bug alsa-driver" ), then write a
  comment in this bug, with your machine name and a pointer to the other
  bug.

  As time permits, I'll try to work on fixing them for the next Ubuntu release. 
Thanks!
   -- David Henningsson

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+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 1056310] [NEW] [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001

2012-09-25 Thread Vlad
Public bug reported:

Apport automatic report

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: xserver-xorg-video-intel 2:2.20.8-0ubuntu1
Uname: Linux 3.6.0-030600rc7-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Chipset: sandybridge-gt1
Date: Tue Sep 25 20:38:50 2012
DistroCodename: quantal
DistroVariant: ubuntu
DuplicateSignature: [sandybridge-gt1] GPU lockup  IPEHR: 0x0b160001 IPEHR: 
0x0b140001 Ubuntu 12.10
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
GpuHangFrequency: Continuously
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120406)
InterpreterPath: /usr/bin/python3.2mu
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:
 
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.6.0-030600rc7-generic 
root=UUID=43bd97ca-8e07-4914-b715-83a427109dda ro rootflags=subvol=@ quiet 
splash elevator=noop ipv6.disable=1 vt.handoff=7
RelatedPackageVersions:
 xserver-xorg 1:7.7+1ubuntu3
 libdrm2  2.4.39-0ubuntu1
 xserver-xorg-video-intel 2:2.20.8-0ubuntu1
SourcePackage: xserver-xorg-video-intel
Title: [sandybridge-gt1] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001
UdevDb: Error: [Errno 2] No such file or directory: 'udevadm'
UpgradeStatus: Upgraded to quantal on 2012-09-25 (0 days ago)
UserGroups:
 
dmi.bios.date: 03/12/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.86A.0151.2012.0312.1138
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH67CL
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10212-208
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0151.2012.0312.1138:bd03/12/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-208:cvn:ct3:cvr:

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash freeze quantal ubuntu

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

Title:
  [sandybridge-gt1] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001

Status in “xserver-xorg-video-intel” package in Ubuntu:
  New

Bug description:
  Apport automatic report

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-intel 2:2.20.8-0ubuntu1
  Uname: Linux 3.6.0-030600rc7-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Chipset: sandybridge-gt1
  Date: Tue Sep 25 20:38:50 2012
  DistroCodename: quantal
  DistroVariant: ubuntu
  DuplicateSignature: [sandybridge-gt1] GPU lockup  IPEHR: 0x0b160001 IPEHR: 
0x0b140001 Ubuntu 12.10
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  GpuHangFrequency: Continuously
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120406)
  InterpreterPath: /usr/bin/python3.2mu
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.6.0-030600rc7-generic 
root=UUID=43bd97ca-8e07-4914-b715-83a427109dda ro rootflags=subvol=@ quiet 
splash elevator=noop ipv6.disable=1 vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu3
   libdrm2  2.4.39-0ubuntu1
   xserver-xorg-video-intel 2:2.20.8-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: [sandybridge-gt1] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001
  UdevDb: Error: [Errno 2] No such file or directory: 'udevadm'
  UpgradeStatus: Upgraded to quantal on 2012-09-25 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0151.2012.0312.1138
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-208
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0151.2012.0312.1138:bd03/12/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-208:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1056310/+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 1056310] Re: [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001

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

Title:
  [sandybridge-gt1] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001

Status in “xserver-xorg-video-intel” package in Ubuntu:
  New

Bug description:
  Apport automatic report

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-intel 2:2.20.8-0ubuntu1
  Uname: Linux 3.6.0-030600rc7-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Chipset: sandybridge-gt1
  Date: Tue Sep 25 20:38:50 2012
  DistroCodename: quantal
  DistroVariant: ubuntu
  DuplicateSignature: [sandybridge-gt1] GPU lockup  IPEHR: 0x0b160001 IPEHR: 
0x0b140001 Ubuntu 12.10
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  GpuHangFrequency: Continuously
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120406)
  InterpreterPath: /usr/bin/python3.2mu
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.6.0-030600rc7-generic 
root=UUID=43bd97ca-8e07-4914-b715-83a427109dda ro rootflags=subvol=@ quiet 
splash elevator=noop ipv6.disable=1 vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu3
   libdrm2  2.4.39-0ubuntu1
   xserver-xorg-video-intel 2:2.20.8-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: [sandybridge-gt1] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001
  UdevDb: Error: [Errno 2] No such file or directory: 'udevadm'
  UpgradeStatus: Upgraded to quantal on 2012-09-25 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0151.2012.0312.1138
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-208
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0151.2012.0312.1138:bd03/12/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-208:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1056310/+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 1056937] [NEW] ALOT of things going wrong at once

2012-09-26 Thread vlad
Public bug reported:

Ok so i'm pretty new to Ubuntu, i got 12.04 LTS, along with my windows 7 
partitioned, everything has been running well for a month or so until i started 
noticing random bugs.
laptop is sony vaio VPCEB26GM


1. Green block of vertical lines on desktop (sounds like graphics problem?)
2. when i close laptop lid, the laptop goes to sleep, but when i open it the 
screen is frozen and i have to do hard restart.
3. Now the desktop icons disappeared and i can't right click the desktop
4. The green block of pixels is happening more frequently and when it does 
everything freezes...

please help i have no clue whats going on, and it feels like someone is
trolling me :(

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

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

Title:
  ALOT of things going wrong at once

Status in “xorg” package in Ubuntu:
  New

Bug description:
  Ok so i'm pretty new to Ubuntu, i got 12.04 LTS, along with my windows 7 
partitioned, everything has been running well for a month or so until i started 
noticing random bugs.
  laptop is sony vaio VPCEB26GM

  
  1. Green block of vertical lines on desktop (sounds like graphics problem?)
  2. when i close laptop lid, the laptop goes to sleep, but when i open it the 
screen is frozen and i have to do hard restart.
  3. Now the desktop icons disappeared and i can't right click the desktop
  4. The green block of pixels is happening more frequently and when it does 
everything freezes...

  please help i have no clue whats going on, and it feels like someone
  is trolling me :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1056937/+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 1056937] Re: ALOT of things going wrong at once

2012-09-26 Thread vlad
** Description changed:

  Ok so i'm pretty new to Ubuntu, i got 12.04 LTS, along with my windows 7 
partitioned, everything has been running well for a month or so until i started 
noticing random bugs.
  laptop is sony vaio VPCEB26GM
- 
  
  1. Green block of vertical lines on desktop (sounds like graphics problem?)
  2. when i close laptop lid, the laptop goes to sleep, but when i open it the 
screen is frozen and i have to do hard restart.
  3. Now the desktop icons disappeared and i can't right click the desktop
  4. The green block of pixels is happening more frequently and when it does 
everything freezes...
  
  please help i have no clue whats going on, and it feels like someone is
  trolling me :(
+ 
+ 
+ Ok so i uninstalled a few dumb apps that i downloaded (ubuntu tweak, and a 
few theme changing ones) 
+ 
+ so far: problem #2 is solved, but i still have no desktop icons, and i
+ can't move stuff to desktop (copy to-> or move to->)

** Description changed:

  Ok so i'm pretty new to Ubuntu, i got 12.04 LTS, along with my windows 7 
partitioned, everything has been running well for a month or so until i started 
noticing random bugs.
  laptop is sony vaio VPCEB26GM
  
  1. Green block of vertical lines on desktop (sounds like graphics problem?)
  2. when i close laptop lid, the laptop goes to sleep, but when i open it the 
screen is frozen and i have to do hard restart.
  3. Now the desktop icons disappeared and i can't right click the desktop
  4. The green block of pixels is happening more frequently and when it does 
everything freezes...
  
  please help i have no clue whats going on, and it feels like someone is
  trolling me :(
  
- 
- Ok so i uninstalled a few dumb apps that i downloaded (ubuntu tweak, and a 
few theme changing ones) 
+ Ok so i uninstalled a few dumb apps that i downloaded (ubuntu tweak, and
+ a few theme changing ones)
  
  so far: problem #2 is solved, but i still have no desktop icons, and i
  can't move stuff to desktop (copy to-> or move to->)
+ 
+ i tried uninstalling ubuntu desktop and redoing sudo apt-get install 
ubuntu-desktop, 
+ nothing changes.
+ 
+ the green bar disappeared but the screen is still freezing if i move the
+ mouse too much :/

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

Title:
  ALOT of things going wrong at once

Status in “xorg” package in Ubuntu:
  New

Bug description:
  Ok so i'm pretty new to Ubuntu, i got 12.04 LTS, along with my windows 7 
partitioned, everything has been running well for a month or so until i started 
noticing random bugs.
  laptop is sony vaio VPCEB26GM

  1. Green block of vertical lines on desktop (sounds like graphics problem?)
  2. when i close laptop lid, the laptop goes to sleep, but when i open it the 
screen is frozen and i have to do hard restart.
  3. Now the desktop icons disappeared and i can't right click the desktop
  4. The green block of pixels is happening more frequently and when it does 
everything freezes...

  please help i have no clue whats going on, and it feels like someone
  is trolling me :(

  Ok so i uninstalled a few dumb apps that i downloaded (ubuntu tweak,
  and a few theme changing ones)

  so far: problem #2 is solved, but i still have no desktop icons, and i
  can't move stuff to desktop (copy to-> or move to->)

  i tried uninstalling ubuntu desktop and redoing sudo apt-get install 
ubuntu-desktop, 
  nothing changes.

  the green bar disappeared but the screen is still freezing if i move
  the mouse too much :/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1056937/+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 980035] Re: seahorse crashes when importing an SSH key. (Assertion Failed/Segfault)

2013-04-03 Thread Vlad
I have the same error.

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

Title:
  seahorse crashes when importing an SSH key. (Assertion
  Failed/Segfault)

Status in “seahorse” package in Ubuntu:
  Confirmed

Bug description:
  While trying to verify if this bug is now fixed, so that it can be
  closed:-

  https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/372608

  I am seeing that infact, the bug above appears to be resolved...
  although now it crashes moments after successfully importing a key,
  this bug is apparently also tracked by redhat here:-

  https://bugzilla.redhat.com/show_bug.cgi?id=751515

  The bug I was originally looking at states that a lot of the import
  code was re-written for seahorse 3.4, so perhaps the solution to this
  is to ask why seahorse is not one of those apps which have been/can be
  rolled forward in 12.04.

  James

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: seahorse 3.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  ApportVersion: 2.0.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 12 17:17:23 2012
  ExecutablePath: /usr/bin/seahorse
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 
(20120228.1)
  ProcEnviron:
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
  SourcePackage: seahorse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/980035/+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 989610] Re: Ubuntu 12.04 fails to install broadcom STA drivers

2012-04-27 Thread Vlad
i confirm, extremely critical, without access to internet on main
computer, help plese

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

Title:
  Ubuntu 12.04 fails to install broadcom STA drivers

Status in “jockey” package in Ubuntu:
  Confirmed

Bug description:
  Jockey fails to properly install broadcom STA wireless drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/989610/+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 916591] [NEW] The browser causes 20-40% CPU load when displaying an animated gif

2012-01-14 Thread Vlad
Public bug reported:

When firefox is displaying a gif, for example
http://i.imgur.com/MVKsc.gif , the CPU is under constant 20-40% load and
system feels to run slower. Same load with and without any addons. When
i remove the element which contains the gif via firebug, the load
instantly drops to 1-2%.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: firefox 9.0.1+build1-0ubuntu0.11.10.2
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
NonfreeKernelModules: wl fglrx
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
  List of CAPTURE Hardware Devices 
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  vlad   1888 F pulseaudio
 /dev/snd/controlC0:  vlad   1888 F pulseaudio
BuildID: 20111228084940
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfbf0 irq 52'
   Mixer name   : 'IDT 92HD81B1X5'
   Components   : 'HDA:111d7605,10280447,00100105'
   Controls  : 14
   Simple ctrls  : 9
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xfbe4 irq 53'
   Mixer name   : 'ATI R6xx HDMI'
   Components   : 'HDA:1002aa01,00aa0100,00100200'
   Controls  : 4
   Simple ctrls  : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Channel: release
Date: Sat Jan 14 22:43:13 2012
ForcedLayersAccel: False
IfupdownConfig:
 auto lo
 iface lo inet loopback
IncompatibleExtensions: LastPass - ID=supp...@lastpass.com, Version=1.80.0, 
minVersion=1.9a2, maxVersion=1.9.6, Location=app-profile, Type=extension, 
Active=Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IpRoute:
 default via 192.168.0.1 dev eth0  proto static 
 169.254.0.0/16 dev eth0  scope link  metric 1000 
 192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.3  metric 1
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=9.0.1/20111228084940 (Running)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/19/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0WK2G6
dmi.board.vendor: Dell Inc.
dmi.board.version: A15
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A15
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd07/19/2011:svnDellInc.:pnInspironN5010:pvrA15:rvnDellInc.:rn0WK2G6:rvrA15:cvnDellInc.:ct8:cvrA15:
dmi.product.name: Inspiron N5010
dmi.product.version: A15
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug oneiric running-unity

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

Title:
  The browser causes 20-40% CPU load when displaying an animated gif

Status in “firefox” package in Ubuntu:
  New

Bug description:
  When firefox is displaying a gif, for example
  http://i.imgur.com/MVKsc.gif , the CPU is under constant 20-40% load
  and system feels to run slower. Same load with and without any addons.
  When i remove the element which contains the gif via firebug, the load
  instantly drops to 1-2%.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 9.0.1+build1-0ubuntu0.11.10.2
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Uname: Linux 3.0.0-14-generic x86_64
  NonfreeKernelModules: wl fglrx
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vlad   1888 F pulseaudio
   /dev/snd/controlC0:  vlad   1888 F pulseaudio
  BuildID: 20111228084940
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfbf0 irq 52'
 Mixer name : 'IDT 92HD81B1X5'
 Components : 'HDA:111d7605,10280447,00100105'
 Controls  : 14
 Simple ctrls  : 9
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xfbe4 irq 53'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,

[Desktop-packages] [Bug 916591] Re: The browser causes 20-40% CPU load when displaying an animated gif

2012-01-14 Thread Vlad
-- 
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/916591

Title:
  The browser causes 20-40% CPU load when displaying an animated gif

Status in “firefox” package in Ubuntu:
  New

Bug description:
  When firefox is displaying a gif, for example
  http://i.imgur.com/MVKsc.gif , the CPU is under constant 20-40% load
  and system feels to run slower. Same load with and without any addons.
  When i remove the element which contains the gif via firebug, the load
  instantly drops to 1-2%.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 9.0.1+build1-0ubuntu0.11.10.2
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Uname: Linux 3.0.0-14-generic x86_64
  NonfreeKernelModules: wl fglrx
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vlad   1888 F pulseaudio
   /dev/snd/controlC0:  vlad   1888 F pulseaudio
  BuildID: 20111228084940
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfbf0 irq 52'
 Mixer name : 'IDT 92HD81B1X5'
 Components : 'HDA:111d7605,10280447,00100105'
 Controls  : 14
 Simple ctrls  : 9
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xfbe4 irq 53'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Channel: release
  Date: Sat Jan 14 22:43:13 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: LastPass - ID=supp...@lastpass.com, Version=1.80.0, 
minVersion=1.9a2, maxVersion=1.9.6, Location=app-profile, Type=extension, 
Active=Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.3  metric 1
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=9.0.1/20111228084940 (Running)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0WK2G6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A15
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A15
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd07/19/2011:svnDellInc.:pnInspironN5010:pvrA15:rvnDellInc.:rn0WK2G6:rvrA15:cvnDellInc.:ct8:cvrA15:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A15
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/916591/+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 865061] [NEW] unable to use digital signatures

2011-10-02 Thread Vlad
Public bug reported:

libreoffice 3.4.3 does not see any personal certificates, even if I manually 
set "MOZILLA_CERTIFICATE_FOLDER" variable.
will someone confirm, this bug is quite nasty.

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

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

Title:
  unable to use digital signatures

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  libreoffice 3.4.3 does not see any personal certificates, even if I manually 
set "MOZILLA_CERTIFICATE_FOLDER" variable.
  will someone confirm, this bug is quite nasty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/865061/+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 1633380] [NEW] package cups-browsed 1.8.3-2ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

2016-10-14 Thread Vlad
Public bug reported:

Help me please

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-browsed 1.8.3-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
Uname: Linux 4.4.0-43-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CupsErrorLog:
 
Date: Fri Oct 14 11:38:58 2016
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
InstallationDate: Installed on 2016-10-12 (1 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E5EV/300E4EV/270E5EV/270E4EV
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=14a9cab6-f083-497f-a700-537d7adbcd31 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: cups-filters
Title: package cups-browsed 1.8.3-2ubuntu3.1 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/03/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P05RBF
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP270E5V-K03RU
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP05RBF:bd05/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5EV/300E4EV/270E5EV/270E4EV:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP270E5V-K03RU:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 300E5EV/300E4EV/270E5EV/270E4EV
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Affects: cups-filters (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package cups-browsed 1.8.3-2ubuntu3.1 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in cups-filters package in Ubuntu:
  New

Bug description:
  Help me please

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-browsed 1.8.3-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Oct 14 11:38:58 2016
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2016-10-12 (1 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E5EV/300E4EV/270E5EV/270E4EV
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=14a9cab6-f083-497f-a700-537d7adbcd31 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: cups-filters
  Title: package cups-browsed 1.8.3-2ubuntu3.1 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P05RBF
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP270E5V-K03RU
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP05RBF:bd05/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5EV/300E4EV/270E5EV/270E4EV:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP270E5V-K03RU:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 300E5EV/300E4EV/270E5EV/270E4EV
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1633380/+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 1658559] [NEW] Sound breaks when I plug headphones [XPS L521X, Realtek ALC3260, Black Headphone Out, Front] No sound at all

2017-01-22 Thread Vlad
Public bug reported:

Sound works until I plug headphones, then it's 50% chance that sound
will mute in headphones. When unplug - sound works fine.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  zman   2187 F pulseaudio
 /dev/snd/controlC0:  zman   2187 F pulseaudio
CurrentDesktop: Unity
Date: Sun Jan 22 20:54:55 2017
InstallationDate: Installed on 2017-01-19 (4 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  zman   2187 F pulseaudio
 /dev/snd/controlC0:  zman   2187 F pulseaudio
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: No sound at all
Title: [XPS L521X, Realtek ALC3260, Black Headphone Out, Front] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/17/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 021YXH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A16
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/17/2013:svnDellInc.:pnXPSL521X:pvrA16:rvnDellInc.:rn021YXH:rvrA00:cvnDellInc.:ct8:cvrA16:
dmi.product.name: XPS L521X
dmi.product.version: A16
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1658559

Title:
  Sound breaks when I plug headphones [XPS L521X, Realtek ALC3260, Black
  Headphone Out, Front] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound works until I plug headphones, then it's 50% chance that sound
  will mute in headphones. When unplug - sound works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zman   2187 F pulseaudio
   /dev/snd/controlC0:  zman   2187 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jan 22 20:54:55 2017
  InstallationDate: Installed on 2017-01-19 (4 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zman   2187 F pulseaudio
   /dev/snd/controlC0:  zman   2187 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [XPS L521X, Realtek ALC3260, Black Headphone Out, Front] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 021YXH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A16
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/17/2013:svnDellInc.:pnXPSL521X:pvrA16:rvnDellInc.:rn021YXH:rvrA00:cvnDellInc.:ct8:cvrA16:
  dmi.product.name: XPS L521X
  dmi.product.version: A16
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1658559/+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 1658559] Re: Sound breaks when I plug headphones [XPS L521X, Realtek ALC3260, Black Headphone Out, Front] No sound at all

2017-01-22 Thread Vlad
** Tags added: headphone-no-sound kernel-sound

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

Title:
  Sound breaks when I plug headphones [XPS L521X, Realtek ALC3260, Black
  Headphone Out, Front] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound works until I plug headphones, then it's 50% chance that sound
  will mute in headphones. When unplug - sound works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zman   2187 F pulseaudio
   /dev/snd/controlC0:  zman   2187 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jan 22 20:54:55 2017
  InstallationDate: Installed on 2017-01-19 (4 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zman   2187 F pulseaudio
   /dev/snd/controlC0:  zman   2187 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [XPS L521X, Realtek ALC3260, Black Headphone Out, Front] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 021YXH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A16
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/17/2013:svnDellInc.:pnXPSL521X:pvrA16:rvnDellInc.:rn021YXH:rvrA00:cvnDellInc.:ct8:cvrA16:
  dmi.product.name: XPS L521X
  dmi.product.version: A16
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1658559/+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 434351] Re: gnome-language selector is labyrinthine

2016-07-05 Thread Vlad
Agree with Niall's comment #2 above - it took me long time to realize
that the greyed out items in the list are not inactive and that it is
necessary to drag the items in order to make them active.

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

Title:
  gnome-language selector is labyrinthine

Status in language-selector package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: language-selector

  As of 09.10 Karmic ...

  An ample list of installed languages is awkward to determine in 
gnome-language-selector.
  (browsing through a long list, missing, and risking to forget the beginning 
as you reach the end )

  If installed languages were moved to the top (before a separator or to 
another list), it would both ease to quickly see what is currently installed 
and to tell that from what has been marked for installation or unmarked for 
removal.
  Otherwise said, the language position in the list would be the current 
installation status and the mark would be the to-be status (any mark below is 
an addition request, any mark missing from the top is a removal request).
  That would be crystal clear.

  Hoping it'll be simple enough to do.

  Update: and maybe even more following comment #4?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/434351/+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 1552281] [NEW] package nvidia-304 304.131-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-03-02 Thread Vlad
Public bug reported:

After installing the Nvidia driver and reboot the operating system
becomes unbootable . Loading stops when you try to log in ... I have
Acer Extensa 5635G, Nvidia G 105M. P.S. Sorry for my English, wrote an
interpreter .

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-304 304.131-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Wed Mar  2 17:12:37 2016
DuplicateSignature: package:nvidia-304:304.131-0ubuntu0.14.04.1:subprocess 
installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-03-01 (0 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: nvidia-graphics-drivers-304
Title: package nvidia-304 304.131-0ubuntu0.14.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package nvidia-304 304.131-0ubuntu0.14.04.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

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

Bug description:
  After installing the Nvidia driver and reboot the operating system
  becomes unbootable . Loading stops when you try to log in ... I have
  Acer Extensa 5635G, Nvidia G 105M. P.S. Sorry for my English, wrote an
  interpreter .

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-304 304.131-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Wed Mar  2 17:12:37 2016
  DuplicateSignature: package:nvidia-304:304.131-0ubuntu0.14.04.1:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-03-01 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: nvidia-graphics-drivers-304
  Title: package nvidia-304 304.131-0ubuntu0.14.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1552281/+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 1477415] Re: No sound at all snd-hda-intel / ALC260

2015-07-23 Thread Vlad
** Description changed:

  Clean installation of the Ubuntu 14.04.2 LTS on laptop: no audio card
  was detected (Dummy Output). After upgrading to new kernel: was found
  and installed the snd-hda-intel for Realtek ALC260 (Digital Output
  S/PDIF only), but jack detection not working -> no sound at all (the
  driver can't find internal speaker and attached headphones).
  
  The hda-jack-sense-test -a don't show any connection, and the
  hdajackretask don't help with reassign pins as internal speaker - Sound
  Settings was show Internal Speaker but no sound.
  
  Testing with "options snd-hda-intel model=%MODEL FOR ALC260%" and
  updating to the oem-audio-hda-daily-dkms also don't help.
+ 
+ The sound is working in Windows.
  
  
  Alsa-info.txt for upgraded Ubuntu 14.04.2 LTS:
  ==
  
  upload=true&script=true&cardinfo=
  !!
  !!ALSA Information Script v 0.4.64
  !!
  
  !!Script ran on: Wed Jul 22 12:52:03 UTC 2015
  
  !!Linux Distribution
  !!--
  
  Ubuntu 14.04.2 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu
  14.04.2 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu
  14.04.2 LTS" HOME_URL="http://www.ubuntu.com/";
  SUPPORT_URL="http://help.ubuntu.com/";
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
  
  !!DMI Information
  !!---
  
  Manufacturer:  Intel Corporation
  Product Name:  Alviso & ICH6M Chipset
  Product Version:   Not Applicable
  Firmware Version:  1.0C-1203-8A20
  
  !!Kernel Information
  !!--
  
  Kernel release:3.16.0-43-generic
  Operating System:  GNU/Linux
  Architecture:  i686
  Processor: i686
  SMP Enabled:   Yes
  
  !!ALSA Version
  !!
  
  Driver version: k3.16.0-43-generic
  Library version:1.0.27.2
  Utilities version:  1.0.27.2
  
  !!Loaded ALSA modules
  !!---
  
  snd_hda_intel
  
  !!Sound Servers on this system
  !!
  
  Pulseaudio:
    Installed - Yes (/usr/bin/pulseaudio)
    Running - Yes
  
  !!Soundcards recognised by ALSA
  !!-
  
   0 [Intel  ]: HDA-Intel - HDA Intel
    HDA Intel at 0xb000 irq 17
  
  !!PCI Soundcards installed in the system
  !!--
  
  00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
  Family) High Definition Audio Controller (rev 04)
  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---
  
  00:1b.0 0403: 8086:2668 (rev 04)
   Subsystem: 1509:3741
  --
   Prefetchable memory behind bridge: 4000-401f
   Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort-  ../controlC0
  
  !!Aplay/Arecord output
  !!
  
  APLAY
  
   List of PLAYBACK Hardware Devices 
  card 0: Intel [HDA Intel], device 0: ALC260 Analog [ALC260 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: Intel [HDA Intel], device 1: ALC260 Digital [ALC260 Digital]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  
  ARECORD
  
   List of CAPTURE Hardware Devices 
  card 0: Intel [HDA Intel], device 0: ALC260 Analog [ALC260 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: Intel [HDA Intel], device 1: ALC260 Digital [ALC260 Digital]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: Intel [HDA Intel], device 2: ALC260 Alt Analog [ALC260 Alt Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  
  !!Amixer output
  !!-
  
  !!---Mixer controls for card 0 [Intel]
  
  Card hw:0 'Intel'/'HDA Intel at 0xb000 irq 17'
    Mixer name  : 'Realtek ALC260'
    Components  : 'HDA:10ec0260,0260,00100400 
HDA:163c3155,163c3055,00100700'
    Controls  : 45
    Simple ctrls  : 16
  Simple mixer control 'Master',0
    Capabilities: pvolume pswitch
    Playback channels: Front Left - Front Right
    Limits: Playback 0 - 64
    Mono:
    Front Left: Playback 64 [100%] [0.00dB] [on]
    Front Right: Playback 64 [100%] [0.00dB] [on]
  Simple mixer control 'PCM',0
    Capabilities: pvolume
    Playback channels: Front Left - Front Right
    Limits: Playback 0 - 255
    Mono:
    Front Left: Playback 255 [100%] [0.00dB]
    Front Right: Playback 255 [100%] [0.00dB]
  Simple mixer control 'Front Mic',0
    Capabilities: pvolume pswitch
    Playback channels: Front Left - Front Right
    Limits: Playback 0 - 65
    Mono:
    Front Left: Playback 65 [100%] [30.00dB] [on]
    Front Right: Playback 65 [100%] [30.00dB] [on]
  Simple mixer control 'Line

[Desktop-packages] [Bug 146850] Re: rhythmbox crashed with SIGSEGV in vorbis_synthesis_blockin()

2015-06-17 Thread vlad
** Changed in: libvorbis (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  rhythmbox crashed with SIGSEGV in vorbis_synthesis_blockin()

Status in The Rhythmbox Music Management Application:
  New
Status in libvorbis package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: rhythmbox

  Pressed play on the "Trance radio station" and Rhythmbox crashed.

  ProblemType: Crash
  Architecture: i386
  Date: Sat Sep 29 11:48:42 2007
  DistroRelease: Ubuntu 7.10
  ExecutablePath: /usr/bin/rhythmbox
  NonfreeKernelModules: nvidia
  Package: rhythmbox 0.11.2-0ubuntu3
  PackageArchitecture: i386
  ProcCmdline: rhythmbox
  ProcCwd: /home/yorneb
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   vorbis_synthesis_blockin () from /usr/lib/libvorbis.so.0
   ?? () from /usr/lib/gstreamer-0.10/libgstvorbis.so
   ?? ()
   ?? ()
   ?? ()
  Title: rhythmbox crashed with SIGSEGV in vorbis_synthesis_blockin()
  Uname: Linux senna 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 
GNU/Linux
  UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev 
powerdev scanner video

  SegvAnalysis:
   Segfault happened at: 0xb435abf9 : fstps  
0xfffc(%esi,%edx,4)
   PC (0xb435abf9) ok
   source "0xfffc(%esi,%edx,4)" (0x09212250) ok
   Stack memory exhausted (SP below stack segment)
   SP (0xb20faa20) ok
   Reason could not be automatically determined.
  SegvReason: Reason could not be automatically determined.

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/146850/+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 1586716] Re: yelp crashed with SIGSEGV in g_str_equal()

2020-12-19 Thread Vlad Orlov
** Bug watch added: gitlab.gnome.org/GNOME/yelp/-/issues #116
   https://gitlab.gnome.org/GNOME/yelp/-/issues/116

** Changed in: yelp
   Importance: Medium => Unknown

** Changed in: yelp
   Status: Expired => Unknown

** Changed in: yelp
 Remote watch: GNOME Bug Tracker #778553 => 
gitlab.gnome.org/GNOME/yelp/-/issues #116

** Bug watch removed: GNOME Bug Tracker #778553
   https://gitlab.gnome.org/778553

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

Title:
  yelp crashed with SIGSEGV in g_str_equal()

Status in Ubuntu GNOME:
  Triaged
Status in Yelp:
  Unknown
Status in yelp package in Ubuntu:
  Triaged

Bug description:
  No idea, just saw the error.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: yelp 3.20.1-1ubuntu1~xenial1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  Uname: Linux 4.6.0-040600-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Sun May 29 03:03:21 2016
  ExecutablePath: /usr/bin/yelp
  InstallationDate: Installed on 2014-02-04 (844 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140203)
  ProcCmdline: yelp file:///usr/share/doc/pspp/pspp.xml#ONEWAY
  SegvAnalysis:
   Segfault happened at: 0x7f497638eb5a <__strcmp_sse2_unaligned+26>:   movdqu 
(%rdi),%xmm1
   PC (0x7f497638eb5a) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm1" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: yelp
  StacktraceTop:
   g_str_equal () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libyelp.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libyelp.so.0
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: yelp crashed with SIGSEGV in g_str_equal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo 
vboxusers
  XsessionErrors:
   (cinnamon-settings-daemon:3255): color-plugin-WARNING **: failed to create 
device: failed to obtain org.freedesktop.color-manager.create-device auth
   (cinnamon-settings-daemon:3255): color-plugin-WARNING **: failed to obtain 
org.freedesktop.color-manager.create-profile auth
   (cinnamon-settings-daemon:3255): color-plugin-WARNING **: failed to obtain 
org.freedesktop.color-manager.create-profile auth
   (cinnamon-settings-daemon:3255): color-plugin-WARNING **: could not find 
device: property match 'XRANDR_name'='eDP1' does not exist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1586716/+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 1549653] Re: Disks utility doesn't remove previous record in /etc/fstab

2021-01-25 Thread Vlad Orlov
** Bug watch added: gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues #43
   https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/43

** Changed in: gnome-disk-utility
   Importance: Medium => Unknown

** Changed in: gnome-disk-utility
   Status: Expired => Unknown

** Changed in: gnome-disk-utility
 Remote watch: GNOME Bug Tracker #762718 => 
gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues #43

** Bug watch removed: GNOME Bug Tracker #762718
   https://gitlab.gnome.org/762718

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

Title:
  Disks utility doesn't remove previous record in /etc/fstab

Status in GNOME Disks:
  Unknown
Status in gnome-disk-utility package in Ubuntu:
  Triaged

Bug description:
  How to reproduce:
  1. delete an NTFS partition on secondary disk (rewrite with zeroes).
  2. put there EXT4 partition instead.
  3. reboot computer
  => ubuntu doesn't boot, allows only single-user mode.

  By checking system log, I found out system was trying to mount the old
  NTFS partition and hanged on it, even though that is not at all a
  necessary partition. Then I checked /etc/fstab and found out the GUI
  tool did NOT remove the original record, when it deleted the partition
  on the drive.

  By commenting it out I was able to get into the GUI again.

  Ubuntu 15.10
  pkg: gnome-disk-utility 3.16.2-0ubuntu2 0

  The original line, that was left behind:
  UUID=52D09468D09453D7 /backup ntfsdefaults,umask=007,gid=46 0 
  0

  The new line that the tool created:
  /dev/disk/by-uuid/414e95a1-fb40-45a6-9b90-487a45337fdd /extdata auto 
nosuid,nodev,nofail,x-gvfs-show 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-disk-utility 3.16.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 25 08:34:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-02-24 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1549653/+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 1360225] Re: gnome-mahjongg has outdated website link in the package description in Mint 17/Ubuntu 14.04

2021-01-26 Thread Vlad Orlov
Fixed in version 1:3.14.1-1, according to git:

https://salsa.debian.org/gnome-team/gnome-
mahjongg/-/commit/04d2e96e8894b340e47b72e9f4bd29c0e2a32b72

** Changed in: gnome-mahjongg (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  gnome-mahjongg has outdated website link in the package description in
  Mint 17/Ubuntu 14.04

Status in gnome-mahjongg package in Ubuntu:
  Fix Released

Bug description:
  The Software Manager (mintInstall 7.5.7) shows an outdated link for the 
gnome-mahjongg package. 
  The link shown is 

  https://live.gnome.org/Mahjongg

  but it should be

  https://wiki.gnome.org/Apps/Mahjongg

  Not the end of the world, I know, but still a bug.

  My system: Mint 17 64-bit XFCE, dist-upgraded to current.

  Cheers
  --Knut

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-mahjongg/+bug/1360225/+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 1871068] [NEW] Gedit current line highlighting doesn't play well with Yaru-dark

2020-04-06 Thread Vlad Svitlichniy
Public bug reported:

By default, gedit has "Highlight current line" option enabled. While
that works great for Yaru and Adwaita, this is barely usable with Yaru-
dark, because both background and foreground are just different shades
of white.

While this is a minor issue and can be easily fixed by adjusting gedit's
color scheme, that might give not the best impression for a first-time
Ubuntu user.

apt policy gedit
gedit:
  Installed: 3.36.1-1
  Candidate: 3.36.1-1
  Version table:
 *** 3.36.1-1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

apt policy yaru-theme-gtk
yaru-theme-gtk:
  Installed: 20.04.4
  Candidate: 20.04.4
  Version table:
 *** 20.04.4 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: yaru-theme-gtk 20.04.4
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  6 11:43:32 2020
InstallationDate: Installed on 2019-11-07 (150 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
SourcePackage: yaru-theme
UpgradeStatus: Upgraded to focal on 2020-03-04 (32 days ago)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-04-06 11-42-38.png"
   
https://bugs.launchpad.net/bugs/1871068/+attachment/5347648/+files/Screenshot%20from%202020-04-06%2011-42-38.png

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

Title:
  Gedit current line highlighting doesn't play well with Yaru-dark

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  By default, gedit has "Highlight current line" option enabled. While
  that works great for Yaru and Adwaita, this is barely usable with
  Yaru-dark, because both background and foreground are just different
  shades of white.

  While this is a minor issue and can be easily fixed by adjusting
  gedit's color scheme, that might give not the best impression for a
  first-time Ubuntu user.

  apt policy gedit
  gedit:
Installed: 3.36.1-1
Candidate: 3.36.1-1
Version table:
   *** 3.36.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  apt policy yaru-theme-gtk
  yaru-theme-gtk:
Installed: 20.04.4
Candidate: 20.04.4
Version table:
   *** 20.04.4 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: yaru-theme-gtk 20.04.4
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 11:43:32 2020
  InstallationDate: Installed on 2019-11-07 (150 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: yaru-theme
  UpgradeStatus: Upgraded to focal on 2020-03-04 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1871068/+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 1862081] Re: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling)

2020-04-09 Thread Vlad Svitlichniy
@jonas-jelten I believe that should be it
https://git.launchpad.net/ubuntu/+source/mutter/diff/debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch?id=3c4a6b2d7bcb210b3460f40587d4b14c19203c02

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

Title:
  Gnome resizes framebuffer when playing fullscreen video over and over
  again (when using X11 fractional scaling)

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  When I play a video with mpv (or e.g. Firefox), it works just fine.

  When this video is fullscreened (e.g. in mpv by pressing f), the
  screen quickly turns off, and switches resolution modes in such a rate
  the screen is unusable.

  The native resolution of the screen is 1440p, but Xorg somehow
  increases the size to 3424x1926 for the fullscreen, then quickly
  switches back to 1440p, before increasing it again.

  As soon as the video is de-fullscreened (by pressing f again in mpv,
  or esc in Firefox), the funny resolution switching stops and the
  system is usable again.

  This also happens with the modesetting 2d-driver. This does not happen
  with Wayland.

  This can be seen in the Xorg-log:
  [20.215] (II) intel(0): EDID vendor "JDI", prod id 0
  [20.215] (II) intel(0): Printing DDC gathered Modelines:
  [20.215] (II) intel(0): Modeline "2560x1440"x0.0  245.12  2560 2608 2640 
2720  1440 1443 1449 1502 +hsync -vsync (90.1 kHz eP)
  [   258.869] (II) intel(0): resizing framebuffer to 3424x1926
  [   258.905] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [   268.955] (II) intel(0): resizing framebuffer to 2560x1440
  [   269.097] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [   270.383] (II) intel(0): resizing framebuffer to 3424x1926
  [   270.400] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [   271.852] (II) intel(0): resizing framebuffer to 2560x1440
  [   271.858] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [   273.294] (II) intel(0): resizing framebuffer to 3424x1926
  [   273.314] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 
0, position (0, 0), rotation normal, reflection none

  When the resolution is increased, the Kernel complains about the
  framebuffer size:

  [  269.830034] [drm] Reducing the compressed framebuffer size. This
  may lead to less power savings than a non-reduced-size. Try to
  increase stolen memory size if available in BIOS.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu13
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 00:00:07 2020
  DistUpgraded: 2020-02-05 22:21:13,002 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:2259]
  MachineType: LENOVO 20LES01W00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/hostname-ubunturoot ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-02-05 (0 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N25ET52W (1.38 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LES01W00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN25ET52W(1.38):bd11/27/2019:svnLENOVO:pn20LES01W00:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LES01W00:rvrNotDefined:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 3rd
  dmi.product.name: 20LES01W00
  dmi.product.sku: LENOVO_MT_20LE_BU_Think_FM_ThinkPad X1 Yoga 3rd
  dmi.product.version: ThinkPad X1 Yoga 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xor

[Desktop-packages] [Bug 1862081] Re: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling)

2020-04-10 Thread Vlad Svitlichniy
Thank you for the fix!
After having my mutter updated, I can finally watch the fullscreen videos while 
having the fractional scaling enabled 

However, there is one minor issue. Whenever I switch to the fullscreen
mode, the scaling factor is changed from 150% to 200%, so all the
widgets are unnecessarily large. This isn't a deal breaker for me,
because I use the fullscreen mode only for watching the videos; I just
wanted to confirm that it's the intended behavior

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

Title:
  Gnome resizes framebuffer when playing fullscreen video over and over
  again (when using X11 fractional scaling)

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  When I play a video with mpv (or e.g. Firefox), it works just fine.

  When this video is fullscreened (e.g. in mpv by pressing f), the
  screen quickly turns off, and switches resolution modes in such a rate
  the screen is unusable.

  The native resolution of the screen is 1440p, but Xorg somehow
  increases the size to 3424x1926 for the fullscreen, then quickly
  switches back to 1440p, before increasing it again.

  As soon as the video is de-fullscreened (by pressing f again in mpv,
  or esc in Firefox), the funny resolution switching stops and the
  system is usable again.

  This also happens with the modesetting 2d-driver. This does not happen
  with Wayland.

  This can be seen in the Xorg-log:
  [20.215] (II) intel(0): EDID vendor "JDI", prod id 0
  [20.215] (II) intel(0): Printing DDC gathered Modelines:
  [20.215] (II) intel(0): Modeline "2560x1440"x0.0  245.12  2560 2608 2640 
2720  1440 1443 1449 1502 +hsync -vsync (90.1 kHz eP)
  [   258.869] (II) intel(0): resizing framebuffer to 3424x1926
  [   258.905] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [   268.955] (II) intel(0): resizing framebuffer to 2560x1440
  [   269.097] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [   270.383] (II) intel(0): resizing framebuffer to 3424x1926
  [   270.400] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [   271.852] (II) intel(0): resizing framebuffer to 2560x1440
  [   271.858] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [   273.294] (II) intel(0): resizing framebuffer to 3424x1926
  [   273.314] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 
0, position (0, 0), rotation normal, reflection none

  When the resolution is increased, the Kernel complains about the
  framebuffer size:

  [  269.830034] [drm] Reducing the compressed framebuffer size. This
  may lead to less power savings than a non-reduced-size. Try to
  increase stolen memory size if available in BIOS.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu13
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 00:00:07 2020
  DistUpgraded: 2020-02-05 22:21:13,002 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:2259]
  MachineType: LENOVO 20LES01W00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/hostname-ubunturoot ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-02-05 (0 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N25ET52W (1.38 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LES01W00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN25ET52W(1.38):bd11/27/2019:svnLENOVO:pn20LES01W00:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LES01W00:rvrNotDefined:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 3rd
  dmi.product.name: 20LES01W00
  dmi.product.sku: LENOVO_MT_20LE_BU_Think_FM_ThinkPad X1 Yoga 3rd
  dmi.product.version: ThinkPad X1 Yoga 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:

[Desktop-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

2020-09-16 Thread Vlad V.
Hi!

I had the same problem with JBL TUNE500BT Headphones on Ubuntu 20.04. I
did a kernel update to 5.8.9-050809-generic version using ubuntu-
mainline-kernel.sh script [1]. I also uninstalled ofono and ofono-
phonesim which I installed earlier when trying to fix this problem and
reverted any changes I did to the default.pa file. It seems to be
working now, but audio quality is awful when using HSP/HFP, which is
related to another bug [2]. I don't know if it's a good solution, but
maybe it will help someone.

[1]: 
https://raw.githubusercontent.com/pimlie/ubuntu-mainline-kernel.sh/master/ubuntu-mainline-kernel.sh
[2]: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838151

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1867668] [NEW] Visual artifacts in Gnome Shell after upgrading to 20.04

2020-03-16 Thread Vlad Svitlichniy
Public bug reported:

I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
minor (but pretty annoying) issues with Gnome Shell every time I load
the system. The background image has some green/violet/black visual
artifacts, and the text elements in Gnome Shell incorrectly display some
of the symbol. Changing the background image removes the artifacts until
the next reboot (but if I select the previous one without rebooting,
then I still see the same artifacts, so it's probably cached somewhere).
Restarting the shell via Alt+F2 `r` usually removes the artifacts from
the background image, but the text issues are still present.

The issues are reprodicable with and without extensions, with 1.0, 1.5
and 2.0 display scaling factors applied, and they are not user-specific
(i.e. I was able to reproduce them after creating a new user from
scratch)

As far as I can say, only Gnome Shell is affected. All the applications
(including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and
flatpak) work fine without any issues

Sometimes, the application icons are also affected (as you can see on
one of the attached screenshots)

~> lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04

~> apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.35.91-1ubuntu2
  Candidate: 3.35.91-1ubuntu2
  Version table:
 *** 3.35.91-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

~> gsettings get org.gnome.mutter experimental-features
['x11-randr-fractional-scaling']

~> uname -r
5.4.0-14-generic

hwinfo (videocard, monitor):
38: PCI 02.0: 0300 VGA compatible controller (VGA)
  [Created at pci.386]
  Unique ID: _Znp.pq3kk9M9L4C
  SysFS ID: /devices/pci:00/:00:02.0
  SysFS BusID: :00:02.0
  Hardware Class: graphics card
  Model: "Intel UHD Graphics 620"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x5917 "UHD Graphics 620"
  SubVendor: pci 0x17aa "Lenovo"
  SubDevice: pci 0x225c
  Revision: 0x07
  Driver: "i915"
  Driver Modules: "i915"
  Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable)
  Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable)
  I/O Ports: 0xe000-0xe03f (rw)
  Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
  IRQ: 161 (64308 events)
  Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00"
  Driver Info #0:
Driver Status: i915 is active
Driver Activation Cmd: "modprobe i915"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
43: None 00.0: 10002 LCD Monitor
  [Created at monitor.125]
  Unique ID: rdCR.R7Dpg_aaVOC
  Parent ID: _Znp.pq3kk9M9L4C
  Hardware Class: monitor
  Model: "LG Display LCD Monitor"
  Vendor: LGD "LG Display"
  Device: eisa 0x058b
  Resolution: 2560x1440@60Hz
  Size: 309x174 mm
  Year of Manufacture: 2016
  Week of Manufacture: 0
  Detailed Timings #0:
 Resolution: 2560x1440
 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
   Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync
Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #38 (VGA compatible controller)

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

** Attachment added: "shell-example-2.png"
   
https://bugs.launchpad.net/bugs/1867668/+attachment/5337648/+files/shell-example-2.png

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

Title:
  Visual artifacts in Gnome Shell after upgrading to 20.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
  minor (but pretty annoying) issues with Gnome Shell every time I load
  the system. The background image has some green/violet/black visual
  artifacts, and the text elements in Gnome Shell incorrectly display
  some of the symbol. Changing the background image removes the
  artifacts until the next reboot (but if I select the previous one
  without rebooting, then I still see the same artifacts, so it's
  probably cached somewhere). Restarting the shell via Alt+F2 `r`
  usually removes the artifacts from the background image, but the text
  issues are still present.

  The issues are reprodicable with and without extensions, with 1.0, 1.5
  and 2.0 display scaling factors applied, and they are not user-
  specific (i.e. I was able to reproduce them after creating a new user
  from scratch)

  As far as I can say, only Gnome Shell is affected. All the
  applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both
  "native" and flatpak) work fine without any issues

  Sometimes, the application icons are also affected (as you can see on
  one of the attached screenshots)

  ~> lsb_release -rd
  Description:  Ubuntu Focal Fossa (development br

[Desktop-packages] [Bug 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04

2020-03-16 Thread Vlad Svitlichniy
** Attachment added: "shell-example-3.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+attachment/5337650/+files/shell-example-3.png

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

Title:
  Visual artifacts in Gnome Shell after upgrading to 20.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
  minor (but pretty annoying) issues with Gnome Shell every time I load
  the system. The background image has some green/violet/black visual
  artifacts, and the text elements in Gnome Shell incorrectly display
  some of the symbol. Changing the background image removes the
  artifacts until the next reboot (but if I select the previous one
  without rebooting, then I still see the same artifacts, so it's
  probably cached somewhere). Restarting the shell via Alt+F2 `r`
  usually removes the artifacts from the background image, but the text
  issues are still present.

  The issues are reprodicable with and without extensions, with 1.0, 1.5
  and 2.0 display scaling factors applied, and they are not user-
  specific (i.e. I was able to reproduce them after creating a new user
  from scratch)

  As far as I can say, only Gnome Shell is affected. All the
  applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both
  "native" and flatpak) work fine without any issues

  Sometimes, the application icons are also affected (as you can see on
  one of the attached screenshots)

  ~> lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ~> apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.35.91-1ubuntu2
    Candidate: 3.35.91-1ubuntu2
    Version table:
   *** 3.35.91-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ~> gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling']

  ~> uname -r
  5.4.0-14-generic

  hwinfo (videocard, monitor):
  38: PCI 02.0: 0300 VGA compatible controller (VGA)
    [Created at pci.386]
    Unique ID: _Znp.pq3kk9M9L4C
    SysFS ID: /devices/pci:00/:00:02.0
    SysFS BusID: :00:02.0
    Hardware Class: graphics card
    Model: "Intel UHD Graphics 620"
    Vendor: pci 0x8086 "Intel Corporation"
    Device: pci 0x5917 "UHD Graphics 620"
    SubVendor: pci 0x17aa "Lenovo"
    SubDevice: pci 0x225c
    Revision: 0x07
    Driver: "i915"
    Driver Modules: "i915"
    Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable)
    Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable)
    I/O Ports: 0xe000-0xe03f (rw)
    Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
    IRQ: 161 (64308 events)
    Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00"
    Driver Info #0:
  Driver Status: i915 is active
  Driver Activation Cmd: "modprobe i915"
    Config Status: cfg=new, avail=yes, need=no, active=unknown
  43: None 00.0: 10002 LCD Monitor
    [Created at monitor.125]
    Unique ID: rdCR.R7Dpg_aaVOC
    Parent ID: _Znp.pq3kk9M9L4C
    Hardware Class: monitor
    Model: "LG Display LCD Monitor"
    Vendor: LGD "LG Display"
    Device: eisa 0x058b
    Resolution: 2560x1440@60Hz
    Size: 309x174 mm
    Year of Manufacture: 2016
    Week of Manufacture: 0
    Detailed Timings #0:
   Resolution: 2560x1440
   Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
     Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync
  Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #38 (VGA compatible controller)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+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 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04

2020-03-16 Thread Vlad Svitlichniy
** Attachment added: "shell-example-1.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+attachment/5337649/+files/shell-example-1.png

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

Title:
  Visual artifacts in Gnome Shell after upgrading to 20.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
  minor (but pretty annoying) issues with Gnome Shell every time I load
  the system. The background image has some green/violet/black visual
  artifacts, and the text elements in Gnome Shell incorrectly display
  some of the symbol. Changing the background image removes the
  artifacts until the next reboot (but if I select the previous one
  without rebooting, then I still see the same artifacts, so it's
  probably cached somewhere). Restarting the shell via Alt+F2 `r`
  usually removes the artifacts from the background image, but the text
  issues are still present.

  The issues are reprodicable with and without extensions, with 1.0, 1.5
  and 2.0 display scaling factors applied, and they are not user-
  specific (i.e. I was able to reproduce them after creating a new user
  from scratch)

  As far as I can say, only Gnome Shell is affected. All the
  applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both
  "native" and flatpak) work fine without any issues

  Sometimes, the application icons are also affected (as you can see on
  one of the attached screenshots)

  ~> lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ~> apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.35.91-1ubuntu2
    Candidate: 3.35.91-1ubuntu2
    Version table:
   *** 3.35.91-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ~> gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling']

  ~> uname -r
  5.4.0-14-generic

  hwinfo (videocard, monitor):
  38: PCI 02.0: 0300 VGA compatible controller (VGA)
    [Created at pci.386]
    Unique ID: _Znp.pq3kk9M9L4C
    SysFS ID: /devices/pci:00/:00:02.0
    SysFS BusID: :00:02.0
    Hardware Class: graphics card
    Model: "Intel UHD Graphics 620"
    Vendor: pci 0x8086 "Intel Corporation"
    Device: pci 0x5917 "UHD Graphics 620"
    SubVendor: pci 0x17aa "Lenovo"
    SubDevice: pci 0x225c
    Revision: 0x07
    Driver: "i915"
    Driver Modules: "i915"
    Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable)
    Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable)
    I/O Ports: 0xe000-0xe03f (rw)
    Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
    IRQ: 161 (64308 events)
    Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00"
    Driver Info #0:
  Driver Status: i915 is active
  Driver Activation Cmd: "modprobe i915"
    Config Status: cfg=new, avail=yes, need=no, active=unknown
  43: None 00.0: 10002 LCD Monitor
    [Created at monitor.125]
    Unique ID: rdCR.R7Dpg_aaVOC
    Parent ID: _Znp.pq3kk9M9L4C
    Hardware Class: monitor
    Model: "LG Display LCD Monitor"
    Vendor: LGD "LG Display"
    Device: eisa 0x058b
    Resolution: 2560x1440@60Hz
    Size: 309x174 mm
    Year of Manufacture: 2016
    Week of Manufacture: 0
    Detailed Timings #0:
   Resolution: 2560x1440
   Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
     Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync
  Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #38 (VGA compatible controller)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+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 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04

2020-03-16 Thread Vlad Svitlichniy
** Attachment added: "shell-example-4.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+attachment/5337651/+files/shell-example-4.png

** Description changed:

  I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
  minor (but pretty annoying) issues with Gnome Shell every time I load
- the system. The background image has some green/violet visual artifacts,
- and the text elements in Gnome Shell incorrectly display some of the
- symbol. Changing the background image removes the artifacts until the
- next reboot (but if I select the previous one without rebooting, then I
- still see the same artifacts, so it's probably cached somewhere).
+ the system. The background image has some green/violet/black visual
+ artifacts, and the text elements in Gnome Shell incorrectly display some
+ of the symbol. Changing the background image removes the artifacts until
+ the next reboot (but if I select the previous one without rebooting,
+ then I still see the same artifacts, so it's probably cached somewhere).
  Restarting the shell via Alt+F2 `r` usually removes the artifacts from
  the background image, but the text issues are still present.
  
- The issues are reproduced with and without extensions, with 1.0, 1.5 and
- 2.0 display scaling factors applied, and they are not user-specific
+ The issues are reprodicable with and without extensions, with 1.0, 1.5
+ and 2.0 display scaling factors applied, and they are not user-specific
  (i.e. I was able to reproduce them after creating a new user from
  scratch)
  
  As far as I can say, only Gnome Shell is affected. All the applications
  (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and
  flatpak) work fine without any issues
  
  Sometimes, the application icons are also affected (as you can see on
  one of the attached screenshots)
  
  ~> lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  
  ~> apt-cache policy gnome-shell
  gnome-shell:
-   Installed: 3.35.91-1ubuntu2
-   Candidate: 3.35.91-1ubuntu2
-   Version table:
-  *** 3.35.91-1ubuntu2 500
- 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 3.35.91-1ubuntu2
+   Candidate: 3.35.91-1ubuntu2
+   Version table:
+  *** 3.35.91-1ubuntu2 500
+ 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  ~> gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling']
  
  ~> uname -r
  5.4.0-14-generic
  
  hwinfo (videocard, monitor):
  38: PCI 02.0: 0300 VGA compatible controller (VGA)
-   [Created at pci.386]
-   Unique ID: _Znp.pq3kk9M9L4C
-   SysFS ID: /devices/pci:00/:00:02.0
-   SysFS BusID: :00:02.0
-   Hardware Class: graphics card
-   Model: "Intel UHD Graphics 620"
-   Vendor: pci 0x8086 "Intel Corporation"
-   Device: pci 0x5917 "UHD Graphics 620"
-   SubVendor: pci 0x17aa "Lenovo"
-   SubDevice: pci 0x225c 
-   Revision: 0x07
-   Driver: "i915"
-   Driver Modules: "i915"
-   Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable)
-   Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable)
-   I/O Ports: 0xe000-0xe03f (rw)
-   Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
-   IRQ: 161 (64308 events)
-   Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00"
-   Driver Info #0:
- Driver Status: i915 is active
- Driver Activation Cmd: "modprobe i915"
-   Config Status: cfg=new, avail=yes, need=no, active=unknown
+   [Created at pci.386]
+   Unique ID: _Znp.pq3kk9M9L4C
+   SysFS ID: /devices/pci:00/:00:02.0
+   SysFS BusID: :00:02.0
+   Hardware Class: graphics card
+   Model: "Intel UHD Graphics 620"
+   Vendor: pci 0x8086 "Intel Corporation"
+   Device: pci 0x5917 "UHD Graphics 620"
+   SubVendor: pci 0x17aa "Lenovo"
+   SubDevice: pci 0x225c
+   Revision: 0x07
+   Driver: "i915"
+   Driver Modules: "i915"
+   Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable)
+   Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable)
+   I/O Ports: 0xe000-0xe03f (rw)
+   Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
+   IRQ: 161 (64308 events)
+   Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00"
+   Driver Info #0:
+ Driver Status: i915 is active
+ Driver Activation Cmd: "modprobe i915"
+   Config Status: cfg=new, avail=yes, need=no, active=unknown
  43: None 00.0: 10002 LCD Monitor
-   [Created at monitor.125]
-   Unique ID: rdCR.R7Dpg_aaVOC
-   Parent ID: _Znp.pq3kk9M9L4C
-   Hardware Class: monitor
-   Model: "LG Display LCD Monitor"
-   Vendor: LGD "LG Display"
-   Device: eisa 0x058b 
-   Resolution: 2560x1440@60Hz
-   Size: 309x174 mm
-   Year of Manufacture: 2016
-   Week of Manufacture: 0
-   Detailed Timings #0:
-  Resolution: 2560x1440
-  Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
-Verti

[Desktop-packages] [Bug 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04

2020-03-17 Thread Vlad Svitlichniy
apport information

** Tags added: apport-collected third-party-packages

** Description changed:

  I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
  minor (but pretty annoying) issues with Gnome Shell every time I load
  the system. The background image has some green/violet/black visual
  artifacts, and the text elements in Gnome Shell incorrectly display some
  of the symbol. Changing the background image removes the artifacts until
  the next reboot (but if I select the previous one without rebooting,
  then I still see the same artifacts, so it's probably cached somewhere).
  Restarting the shell via Alt+F2 `r` usually removes the artifacts from
  the background image, but the text issues are still present.
  
  The issues are reprodicable with and without extensions, with 1.0, 1.5
  and 2.0 display scaling factors applied, and they are not user-specific
  (i.e. I was able to reproduce them after creating a new user from
  scratch)
  
  As far as I can say, only Gnome Shell is affected. All the applications
  (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and
  flatpak) work fine without any issues
  
  Sometimes, the application icons are also affected (as you can see on
  one of the attached screenshots)
  
  ~> lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  
  ~> apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.35.91-1ubuntu2
    Candidate: 3.35.91-1ubuntu2
    Version table:
   *** 3.35.91-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  
  ~> gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling']
  
  ~> uname -r
  5.4.0-14-generic
  
  hwinfo (videocard, monitor):
  38: PCI 02.0: 0300 VGA compatible controller (VGA)
    [Created at pci.386]
    Unique ID: _Znp.pq3kk9M9L4C
    SysFS ID: /devices/pci:00/:00:02.0
    SysFS BusID: :00:02.0
    Hardware Class: graphics card
    Model: "Intel UHD Graphics 620"
    Vendor: pci 0x8086 "Intel Corporation"
    Device: pci 0x5917 "UHD Graphics 620"
    SubVendor: pci 0x17aa "Lenovo"
    SubDevice: pci 0x225c
    Revision: 0x07
    Driver: "i915"
    Driver Modules: "i915"
    Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable)
    Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable)
    I/O Ports: 0xe000-0xe03f (rw)
    Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
    IRQ: 161 (64308 events)
    Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00"
    Driver Info #0:
  Driver Status: i915 is active
  Driver Activation Cmd: "modprobe i915"
    Config Status: cfg=new, avail=yes, need=no, active=unknown
  43: None 00.0: 10002 LCD Monitor
    [Created at monitor.125]
    Unique ID: rdCR.R7Dpg_aaVOC
    Parent ID: _Znp.pq3kk9M9L4C
    Hardware Class: monitor
    Model: "LG Display LCD Monitor"
    Vendor: LGD "LG Display"
    Device: eisa 0x058b
    Resolution: 2560x1440@60Hz
    Size: 309x174 mm
    Year of Manufacture: 2016
    Week of Manufacture: 0
    Detailed Timings #0:
   Resolution: 2560x1440
   Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
     Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync
  Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #38 (VGA compatible controller)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu20
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2019-11-07 (130 days ago)
+ InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
+ Package: gnome-shell 3.35.91-1ubuntu2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
+ RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
+ Tags: third-party-packages focal
+ Uname: Linux 5.4.0-14-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago)
+ UserGroups: microk8s sudo
+ _MarkForUpload: True

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

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

Title:
  Visual artifacts in Gnome Shell after upgrading to 20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
  minor (but pretty annoying) issues with Gnome Shell every time I load
  the system. The background image has some green/violet/black visual
  artifacts, and the text elements in Gnome Shell incorrectly display
  some of the symbol. Changing the background image removes the
  artifacts until the next reboot (but if I select 

[Desktop-packages] [Bug 1867668] ProcEnviron.txt

2020-03-17 Thread Vlad Svitlichniy
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1867668/+attachment/5337878/+files/ProcEnviron.txt

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

Title:
  Visual artifacts in Gnome Shell after upgrading to 20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
  minor (but pretty annoying) issues with Gnome Shell every time I load
  the system. The background image has some green/violet/black visual
  artifacts, and the text elements in Gnome Shell incorrectly display
  some of the symbol. Changing the background image removes the
  artifacts until the next reboot (but if I select the previous one
  without rebooting, then I still see the same artifacts, so it's
  probably cached somewhere). Restarting the shell via Alt+F2 `r`
  usually removes the artifacts from the background image, but the text
  issues are still present.

  The issues are reprodicable with and without extensions, with 1.0, 1.5
  and 2.0 display scaling factors applied, and they are not user-
  specific (i.e. I was able to reproduce them after creating a new user
  from scratch)

  As far as I can say, only Gnome Shell is affected. All the
  applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both
  "native" and flatpak) work fine without any issues

  Sometimes, the application icons are also affected (as you can see on
  one of the attached screenshots)

  ~> lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ~> apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.35.91-1ubuntu2
    Candidate: 3.35.91-1ubuntu2
    Version table:
   *** 3.35.91-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ~> gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling']

  ~> uname -r
  5.4.0-14-generic

  hwinfo (videocard, monitor):
  38: PCI 02.0: 0300 VGA compatible controller (VGA)
    [Created at pci.386]
    Unique ID: _Znp.pq3kk9M9L4C
    SysFS ID: /devices/pci:00/:00:02.0
    SysFS BusID: :00:02.0
    Hardware Class: graphics card
    Model: "Intel UHD Graphics 620"
    Vendor: pci 0x8086 "Intel Corporation"
    Device: pci 0x5917 "UHD Graphics 620"
    SubVendor: pci 0x17aa "Lenovo"
    SubDevice: pci 0x225c
    Revision: 0x07
    Driver: "i915"
    Driver Modules: "i915"
    Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable)
    Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable)
    I/O Ports: 0xe000-0xe03f (rw)
    Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
    IRQ: 161 (64308 events)
    Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00"
    Driver Info #0:
  Driver Status: i915 is active
  Driver Activation Cmd: "modprobe i915"
    Config Status: cfg=new, avail=yes, need=no, active=unknown
  43: None 00.0: 10002 LCD Monitor
    [Created at monitor.125]
    Unique ID: rdCR.R7Dpg_aaVOC
    Parent ID: _Znp.pq3kk9M9L4C
    Hardware Class: monitor
    Model: "LG Display LCD Monitor"
    Vendor: LGD "LG Display"
    Device: eisa 0x058b
    Resolution: 2560x1440@60Hz
    Size: 309x174 mm
    Year of Manufacture: 2016
    Week of Manufacture: 0
    Detailed Timings #0:
   Resolution: 2560x1440
   Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
     Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync
  Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #38 (VGA compatible controller)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-07 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago)
  UserGroups: microk8s sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+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 1867668] ShellJournal.txt

2020-03-17 Thread Vlad Svitlichniy
apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1867668/+attachment/5337879/+files/ShellJournal.txt

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

Title:
  Visual artifacts in Gnome Shell after upgrading to 20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
  minor (but pretty annoying) issues with Gnome Shell every time I load
  the system. The background image has some green/violet/black visual
  artifacts, and the text elements in Gnome Shell incorrectly display
  some of the symbol. Changing the background image removes the
  artifacts until the next reboot (but if I select the previous one
  without rebooting, then I still see the same artifacts, so it's
  probably cached somewhere). Restarting the shell via Alt+F2 `r`
  usually removes the artifacts from the background image, but the text
  issues are still present.

  The issues are reprodicable with and without extensions, with 1.0, 1.5
  and 2.0 display scaling factors applied, and they are not user-
  specific (i.e. I was able to reproduce them after creating a new user
  from scratch)

  As far as I can say, only Gnome Shell is affected. All the
  applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both
  "native" and flatpak) work fine without any issues

  Sometimes, the application icons are also affected (as you can see on
  one of the attached screenshots)

  ~> lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ~> apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.35.91-1ubuntu2
    Candidate: 3.35.91-1ubuntu2
    Version table:
   *** 3.35.91-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ~> gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling']

  ~> uname -r
  5.4.0-14-generic

  hwinfo (videocard, monitor):
  38: PCI 02.0: 0300 VGA compatible controller (VGA)
    [Created at pci.386]
    Unique ID: _Znp.pq3kk9M9L4C
    SysFS ID: /devices/pci:00/:00:02.0
    SysFS BusID: :00:02.0
    Hardware Class: graphics card
    Model: "Intel UHD Graphics 620"
    Vendor: pci 0x8086 "Intel Corporation"
    Device: pci 0x5917 "UHD Graphics 620"
    SubVendor: pci 0x17aa "Lenovo"
    SubDevice: pci 0x225c
    Revision: 0x07
    Driver: "i915"
    Driver Modules: "i915"
    Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable)
    Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable)
    I/O Ports: 0xe000-0xe03f (rw)
    Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
    IRQ: 161 (64308 events)
    Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00"
    Driver Info #0:
  Driver Status: i915 is active
  Driver Activation Cmd: "modprobe i915"
    Config Status: cfg=new, avail=yes, need=no, active=unknown
  43: None 00.0: 10002 LCD Monitor
    [Created at monitor.125]
    Unique ID: rdCR.R7Dpg_aaVOC
    Parent ID: _Znp.pq3kk9M9L4C
    Hardware Class: monitor
    Model: "LG Display LCD Monitor"
    Vendor: LGD "LG Display"
    Device: eisa 0x058b
    Resolution: 2560x1440@60Hz
    Size: 309x174 mm
    Year of Manufacture: 2016
    Week of Manufacture: 0
    Detailed Timings #0:
   Resolution: 2560x1440
   Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
     Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync
  Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #38 (VGA compatible controller)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-07 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago)
  UserGroups: microk8s sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+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 1867668] GsettingsChanges.txt

2020-03-17 Thread Vlad Svitlichniy
apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1867668/+attachment/5337876/+files/GsettingsChanges.txt

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

Title:
  Visual artifacts in Gnome Shell after upgrading to 20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
  minor (but pretty annoying) issues with Gnome Shell every time I load
  the system. The background image has some green/violet/black visual
  artifacts, and the text elements in Gnome Shell incorrectly display
  some of the symbol. Changing the background image removes the
  artifacts until the next reboot (but if I select the previous one
  without rebooting, then I still see the same artifacts, so it's
  probably cached somewhere). Restarting the shell via Alt+F2 `r`
  usually removes the artifacts from the background image, but the text
  issues are still present.

  The issues are reprodicable with and without extensions, with 1.0, 1.5
  and 2.0 display scaling factors applied, and they are not user-
  specific (i.e. I was able to reproduce them after creating a new user
  from scratch)

  As far as I can say, only Gnome Shell is affected. All the
  applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both
  "native" and flatpak) work fine without any issues

  Sometimes, the application icons are also affected (as you can see on
  one of the attached screenshots)

  ~> lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ~> apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.35.91-1ubuntu2
    Candidate: 3.35.91-1ubuntu2
    Version table:
   *** 3.35.91-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ~> gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling']

  ~> uname -r
  5.4.0-14-generic

  hwinfo (videocard, monitor):
  38: PCI 02.0: 0300 VGA compatible controller (VGA)
    [Created at pci.386]
    Unique ID: _Znp.pq3kk9M9L4C
    SysFS ID: /devices/pci:00/:00:02.0
    SysFS BusID: :00:02.0
    Hardware Class: graphics card
    Model: "Intel UHD Graphics 620"
    Vendor: pci 0x8086 "Intel Corporation"
    Device: pci 0x5917 "UHD Graphics 620"
    SubVendor: pci 0x17aa "Lenovo"
    SubDevice: pci 0x225c
    Revision: 0x07
    Driver: "i915"
    Driver Modules: "i915"
    Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable)
    Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable)
    I/O Ports: 0xe000-0xe03f (rw)
    Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
    IRQ: 161 (64308 events)
    Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00"
    Driver Info #0:
  Driver Status: i915 is active
  Driver Activation Cmd: "modprobe i915"
    Config Status: cfg=new, avail=yes, need=no, active=unknown
  43: None 00.0: 10002 LCD Monitor
    [Created at monitor.125]
    Unique ID: rdCR.R7Dpg_aaVOC
    Parent ID: _Znp.pq3kk9M9L4C
    Hardware Class: monitor
    Model: "LG Display LCD Monitor"
    Vendor: LGD "LG Display"
    Device: eisa 0x058b
    Resolution: 2560x1440@60Hz
    Size: 309x174 mm
    Year of Manufacture: 2016
    Week of Manufacture: 0
    Detailed Timings #0:
   Resolution: 2560x1440
   Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
     Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync
  Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #38 (VGA compatible controller)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-07 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago)
  UserGroups: microk8s sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+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 1867668] ProcCpuinfoMinimal.txt

2020-03-17 Thread Vlad Svitlichniy
apport information

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

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

Title:
  Visual artifacts in Gnome Shell after upgrading to 20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
  minor (but pretty annoying) issues with Gnome Shell every time I load
  the system. The background image has some green/violet/black visual
  artifacts, and the text elements in Gnome Shell incorrectly display
  some of the symbol. Changing the background image removes the
  artifacts until the next reboot (but if I select the previous one
  without rebooting, then I still see the same artifacts, so it's
  probably cached somewhere). Restarting the shell via Alt+F2 `r`
  usually removes the artifacts from the background image, but the text
  issues are still present.

  The issues are reprodicable with and without extensions, with 1.0, 1.5
  and 2.0 display scaling factors applied, and they are not user-
  specific (i.e. I was able to reproduce them after creating a new user
  from scratch)

  As far as I can say, only Gnome Shell is affected. All the
  applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both
  "native" and flatpak) work fine without any issues

  Sometimes, the application icons are also affected (as you can see on
  one of the attached screenshots)

  ~> lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ~> apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.35.91-1ubuntu2
    Candidate: 3.35.91-1ubuntu2
    Version table:
   *** 3.35.91-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ~> gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling']

  ~> uname -r
  5.4.0-14-generic

  hwinfo (videocard, monitor):
  38: PCI 02.0: 0300 VGA compatible controller (VGA)
    [Created at pci.386]
    Unique ID: _Znp.pq3kk9M9L4C
    SysFS ID: /devices/pci:00/:00:02.0
    SysFS BusID: :00:02.0
    Hardware Class: graphics card
    Model: "Intel UHD Graphics 620"
    Vendor: pci 0x8086 "Intel Corporation"
    Device: pci 0x5917 "UHD Graphics 620"
    SubVendor: pci 0x17aa "Lenovo"
    SubDevice: pci 0x225c
    Revision: 0x07
    Driver: "i915"
    Driver Modules: "i915"
    Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable)
    Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable)
    I/O Ports: 0xe000-0xe03f (rw)
    Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
    IRQ: 161 (64308 events)
    Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00"
    Driver Info #0:
  Driver Status: i915 is active
  Driver Activation Cmd: "modprobe i915"
    Config Status: cfg=new, avail=yes, need=no, active=unknown
  43: None 00.0: 10002 LCD Monitor
    [Created at monitor.125]
    Unique ID: rdCR.R7Dpg_aaVOC
    Parent ID: _Znp.pq3kk9M9L4C
    Hardware Class: monitor
    Model: "LG Display LCD Monitor"
    Vendor: LGD "LG Display"
    Device: eisa 0x058b
    Resolution: 2560x1440@60Hz
    Size: 309x174 mm
    Year of Manufacture: 2016
    Week of Manufacture: 0
    Detailed Timings #0:
   Resolution: 2560x1440
   Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
     Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync
  Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #38 (VGA compatible controller)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-07 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago)
  UserGroups: microk8s sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+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 1867668] monitors.xml.txt

2020-03-17 Thread Vlad Svitlichniy
apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1867668/+attachment/5337880/+files/monitors.xml.txt

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

Title:
  Visual artifacts in Gnome Shell after upgrading to 20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
  minor (but pretty annoying) issues with Gnome Shell every time I load
  the system. The background image has some green/violet/black visual
  artifacts, and the text elements in Gnome Shell incorrectly display
  some of the symbol. Changing the background image removes the
  artifacts until the next reboot (but if I select the previous one
  without rebooting, then I still see the same artifacts, so it's
  probably cached somewhere). Restarting the shell via Alt+F2 `r`
  usually removes the artifacts from the background image, but the text
  issues are still present.

  The issues are reprodicable with and without extensions, with 1.0, 1.5
  and 2.0 display scaling factors applied, and they are not user-
  specific (i.e. I was able to reproduce them after creating a new user
  from scratch)

  As far as I can say, only Gnome Shell is affected. All the
  applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both
  "native" and flatpak) work fine without any issues

  Sometimes, the application icons are also affected (as you can see on
  one of the attached screenshots)

  ~> lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ~> apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.35.91-1ubuntu2
    Candidate: 3.35.91-1ubuntu2
    Version table:
   *** 3.35.91-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ~> gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling']

  ~> uname -r
  5.4.0-14-generic

  hwinfo (videocard, monitor):
  38: PCI 02.0: 0300 VGA compatible controller (VGA)
    [Created at pci.386]
    Unique ID: _Znp.pq3kk9M9L4C
    SysFS ID: /devices/pci:00/:00:02.0
    SysFS BusID: :00:02.0
    Hardware Class: graphics card
    Model: "Intel UHD Graphics 620"
    Vendor: pci 0x8086 "Intel Corporation"
    Device: pci 0x5917 "UHD Graphics 620"
    SubVendor: pci 0x17aa "Lenovo"
    SubDevice: pci 0x225c
    Revision: 0x07
    Driver: "i915"
    Driver Modules: "i915"
    Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable)
    Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable)
    I/O Ports: 0xe000-0xe03f (rw)
    Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
    IRQ: 161 (64308 events)
    Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00"
    Driver Info #0:
  Driver Status: i915 is active
  Driver Activation Cmd: "modprobe i915"
    Config Status: cfg=new, avail=yes, need=no, active=unknown
  43: None 00.0: 10002 LCD Monitor
    [Created at monitor.125]
    Unique ID: rdCR.R7Dpg_aaVOC
    Parent ID: _Znp.pq3kk9M9L4C
    Hardware Class: monitor
    Model: "LG Display LCD Monitor"
    Vendor: LGD "LG Display"
    Device: eisa 0x058b
    Resolution: 2560x1440@60Hz
    Size: 309x174 mm
    Year of Manufacture: 2016
    Week of Manufacture: 0
    Detailed Timings #0:
   Resolution: 2560x1440
   Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
     Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync
  Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #38 (VGA compatible controller)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-07 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago)
  UserGroups: microk8s sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+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 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04

2020-03-17 Thread Vlad Svitlichniy
** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+attachment/5337906/+files/journal.txt

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

Title:
  Visual artifacts in Gnome Shell after upgrading to 20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
  minor (but pretty annoying) issues with Gnome Shell every time I load
  the system. The background image has some green/violet/black visual
  artifacts, and the text elements in Gnome Shell incorrectly display
  some of the symbol. Changing the background image removes the
  artifacts until the next reboot (but if I select the previous one
  without rebooting, then I still see the same artifacts, so it's
  probably cached somewhere). Restarting the shell via Alt+F2 `r`
  usually removes the artifacts from the background image, but the text
  issues are still present.

  The issues are reprodicable with and without extensions, with 1.0, 1.5
  and 2.0 display scaling factors applied, and they are not user-
  specific (i.e. I was able to reproduce them after creating a new user
  from scratch)

  As far as I can say, only Gnome Shell is affected. All the
  applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both
  "native" and flatpak) work fine without any issues

  Sometimes, the application icons are also affected (as you can see on
  one of the attached screenshots)

  ~> lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ~> apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.35.91-1ubuntu2
    Candidate: 3.35.91-1ubuntu2
    Version table:
   *** 3.35.91-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ~> gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling']

  ~> uname -r
  5.4.0-14-generic

  hwinfo (videocard, monitor):
  38: PCI 02.0: 0300 VGA compatible controller (VGA)
    [Created at pci.386]
    Unique ID: _Znp.pq3kk9M9L4C
    SysFS ID: /devices/pci:00/:00:02.0
    SysFS BusID: :00:02.0
    Hardware Class: graphics card
    Model: "Intel UHD Graphics 620"
    Vendor: pci 0x8086 "Intel Corporation"
    Device: pci 0x5917 "UHD Graphics 620"
    SubVendor: pci 0x17aa "Lenovo"
    SubDevice: pci 0x225c
    Revision: 0x07
    Driver: "i915"
    Driver Modules: "i915"
    Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable)
    Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable)
    I/O Ports: 0xe000-0xe03f (rw)
    Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
    IRQ: 161 (64308 events)
    Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00"
    Driver Info #0:
  Driver Status: i915 is active
  Driver Activation Cmd: "modprobe i915"
    Config Status: cfg=new, avail=yes, need=no, active=unknown
  43: None 00.0: 10002 LCD Monitor
    [Created at monitor.125]
    Unique ID: rdCR.R7Dpg_aaVOC
    Parent ID: _Znp.pq3kk9M9L4C
    Hardware Class: monitor
    Model: "LG Display LCD Monitor"
    Vendor: LGD "LG Display"
    Device: eisa 0x058b
    Resolution: 2560x1440@60Hz
    Size: 309x174 mm
    Year of Manufacture: 2016
    Week of Manufacture: 0
    Detailed Timings #0:
   Resolution: 2560x1440
   Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
     Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync
  Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #38 (VGA compatible controller)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-07 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago)
  UserGroups: microk8s sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+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 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04

2020-03-17 Thread Vlad Svitlichniy
** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+attachment/5337888/+files/dmesg.txt

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

Title:
  Visual artifacts in Gnome Shell after upgrading to 20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
  minor (but pretty annoying) issues with Gnome Shell every time I load
  the system. The background image has some green/violet/black visual
  artifacts, and the text elements in Gnome Shell incorrectly display
  some of the symbol. Changing the background image removes the
  artifacts until the next reboot (but if I select the previous one
  without rebooting, then I still see the same artifacts, so it's
  probably cached somewhere). Restarting the shell via Alt+F2 `r`
  usually removes the artifacts from the background image, but the text
  issues are still present.

  The issues are reprodicable with and without extensions, with 1.0, 1.5
  and 2.0 display scaling factors applied, and they are not user-
  specific (i.e. I was able to reproduce them after creating a new user
  from scratch)

  As far as I can say, only Gnome Shell is affected. All the
  applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both
  "native" and flatpak) work fine without any issues

  Sometimes, the application icons are also affected (as you can see on
  one of the attached screenshots)

  ~> lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ~> apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.35.91-1ubuntu2
    Candidate: 3.35.91-1ubuntu2
    Version table:
   *** 3.35.91-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ~> gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling']

  ~> uname -r
  5.4.0-14-generic

  hwinfo (videocard, monitor):
  38: PCI 02.0: 0300 VGA compatible controller (VGA)
    [Created at pci.386]
    Unique ID: _Znp.pq3kk9M9L4C
    SysFS ID: /devices/pci:00/:00:02.0
    SysFS BusID: :00:02.0
    Hardware Class: graphics card
    Model: "Intel UHD Graphics 620"
    Vendor: pci 0x8086 "Intel Corporation"
    Device: pci 0x5917 "UHD Graphics 620"
    SubVendor: pci 0x17aa "Lenovo"
    SubDevice: pci 0x225c
    Revision: 0x07
    Driver: "i915"
    Driver Modules: "i915"
    Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable)
    Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable)
    I/O Ports: 0xe000-0xe03f (rw)
    Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
    IRQ: 161 (64308 events)
    Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00"
    Driver Info #0:
  Driver Status: i915 is active
  Driver Activation Cmd: "modprobe i915"
    Config Status: cfg=new, avail=yes, need=no, active=unknown
  43: None 00.0: 10002 LCD Monitor
    [Created at monitor.125]
    Unique ID: rdCR.R7Dpg_aaVOC
    Parent ID: _Znp.pq3kk9M9L4C
    Hardware Class: monitor
    Model: "LG Display LCD Monitor"
    Vendor: LGD "LG Display"
    Device: eisa 0x058b
    Resolution: 2560x1440@60Hz
    Size: 309x174 mm
    Year of Manufacture: 2016
    Week of Manufacture: 0
    Detailed Timings #0:
   Resolution: 2560x1440
   Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
     Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync
  Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #38 (VGA compatible controller)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-07 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago)
  UserGroups: microk8s sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+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 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04

2020-03-17 Thread Vlad Svitlichniy
** Attachment added: "lspcik.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+attachment/5337907/+files/lspcik.txt

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

Title:
  Visual artifacts in Gnome Shell after upgrading to 20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
  minor (but pretty annoying) issues with Gnome Shell every time I load
  the system. The background image has some green/violet/black visual
  artifacts, and the text elements in Gnome Shell incorrectly display
  some of the symbol. Changing the background image removes the
  artifacts until the next reboot (but if I select the previous one
  without rebooting, then I still see the same artifacts, so it's
  probably cached somewhere). Restarting the shell via Alt+F2 `r`
  usually removes the artifacts from the background image, but the text
  issues are still present.

  The issues are reprodicable with and without extensions, with 1.0, 1.5
  and 2.0 display scaling factors applied, and they are not user-
  specific (i.e. I was able to reproduce them after creating a new user
  from scratch)

  As far as I can say, only Gnome Shell is affected. All the
  applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both
  "native" and flatpak) work fine without any issues

  Sometimes, the application icons are also affected (as you can see on
  one of the attached screenshots)

  ~> lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ~> apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.35.91-1ubuntu2
    Candidate: 3.35.91-1ubuntu2
    Version table:
   *** 3.35.91-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ~> gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling']

  ~> uname -r
  5.4.0-14-generic

  hwinfo (videocard, monitor):
  38: PCI 02.0: 0300 VGA compatible controller (VGA)
    [Created at pci.386]
    Unique ID: _Znp.pq3kk9M9L4C
    SysFS ID: /devices/pci:00/:00:02.0
    SysFS BusID: :00:02.0
    Hardware Class: graphics card
    Model: "Intel UHD Graphics 620"
    Vendor: pci 0x8086 "Intel Corporation"
    Device: pci 0x5917 "UHD Graphics 620"
    SubVendor: pci 0x17aa "Lenovo"
    SubDevice: pci 0x225c
    Revision: 0x07
    Driver: "i915"
    Driver Modules: "i915"
    Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable)
    Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable)
    I/O Ports: 0xe000-0xe03f (rw)
    Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
    IRQ: 161 (64308 events)
    Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00"
    Driver Info #0:
  Driver Status: i915 is active
  Driver Activation Cmd: "modprobe i915"
    Config Status: cfg=new, avail=yes, need=no, active=unknown
  43: None 00.0: 10002 LCD Monitor
    [Created at monitor.125]
    Unique ID: rdCR.R7Dpg_aaVOC
    Parent ID: _Znp.pq3kk9M9L4C
    Hardware Class: monitor
    Model: "LG Display LCD Monitor"
    Vendor: LGD "LG Display"
    Device: eisa 0x058b
    Resolution: 2560x1440@60Hz
    Size: 309x174 mm
    Year of Manufacture: 2016
    Week of Manufacture: 0
    Detailed Timings #0:
   Resolution: 2560x1440
   Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
     Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync
  Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #38 (VGA compatible controller)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-07 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago)
  UserGroups: microk8s sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+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 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04

2020-03-18 Thread Vlad Svitlichniy
Thank you, removing both "xserver-xorg-video-intel" package and
/etc/X11/xorg.conf.d/20-intel.conf file solved all the issues I had

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

Title:
  Visual artifacts in Gnome Shell after upgrading to 20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some
  minor (but pretty annoying) issues with Gnome Shell every time I load
  the system. The background image has some green/violet/black visual
  artifacts, and the text elements in Gnome Shell incorrectly display
  some of the symbol. Changing the background image removes the
  artifacts until the next reboot (but if I select the previous one
  without rebooting, then I still see the same artifacts, so it's
  probably cached somewhere). Restarting the shell via Alt+F2 `r`
  usually removes the artifacts from the background image, but the text
  issues are still present.

  The issues are reprodicable with and without extensions, with 1.0, 1.5
  and 2.0 display scaling factors applied, and they are not user-
  specific (i.e. I was able to reproduce them after creating a new user
  from scratch)

  As far as I can say, only Gnome Shell is affected. All the
  applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both
  "native" and flatpak) work fine without any issues

  Sometimes, the application icons are also affected (as you can see on
  one of the attached screenshots)

  ~> lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ~> apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.35.91-1ubuntu2
    Candidate: 3.35.91-1ubuntu2
    Version table:
   *** 3.35.91-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ~> gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling']

  ~> uname -r
  5.4.0-14-generic

  hwinfo (videocard, monitor):
  38: PCI 02.0: 0300 VGA compatible controller (VGA)
    [Created at pci.386]
    Unique ID: _Znp.pq3kk9M9L4C
    SysFS ID: /devices/pci:00/:00:02.0
    SysFS BusID: :00:02.0
    Hardware Class: graphics card
    Model: "Intel UHD Graphics 620"
    Vendor: pci 0x8086 "Intel Corporation"
    Device: pci 0x5917 "UHD Graphics 620"
    SubVendor: pci 0x17aa "Lenovo"
    SubDevice: pci 0x225c
    Revision: 0x07
    Driver: "i915"
    Driver Modules: "i915"
    Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable)
    Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable)
    I/O Ports: 0xe000-0xe03f (rw)
    Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
    IRQ: 161 (64308 events)
    Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00"
    Driver Info #0:
  Driver Status: i915 is active
  Driver Activation Cmd: "modprobe i915"
    Config Status: cfg=new, avail=yes, need=no, active=unknown
  43: None 00.0: 10002 LCD Monitor
    [Created at monitor.125]
    Unique ID: rdCR.R7Dpg_aaVOC
    Parent ID: _Znp.pq3kk9M9L4C
    Hardware Class: monitor
    Model: "LG Display LCD Monitor"
    Vendor: LGD "LG Display"
    Device: eisa 0x058b
    Resolution: 2560x1440@60Hz
    Size: 309x174 mm
    Year of Manufacture: 2016
    Week of Manufacture: 0
    Detailed Timings #0:
   Resolution: 2560x1440
   Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
     Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync
  Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #38 (VGA compatible controller)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-07 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago)
  UserGroups: microk8s sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+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 2072761] Re: Stuck arrow keys after switching workspaces

2024-08-05 Thread Vlad Arialin
Hi Daniel, thanks for you suggestion. I tried disabling all the
extensions and re-logging, but to no success - the stuck key is still
there, infinitely scrolling after a workspace switch.

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

Title:
  Stuck arrow keys after switching workspaces

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When shifting virtual desks (Alt-Ctrl-Left/Right arrow) one of the
  keys (most notably an arrow-key) are not registered as released when
  arriving at the destination desktop. E.e. I move one desktop to the
  right and after releasing Alt+Ctrl+Right-arrow the system behaves like
  I'm holding down the right-arrow key.

  PS I have upgraded from 23.10 using the distribution upgrade tool. It
  worked correctly in 23.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
  Uname: Linux 6.8.0-38-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 11 14:05:15 2024
  DistUpgraded: 2024-05-23 11:57:24,980 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.16, 6.8.0-35-generic, x86_64: installed
   virtualbox/7.0.16, 6.8.0-36-generic, x86_64: installed
   virtualbox/7.0.16, 6.8.0-38-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:07e6]
  InstallationDate: Installed on 2021-09-07 (1038 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  MachineType: Dell Inc. XPS 13 9370
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic 
root=UUID=d1885d5d-591e-4946-b6ff-8fc9ad9a601f ro nouveau.runpm=0 splash 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-05-23 (49 days ago)
  dmi.bios.date: 07/06/2022
  dmi.bios.release: 1.21
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.21.0
  dmi.board.name: 0W970W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA06:cvnDellInc.:ct10:cvr:sku07E6:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2072761/+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 2043507] [NEW] xdg-desktop-portal-gtk - asks two times "Select window to share with requesting application" when starting sharing a window in google meet

2023-11-14 Thread Vlad Gheorghe
Public bug reported:


Expected (initial) behavior in Google Meet was
During the meeting:
When I click "Present Now"
Then popup:  "Choose what to share with meet.google.com"
When I click "Window" and select window to share and click OK
Then the selected window is shared in the meet

Observed behaviour:
When I click "Present Now"
Then Popup1:  "Choose what to share with meet.google.com"
When I click "Window" tab
Then Popup2 "Select window to share with requesting application"
- and Popup1 window list remains empty
When I select a window and click Share
Then Popup1 > Window shows a small image of the selected window
When in Popup1 i click on the window image and Share
Then Popup3: "Select window to share with requesting application" and a list of 
open windows
When in Popup3 I select again the window to share and click Share
Then the selected window is shared in the meet


Based on the window title it seems that the extra popups (2/3 above) come from 
https://github.com/flatpak/xdg-desktop-portal-gtk/blob/1.14.0/src/screencastwidget.c


release: Ubuntu 22.04.3 LTS
xdg-desktop-portal-gtk/jammy,now 1.14.0-1build1 amd64 
Google Chrome: Version 119.0.6045.123 (Official Build) (64-bit)

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

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

Title:
  xdg-desktop-portal-gtk - asks two times "Select window to share with
  requesting application" when  starting sharing a window in google meet

Status in vino package in Ubuntu:
  New

Bug description:
  
  Expected (initial) behavior in Google Meet was
  During the meeting:
  When I click "Present Now"
  Then popup:  "Choose what to share with meet.google.com"
  When I click "Window" and select window to share and click OK
  Then the selected window is shared in the meet

  Observed behaviour:
  When I click "Present Now"
  Then Popup1:  "Choose what to share with meet.google.com"
  When I click "Window" tab
  Then Popup2 "Select window to share with requesting application"
  - and Popup1 window list remains empty
  When I select a window and click Share
  Then Popup1 > Window shows a small image of the selected window
  When in Popup1 i click on the window image and Share
  Then Popup3: "Select window to share with requesting application" and a list 
of open windows
  When in Popup3 I select again the window to share and click Share
  Then the selected window is shared in the meet


  
  Based on the window title it seems that the extra popups (2/3 above) come 
from 
  
https://github.com/flatpak/xdg-desktop-portal-gtk/blob/1.14.0/src/screencastwidget.c

  
  release: Ubuntu 22.04.3 LTS
  xdg-desktop-portal-gtk/jammy,now 1.14.0-1build1 amd64 
  Google Chrome: Version 119.0.6045.123 (Official Build) (64-bit)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/2043507/+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 2043507] Re: xdg-desktop-portal-gtk - asks two times "Select window to share with requesting application" when starting sharing a window in google meet

2023-11-15 Thread Vlad Gheorghe
** Package changed: vino (Ubuntu) => xdg-desktop-portal-gtk (Ubuntu)

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

Title:
  xdg-desktop-portal-gtk - asks two times "Select window to share with
  requesting application" when  starting sharing a window in google meet

Status in xdg-desktop-portal-gtk package in Ubuntu:
  New

Bug description:
  
  Expected (initial) behavior in Google Meet was
  During the meeting:
  When I click "Present Now"
  Then popup:  "Choose what to share with meet.google.com"
  When I click "Window" and select window to share and click OK
  Then the selected window is shared in the meet

  Observed behaviour:
  When I click "Present Now"
  Then Popup1:  "Choose what to share with meet.google.com"
  When I click "Window" tab
  Then Popup2 "Select window to share with requesting application"
  - and Popup1 window list remains empty
  When I select a window and click Share
  Then Popup1 > Window shows a small image of the selected window
  When in Popup1 i click on the window image and Share
  Then Popup3: "Select window to share with requesting application" and a list 
of open windows
  When in Popup3 I select again the window to share and click Share
  Then the selected window is shared in the meet


  
  Based on the window title it seems that the extra popups (2/3 above) come 
from 
  
https://github.com/flatpak/xdg-desktop-portal-gtk/blob/1.14.0/src/screencastwidget.c

  
  release: Ubuntu 22.04.3 LTS
  xdg-desktop-portal-gtk/jammy,now 1.14.0-1build1 amd64 
  Google Chrome: Version 119.0.6045.123 (Official Build) (64-bit)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2043507/+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 2017841] Re: Firefox drag/drop url onto desktop crashes ubuntu login session

2023-04-27 Thread Vlad Ziganshin
I have a similar situation. Firefox 112.0.2 When moving the mouse over 
thumbnails on the predominantly Youtube site, the browser closes spontaneously. 
Sometimes with exiting a Gnome desktop session. The reason is not clear. There 
is no such problem in the Chromium browser.
Ubuntu 23.04, Wayland session, CPU AMD Ryzen 9 7900х

** Description changed:

  Situation - while browsing I want to save page's url to desktop (likely any 
folder).
  I drag the url (by padlock icon in the address bar) onto my desktop folder to 
save shortcut to the page (for later view, to share it etc).
  The ubuntu user session (Wayland) will lock up and crash (bringing me back to 
user login screen) the moment I move the mouse (dragging the url) to FF windows 
boundary. Sometimes I'll get as far hovering over open desktop area but it'll 
crash withing seconds from me starting the task.
  No shortcut is saved to the desktop.
  FireFox can't restore session when launched again after login to system (I 
tried even restarting the pc before attempts at launching FF again). All you 
get is black/blank FF window and spinning cursor.
  Initially, the only way to get FF working again appeared to be to kill open 
FF window, switch to in private mode - this one will start fine and the next 
time FF would start normally. The session from before the crash would be gone 
though, really annoying for anyone with multiple open tabs. I'm quite certain 
that this was the reason why I'd given up on FF snap in 22.04 (normal/legacy 
install did not have the problem) but the same (?) problem on 23.04 forced me 
to have a closer look at what's going on, recovery options and to sing 
up/report the bug.
- What I've also noticed is that if following the crash I'd open in private FF 
windows 1st (instead of trying to open normal browser session only to have to 
terminate the browser showing blank window) and only then start normal FF 
session, FF would restore my tabs from before the crash. This is of little use 
now that I have to figure how to go back to my old session (I'll backtrack it 
somehow but this is pita). I'm tempted to pull the plug on snap FF again and 
move back to less fancy but more resilient setup (and with greater 
functionality). 
+ What I've also noticed is that if following the crash I'd open in private FF 
windows 1st (instead of trying to open normal browser session only to have to 
terminate the browser showing blank window) and only then start normal FF 
session, FF would restore my tabs from before the crash. This is of little use 
now that I have to figure how to go back to my old session (I'll backtrack it 
somehow but this is pita). I'm tempted to pull the plug on snap FF again and 
move back to less fancy but more resilient setup (and with greater 
functionality).
  Btw, the same crash can be triggered when doing drag and drop from bookmark 
or history manager in FF.
- Chromium snap install does not crash the login/Wayland session but url drag 
and drop attempt just does nothing anyway, no file is left on the desktop. 
Quite a basic functionality that works from any browser on Windows or macOS, 
seems like a great omission. An unfortunate choice if limited interactivity 
with user's own file system was just inherent to snap packaged software. I 
understand security but it's personal computer desktop environment 1st. 
+ Chromium snap install does not crash the login/Wayland session but url drag 
and drop attempt just does nothing anyway, no file is left on the desktop. 
Quite a basic functionality that works from any browser on Windows or macOS, 
seems like a great omission. An unfortunate choice if limited interactivity 
with user's own file system was just inherent to snap packaged software. I 
understand security but it's personal computer desktop environment 1st.
  I'm not sure of any security impact but this surely does not look good and is 
definitely a risk of data/work lost (luckily I did not have whole lot of open 
windows besides terminal).

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

Title:
  Firefox drag/drop url onto desktop crashes ubuntu login session

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Situation - while browsing I want to save page's url to desktop (likely any 
folder).
  I drag the url (by padlock icon in the address bar) onto my desktop folder to 
save shortcut to the page (for later view, to share it etc).
  The ubuntu user session (Wayland) will lock up and crash (bringing me back to 
user login screen) the moment I move the mouse (dragging the url) to FF windows 
boundary. Sometimes I'll get as far hovering over open desktop area but it'll 
crash withing seconds from me starting the task.
  No shortcut is saved to the desktop.
  FireFox can't restore session when launched again after login to system (I 
tried even restarting the pc before attempts at 

[Desktop-packages] [Bug 1716654] Re: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound

2018-08-14 Thread Vlad Lipskiy
Same: ASUS Prime x470-pro, Ryzen 7 2700X, 4.18.0 kernel. Cracking sound
on the mic/line-in on ALC1220. The only thing, that somewhat helped, is
increasing the default-fragment-size-msec to 75+ at
/etc/pulse/daemon.conf. But it is a workaround, and it doesn't remove
the cracking fully.

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

Title:
  [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Have checked under windows (same computer in dual-boot & same
  headset), and the sound is crystal clear, so 99% sure this is not a
  hardware problem.

  Motherboard is ASUS Crosshair Hero 6.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  paul   2587 F pulseaudio
   /dev/snd/controlC0:  paul   2587 F pulseaudio
   /dev/snd/controlC1:  paul   2587 F pulseaudio
   /dev/snd/controlC2:  paul   2587 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 11:48:05 2017
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic 
successful
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Pink Mic, Rear
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Generic successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, 
dropouts or crackling sound
  UpgradeStatus: Upgraded to artful on 2017-08-31 (11 days ago)
  dmi.bios.date: 07/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1501
  dmi.board.asset.tag: Default string
  dmi.board.name: CROSSHAIR VI HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1501:bd07/28/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-12T11:37:48.670242

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716654/+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 1788036] Re: nautilus crashed with SIGSEGV in tcache_get()

2018-09-01 Thread Vlad Ionescu
*** This bug is a duplicate of bug 1786650 ***
https://bugs.launchpad.net/bugs/1786650

** This bug has been marked a duplicate of bug 1786650
   nautilus crashed with SIGSEGV in tcache_get()

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

Title:
  nautilus crashed with SIGSEGV in tcache_get()

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  nautilus closed all of a sudden

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 20 23:26:18 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'216'
   b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency']"
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f7f019c1207 <__GI___libc_malloc+407>:   mov
(%rdx),%rdi
   PC (0x7f7f019c1207) ok
   source "(%rdx)" (0x6f73692e) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   tcache_get (tc_idx=0) at malloc.c:2943
   __GI___libc_malloc (bytes=17) at malloc.c:3050
   g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_strndup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_strsplit () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with SIGSEGV in tcache_get()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1788036/+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 1560722] Re: repositórios sumiram

2022-05-24 Thread Vlad Orlov
** Changed in: glib2.0 (Ubuntu)
   Status: New => Incomplete

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

Title:
  repositórios sumiram

Status in glib2.0 package in Ubuntu:
  Incomplete

Bug description:
  repositórios sumiram não sei o que fiz de errado.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: mate-notification-daemon 1.12.1-1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 22 19:41:03 2016
  ExecutablePath: /usr/lib/mate-notification-daemon/mate-notification-daemon
  InstallationDate: Installed on 2016-03-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  ProcCmdline: /usr/lib/mate-notification-daemon/mate-notification-daemon
  Signal: 5
  SourcePackage: mate-notification-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  Title: mate-notification-daemon crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1560722/+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 1359715] Re: Ghostscript runaway memory consumption during font search

2022-05-26 Thread Vlad Orlov
Marking as fixed according to the latest comments here

** Changed in: ghostscript (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Ghostscript runaway memory consumption during font search

Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  Linux Mint 17 (Qiana), Cinnamon 64-bit, kernel 3.13.0-24-generic #47-Ubuntu 
SMP x86_64 x86_64 x86_64 GNU/Linux
  Ghostscript version 9.10

  When Ghostscript searches for a specified font, if that font is not
  found in the Fontmap file, memory consumption shoots up, the system
  starts swapping and hangs.

  Tested on system (see above) with ~ 2GB memory.

  A simple way to reproduce, is to use the following procedure to
  attempt to display a font:

  1) Invoke ghostscript on 'prfont.ps'

  $ gs /usr/share/ghostscript/9.10/lib/prfont.ps
  GPL Ghostscript 9.10 (2013-08-30)
  Copyright (C) 2013 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Loading NimbusRomNo9L-Regu font from 
/usr/share/fonts/type1/gsfonts/n021003l.pfb... 3896292 2355421 3853784 2540955 
1 done.
  GS>

  2) At Ghostscript prompt, specify a random fontname - which we know
  does not exist - to 'DoFont':

  GS>/Somefont DoFont
  Can't find (or can't open) font file 
/usr/share/ghostscript/9.10/Resource/Font/Somefont.
  Can't find (or can't open) font file Somefont.
  Querying operating system for font files...

  Result: memory usage maxes out, system swaps and hangs.

  I expected Ghostscript to conclude the font search (without
  exhausating system resources!) and to report failure to locate the
  specified font.

  This problem always occurs, and affects any other program which
  invokes ghostscript and triggers a font search.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1359715/+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 1959027]

2022-02-10 Thread Vlad-zahorodnii
Not sure what the problem is, gtk apps refuse to use correct theme and
font settings on wayland. As far as I know, it can be worked around by
installing gtk xdg desktop portal.

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

Title:
  [snap] Various UI and theming issues when running in Plasma Wayland
  session

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

Bug description:
  Hello,

  after installing the current live image of Kubuntu Jammy, I tested the
  preinstalled Firefox snap on the Plasma Wayland session (which I use
  by default), and discovered multiple UI and theming issues:

  1. I had switched my global theme to Breeze Dark. Nevertheless Firefox
  used a light theme when I launched it for the first time.
  Interestingly, at further runs Firefox properly came up with a dark
  theme. But I had restarted my session in between and also had removed
  and reinstalled the Firefox snap, so it's possible that one of these
  actions triggered Firefox to finally use a dark theme.

  2. The font size in the UI is too big (compare with other KDE apps on
  screenshots).

  3. It apparently doesn't use Breeze (light or dark) as the UI theme,
  but something else (Adwaita I guess).

  4. The mouse cursor uses the wrong theme and is too big (it changes
  visible if move the cursor in and out of the Firefox window).

  5. If I click e.g. on "File -> Open file...", the file dialog is not
  the one from KDE but the one from GTK/Gnome. And the UI text is
  displayed in a rather jagged/distorted way (see screenshot).

  The issues described above do _not_ appear:
  * If I run Firefox as snap in Plasma X11 session.
  * If I run Firefox as deb (both Plasma Wayland and X11 session work fine).

  Kind regards, Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 96.0.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BuildID: 20220119190439
  CasperMD5CheckResult: pass
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Tue Jan 25 17:19:38 2022
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-01-25 (0 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220125.1)
  IpRoute:
   default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 
metric 100
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=96.0.2/20220119190439
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1959027/+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 1359308] Re: crash due to assertion in gail_focus_notify_when_idle: code should not be reached

2018-03-09 Thread Vlad Orlov
** Summary changed:

- mate-panel crashed when using window list
+ crash due to assertion in gail_focus_notify_when_idle: code should not be 
reached

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

Title:
  crash due to assertion in gail_focus_notify_when_idle: code should not
  be reached

Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  On an Ubuntu MATE utopic amd64 system, mate-panel 1.8.0+dfsg1-2
  crashed when I clicked on an item in the window list (located in the
  bottom panel). The panel reappeared and continued working correctly.
  This happened while apt-get was upgrading packages, but mate-panel was
  not one of the packages being upgraded.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: mate-panel 1.8.0+dfsg1-2
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  Date: Wed Aug 20 13:21:43 2014
  ExecutablePath: /usr/bin/mate-panel
  InstallationDate: Installed on 2014-08-19 (1 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731)
  ProcCmdline: mate-panel
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1359308/+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 1744744] Re: /usr/bin/mate-settings-daemon:5:XGetWindowProperty:gdk_check_wm_state_changed:gdk_x11_display_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_

2018-03-09 Thread Vlad Orlov
*** This bug is a duplicate of bug 1427332 ***
https://bugs.launchpad.net/bugs/1427332

** Package changed: mate-settings-daemon (Ubuntu) => gtk+3.0 (Ubuntu)

** This bug has been marked a duplicate of bug 1427332
   crash in XGetWindowProperty from gdk_check_wm_state_changed

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

Title:
  /usr/bin/mate-settings-
  
daemon:5:XGetWindowProperty:gdk_check_wm_state_changed:gdk_x11_display_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_translate_event

Status in gtk+3.0 package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1744744/+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 1751948] Re: /usr/bin/nautilus:5:XGetWindowProperty:read_settings:gdk_xsettings_manager_window_filter:gdk_event_apply_filters:gdk_event_source_translate_event

2018-03-09 Thread Vlad Orlov
*** This bug is a duplicate of bug 1201854 ***
https://bugs.launchpad.net/bugs/1201854

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

** This bug has been marked a duplicate of bug 1201854
   crash in XGetWindowProperty from read_settings from 
gdk_xsettings_manager_window_filter

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

Title:
  
/usr/bin/nautilus:5:XGetWindowProperty:read_settings:gdk_xsettings_manager_window_filter:gdk_event_apply_filters:gdk_event_source_translate_event

Status in gtk+3.0 package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1751948/+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 1201854] Re: gnome-settings-daemon crashed with signal 5 in _XReply()

2018-03-09 Thread Vlad Orlov
** Package changed: gnome-settings-daemon (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- gnome-settings-daemon crashed with signal 5 in _XReply()
+ crash in XGetWindowProperty from read_settings from 
gdk_xsettings_manager_window_filter

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

Title:
  crash in XGetWindowProperty from read_settings from
  gdk_xsettings_manager_window_filter

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  This happened immediately after a reboot for updates. Immediately
  after I checked for more updates and there were some, meaning this bug
  might already be fixed. About the updates, I noticed that a few
  'failed to download' but running sudo apt-get upgrade they installed
  fine. I don't know if this is related but it might be. This has
  probably happened several times, but I don't think it's a regular
  pattern. Running 13.10 Alpha. Otherwise seems to be pretty stable so
  far despite the minor bugs.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.6.4-0ubuntu15
  ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  Date: Fri Jul 12 23:43:27 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ExecutableTimestamp: 1372327096
  InstallationDate: Installed on 2013-06-14 (28 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MarkForUpload: True
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ProcCwd: /home/karatekid
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-settings-daemon crashed with signal 5 in _XReply()
  UpgradeStatus: Upgraded to saucy on 2013-07-12 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1201854/+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 1427332] Re: nautilus crashed with signal 5 in _XReply()

2018-03-09 Thread Vlad Orlov
** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- nautilus crashed with signal 5 in _XReply()
+ crash in XGetWindowProperty from gdk_check_wm_state_changed

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

Title:
  crash in XGetWindowProperty from gdk_check_wm_state_changed

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  none

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  Date: Mon Mar  2 16:17:00 2015
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-10-24 (129 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: nautilus
  ProcEnviron:
   LANGUAGE=es_UY:es
   PATH=(custom, no user)
   LANG=es_UY.UTF-8
   SHELL=/bin/bash
   TERM=unknown
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus crashed with signal 5 in _XReply()
  UpgradeStatus: Upgraded to vivid on 2015-01-05 (56 days ago)
  UserGroups:
   
  usr_lib_nautilus:
   brasero3.12.0-0ubuntu2
   evince 3.14.1-0ubuntu5
   file-roller3.14.2-0ubuntu4
   gnome-terminal 3.14.2-0ubuntu2
   nautilus-share 0.7.3-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1427332/+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 1678693] Re: mate-notification-daemon crashed with SIGABRT in g_assertion_message()

2018-03-09 Thread Vlad Orlov
*** This bug is a duplicate of bug 1627564 ***
https://bugs.launchpad.net/bugs/1627564

** Package changed: mate-notification-daemon (Ubuntu) => gtk+3.0
(Ubuntu)

** This bug has been marked a duplicate of bug 1627564
   crash due to assertion in ensure_surface_for_gicon

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

Title:
  mate-notification-daemon crashed with SIGABRT in g_assertion_message()

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  occurred while installing packages

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-notification-daemon 1.18.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  2 23:04:26 2017
  ExecutablePath: /usr/lib/mate-notification-daemon/mate-notification-daemon
  InstallationDate: Installed on 2017-04-01 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  ProcCmdline: /usr/lib/mate-notification-daemon/mate-notification-daemon
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_US
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: mate-notification-daemon
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-notification-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1678693/+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 1627564] Re: was doing an upgrade and this created a trouble report

2018-03-09 Thread Vlad Orlov
** Package changed: lightdm-gtk-greeter (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- was doing an upgrade and this created a trouble report
+ crash due to assertion in ensure_surface_for_gicon

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

Title:
  crash due to assertion in ensure_surface_for_gicon

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  bubble opened up indicating there was a failure during the latest
  update.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: lightdm-gtk-greeter 2.0.1-2ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.4.0-9136-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  Date: Sun Sep 25 20:37:06 2016
  ExecutablePath: /usr/sbin/lightdm-gtk-greeter
  InstallationDate: Installed on 2016-08-04 (52 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727)
  ProcCmdline: /usr/sbin/lightdm-gtk-greeter
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: lightdm-gtk-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
   [greeter]
   theme-name = Lubuntu-dark-panel
  mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 
2016-08-14T22:33:57.293011

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1627564/+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 1594609] Re: /usr/bin/mate-panel:6:g_assertion_message:g_assertion_message_expr:get_icon_fallback:gtk_recent_chooser_menu_create_item:idle_populate_func

2018-03-09 Thread Vlad Orlov
** Package changed: mate-panel (Ubuntu) => gtk+2.0 (Ubuntu)

** Summary changed:

- 
/usr/bin/mate-panel:6:g_assertion_message:g_assertion_message_expr:get_icon_fallback:gtk_recent_chooser_menu_create_item:idle_populate_func
+ crash due to assertion in get_icon_fallback from 
gtk_recent_chooser_menu_create_item

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

Title:
  crash due to assertion in get_icon_fallback from
  gtk_recent_chooser_menu_create_item

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-panel.  This problem was most recently seen with
  version 1.12.2-1, the problem page at
  https://errors.ubuntu.com/problem/96ae198a578de2353a3cc778896a83a10ab7d131
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1594609/+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 1752506] Re: zenity crashed with SIGABRT in g_assertion_message()

2018-03-10 Thread Vlad Orlov
*** This bug is a duplicate of bug 1627564 ***
https://bugs.launchpad.net/bugs/1627564

** This bug is no longer a duplicate of bug 1752533
   zenity (6) g_assertion_message → g_assertion_message_error → 
ensure_surface_for_gicon → gtk_icon_helper_load_surface → 
gtk_icon_helper_ensure_surface
** This bug has been marked a duplicate of bug 1627564
   crash due to assertion in ensure_surface_for_gicon

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

Title:
  zenity crashed with SIGABRT in g_assertion_message()

Status in zenity package in Ubuntu:
  New

Bug description:
  no idea, just asked to submit the error report

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: zenity 3.27.90-1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Thu Mar  1 02:21:03 2018
  ExecutablePath: /usr/bin/zenity
  InstallationDate: Installed on 2015-03-19 (1077 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: zenity --warning --text The\ system\ is\ running\ in\ 
low-graphics\ mode\\n\\nYour\ screen,\ graphics\ card,\ and\ input\ 
device\ settings\\ncould\ not\ be\ detected\ correctly.\ \ You\ will\ need\ to\ 
configure\ these\ yourself.
  Signal: 6
  SourcePackage: zenity
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_error () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: zenity crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1752506/+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 1752533] Re: zenity (6) g_assertion_message → g_assertion_message_error → ensure_surface_for_gicon → gtk_icon_helper_load_surface → gtk_icon_helper_ensure_surface

2018-03-10 Thread Vlad Orlov
*** This bug is a duplicate of bug 1627564 ***
https://bugs.launchpad.net/bugs/1627564

** This bug has been marked a duplicate of bug 1627564
   crash due to assertion in ensure_surface_for_gicon

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

Title:
  zenity (6) g_assertion_message → g_assertion_message_error →
  ensure_surface_for_gicon → gtk_icon_helper_load_surface →
  gtk_icon_helper_ensure_surface

Status in zenity package in Ubuntu:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1752533/+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 1718543] Re: gnome-shell-extension-prefs crashed with SIGABRT in g_assertion_message_expr() "assertion failed: (destination)" from ensure_surface_for_gicon()

2018-03-10 Thread Vlad Orlov
*** This bug is a duplicate of bug 1627564 ***
https://bugs.launchpad.net/bugs/1627564

** This bug has been marked a duplicate of bug 1627564
   crash due to assertion in ensure_surface_for_gicon

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

Title:
  gnome-shell-extension-prefs crashed with SIGABRT in
  g_assertion_message_expr() "assertion failed: (destination)" from
  ensure_surface_for_gicon()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crashed when changing Dash to Dock settings

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 20 00:56:33 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  InstallationDate: Installed on 2017-06-01 (110 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-shell-extension-prefs dash-to-d...@micxgx.gmail.com
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-shell-extension-prefs crashed with SIGABRT in 
g_assertion_message()
  UpgradeStatus: Upgraded to artful on 2017-06-10 (101 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718543/+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 1580686] Re: scp-dbus-service.py crashed with signal 5 in _XReply()

2018-03-10 Thread Vlad Orlov
** Package changed: system-config-printer (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- scp-dbus-service.py crashed with signal 5 in _XReply()
+ crash in XTranslateCoordinates from gdk_window_x11_get_root_coords

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

Title:
  crash in XTranslateCoordinates from gdk_window_x11_get_root_coords

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Printed 3 copys of one document with setting 2 pages on 1 sheet. Job
  printed normally but crash report appeared afterwards.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: system-config-printer-gnome 1.5.7+20160212-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog: E [11/May/2016:18:27:44 +0200] [cups-deviced] PID 13760 
(gutenprint52+usb) stopped with status 1!
  CurrentDesktop: XFCE
  Date: Wed May 11 18:32:16 2016
  ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py
  InstallationDate: Installed on 2016-04-30 (11 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterpreterPath: /usr/bin/python3.5
  Lpstat: device for FS-1010: usb://Kyocera/FS-1010?serial=XAL4584303
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  PackageArchitecture: all
  Papersize: a4
  PpdFiles: FS-1010: Kyocera Mita FS-1010
  ProcCmdline: /usr/bin/python3 
/usr/share/system-config-printer/scp-dbus-service.py
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=6d707d68-42fe-492a-8d56-5bd131334069 ro quiet splash vt.handoff=7
  Signal: 5
  SourcePackage: system-config-printer
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XTranslateCoordinates () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gtk_tooltip_trigger_tooltip_query () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: scp-dbus-service.py crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare sudo video
  dmi.bios.date: 03/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B150-HD3P-CF
  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: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd03/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB150-HD3P-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1580686/+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 1726661] Re: nautilus-desktop crashed with signal 5 in gnome_bg_create_surface()

2018-03-10 Thread Vlad Orlov
*** This bug is a duplicate of bug 1071155 ***
https://bugs.launchpad.net/bugs/1071155

** This bug has been marked a duplicate of bug 1071155
   nautilus crashed with signal 5 in _XReply()

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

Title:
  nautilus-desktop crashed with signal 5 in gnome_bg_create_surface()

Status in nautilus package in Ubuntu:
  New

Bug description:
  This crash happened just after the system booted. I had installed a
  bunch of themes from Github previous to that. I also have nemo 3
  installed from noobslab.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 07:12:23 2017
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: nautilus-desktop
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   gdk_flush () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus-desktop crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726661/+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 1071155] Re: nautilus crashed with signal 5 in gdk_flush from make_root_pixmap from gnome_bg_create_surface

2018-03-10 Thread Vlad Orlov
** Summary changed:

- nautilus crashed with signal 5 in _XReply()
+ nautilus crashed with signal 5 in gdk_flush from make_root_pixmap from 
gnome_bg_create_surface

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

Title:
  nautilus crashed with signal 5 in gdk_flush from make_root_pixmap from
  gnome_bg_create_surface

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Unity was being glitchy so I ran "$ unity --replace". Nautilus then
  crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Thu Oct 25 17:36:13 2012
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'958x502+0+548'"
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: nautilus -n
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   gdk_flush () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus crashed with signal 5 in _XReply()
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (6 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1071155/+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 1617552] Re: mate-notification-daemon crashed with SIGABRT in __assert_fail_base()

2018-03-10 Thread Vlad Orlov
*** This bug is a duplicate of bug 1598142 ***
https://bugs.launchpad.net/bugs/1598142

** Package changed: gtk+3.0 (Ubuntu) => ubuntu

** This bug has been marked a duplicate of bug 1598142
   mate-notification-daemon assert failure: mate-notification-daemon: 
../../../../src/cairo.c:305: cairo_destroy: Assertion 
`CAIRO_REFERENCE_COUNT_HAS_REFERENCE (&cr->ref_count)' failed.

** This bug is no longer a duplicate of bug 1598142
   mate-notification-daemon assert failure: mate-notification-daemon: 
../../../../src/cairo.c:305: cairo_destroy: Assertion 
`CAIRO_REFERENCE_COUNT_HAS_REFERENCE (&cr->ref_count)' failed.

** Package changed: ubuntu => mate-notification-daemon (Ubuntu)

** This bug has been marked a duplicate of bug 1598142
   mate-notification-daemon assert failure: mate-notification-daemon: 
../../../../src/cairo.c:305: cairo_destroy: Assertion 
`CAIRO_REFERENCE_COUNT_HAS_REFERENCE (&cr->ref_count)' failed.

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

Title:
  mate-notification-daemon crashed with SIGABRT in __assert_fail_base()

Status in mate-notification-daemon package in Ubuntu:
  New

Bug description:
  Just popped out of nowhere.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: mate-notification-daemon 1.14.1-1build1
  ProcVersionSignature: Ubuntu 4.4.0-9134.53-powerpc64-smp 4.4.15
  Uname: Linux 4.4.0-9134-powerpc64-smp ppc64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  CurrentDesktop: MATE
  Date: Sat Aug 27 13:10:34 2016
  ExecutablePath: /usr/lib/mate-notification-daemon/mate-notification-daemon
  InstallationDate: Installed on 2016-03-26 (153 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta powerpc 
(20160326)
  ProcCmdline: /usr/lib/mate-notification-daemon/mate-notification-daemon
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=de_AT:de
   LANG=de_AT.UTF-8
  Signal: 6
  SourcePackage: mate-notification-daemon
  StacktraceTop:
   raise () from /lib/powerpc-linux-gnu/libc.so.6
   abort () from /lib/powerpc-linux-gnu/libc.so.6
   ?? () from /lib/powerpc-linux-gnu/libc.so.6
   __assert_fail () from /lib/powerpc-linux-gnu/libc.so.6
   cairo_destroy () from /usr/lib/powerpc-linux-gnu/libcairo.so.2
  Title: mate-notification-daemon crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-notification-daemon/+bug/1617552/+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 1535944] Re: /usr/lib/mate-panel/wnck-applet:11:g_type_check_instance_cast:pager_update:display_workspace_names_changed:g_cclosure_marshal_VOID__STRINGv:_g_closure_invoke_va

2018-03-10 Thread Vlad Orlov
*** This bug is a duplicate of bug 1555993 ***
https://bugs.launchpad.net/bugs/1555993

Random crash after display_workspace_names_changed, fixed as bug
1555993.

** Changed in: libwnck (Ubuntu)
   Status: New => Invalid

** Changed in: mate-panel (Ubuntu)
   Status: Invalid => Fix Released

** This bug has been marked a duplicate of bug 1555993
   wnck-applet (window list, workspace switcher) crashes on moving/removing 
applet

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

Title:
  /usr/lib/mate-panel/wnck-
  
applet:11:g_type_check_instance_cast:pager_update:display_workspace_names_changed:g_cclosure_marshal_VOID__STRINGv:_g_closure_invoke_va

Status in libwnck package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-panel.  This problem was most recently seen with
  version 1.10.1+gfdl1-1, the problem page at
  https://errors.ubuntu.com/problem/ccf5af49f1c8672b263e1bb5e90d637a8c027758
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwnck/+bug/1535944/+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 1555331] Re: crash in g_slist_remove_all from gtk_rc_clear_realized_style

2018-03-10 Thread Vlad Orlov
** Summary changed:

- mate-panel crashed with SIGSEGV in g_slist_remove_all()
+ crash in g_slist_remove_all from gtk_rc_clear_realized_style

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

Title:
  crash in g_slist_remove_all from gtk_rc_clear_realized_style

Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Won't Fix

Bug description:
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: mate-panel 1.12.2-1
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Mar  9 22:49:55 2016
  ExecutablePath: /usr/bin/mate-panel
  InstallationDate: Installed on 2016-02-25 (12 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  ProcCmdline: mate-panel
  SegvAnalysis:
   Segfault happened at: 0x7f4fa6439b1c :cmp
%rbp,(%rdi)
   PC (0x7f4fa6439b1c) ok
   source "%rbp" ok
   destination "(%rdi)" (0x160016) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-panel
  StacktraceTop:
   g_slist_remove_all () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_rc_reset_styles () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  Title: mate-panel crashed with SIGSEGV in g_slist_remove_all()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1555331/+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 1670898] Re: crash after spi_cache_foreach from impl_GetItems

2018-03-10 Thread Vlad Orlov
** Summary changed:

- 
/usr/bin/mate-settings-daemon:11:g_type_check_instance_is_fundamentally_a:g_object_ref:g_hash_table_foreach:spi_cache_foreach:impl_GetItems
+ crash after spi_cache_foreach from impl_GetItems

** Package changed: mate-settings-daemon (Ubuntu) => at-spi2-atk
(Ubuntu)

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

Title:
  crash after spi_cache_foreach from impl_GetItems

Status in at-spi2-atk package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mate-settings-daemon.  This problem was most recently seen with package version 
1.12.1-2build1, the problem page at 
https://errors.ubuntu.com/problem/f507ea21d5337991672738917ae190e6e86f76e2 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1670898/+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 1620708] Re: /usr/bin/caja:7:meta_tree_needs_rereading:meta_tree_refresh:meta_tree_lookup_by_name:meta_lookup_cache_lookup_path:g_daemon_vfs_local_file_add_info

2018-03-10 Thread Vlad Orlov
*** This bug is a duplicate of bug 580958 ***
https://bugs.launchpad.net/bugs/580958

** Package changed: caja (Ubuntu) => gvfs (Ubuntu)

** This bug has been marked a duplicate of bug 580958
   nautilus crashed with signal 7

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

Title:
  
/usr/bin/caja:7:meta_tree_needs_rereading:meta_tree_refresh:meta_tree_lookup_by_name:meta_lookup_cache_lookup_path:g_daemon_vfs_local_file_add_info

Status in gvfs package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding caja.  This problem was most recently seen with version
  1.12.7-1, the problem page at
  https://errors.ubuntu.com/problem/acdafa3ef66918969b8aa8b7b780f5bf9f61e934
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1620708/+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 580958] Re: nautilus crashed with signal 7

2018-03-10 Thread Vlad Orlov
** Package changed: nautilus (Ubuntu) => gvfs (Ubuntu)

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

Title:
  nautilus crashed with signal 7

Status in Nautilus:
  Expired
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  Nautilus crashes if it has not been used for some time (I don't now
  the exact time but maybe 15 minutes). If it is already started it
  crashes and if I start it it crashes. But it works if I start it a
  second time, but crashes again when it has been idle for 15 minutes.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: nautilus 1:2.30.1-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  NonfreeKernelModules: openafs nvidia
  Architecture: i386
  CrashCounter: 1
  Date: Sat May 15 15:15:29 2010
  ExecutablePath: /usr/bin/nautilus
  ProcCmdline: nautilus
  ProcEnviron:
   LANGUAGE=sv_SE:sv:en_GB:en
   PATH=(custom, no user)
   LANG=sv_SE.utf8
   SHELL=/bin/bash
  Signal: 7
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/gio/modules/libgvfsdbus.so
  Title: nautilus crashed with signal 7
  UserGroups: admin audio plugdev pulse

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/580958/+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 1569068] Re: /usr/bin/mate-settings-daemon:ERROR:pulse/glib-mainloop.c:407:glib_defer_free: assertion failed: (!e->dead)

2018-03-11 Thread Vlad Orlov
** Package changed: mate-settings-daemon (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  /usr/bin/mate-settings-daemon:ERROR:pulse/glib-
  mainloop.c:407:glib_defer_free: assertion failed: (!e->dead)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-settings-daemon.  This problem was most recently seen
  with version 1.12.1-2build1, the problem page at
  https://errors.ubuntu.com/problem/1b3afc018f02173501b79b75651ec747d69300b7
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1569068/+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 1613363] Re: /usr/bin/engrampa:11:g_type_check_instance_is_fundamentally_a:g_object_get_qdata:detach_from_style:clear_cache:ensure_cache_up_to_date

2018-03-13 Thread Vlad Orlov
** Package changed: engrampa (Ubuntu) => gtk+2.0 (Ubuntu)

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

Title:
  
/usr/bin/engrampa:11:g_type_check_instance_is_fundamentally_a:g_object_get_qdata:detach_from_style:clear_cache:ensure_cache_up_to_date

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding engrampa.  This problem was most recently seen with version
  1.12.0-2, the problem page at
  https://errors.ubuntu.com/problem/2f8bf782a90fe3ab90595f0ab71cdafa82f08b7f
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1613363/+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 1755555] Re: nautilus crashed with SIGSEGV while trying to install Budgie Desktop applet

2018-03-13 Thread Vlad Tarasiuk
** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGSEGV  while trying to install Budgie Desktop
  applet

Status in nautilus package in Ubuntu:
  New

Bug description:
  This problem happens on Ubuntu Budgie 18.04 when first time in session
  I try to install applet using Budgie Desktop Applets. Seems like it
  only happens when installing Global menu applet (budgie-appmenu-
  applet) which afterwards also does not show up in applet list, though
  apt says it installed. But Pixel Saver applet (budgie-pixel-saver-
  applet) which has similar functionality installs without any problems
  and works fine.

  Release:  18.04
  Description:  Ubuntu Bionic Beaver (development branch)

  budgie-appmenu-applet:
Installed: 0.6.92+repack1-3ubuntu1

  budgie-pixel-saver-applet:
Installed: 4.0+git20171102.30c1f94-0ubuntu1~bionic

  nautilus:
Installed: 1:3.26.2-0ubuntu3.1

  
  I should also mention that I could not login and got freezes after 
installation without nomodeset because of Nvidia drivers. I installed 
nvidia-384 driver and deleted xserver-xorg-video-nvidia-390 to fix these 
freezes and be able to login to desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 13 19:11:31 2018
  Disassembly: No registers.
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+108+80'"
   b'org.gnome.nautilus.desktop' b'network-icon-visible' b'true'
   b'org.gnome.nautilus.desktop' b'volumes-visible' b'true'
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180312)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  Registers: The program has no registers now.
  SegvAnalysis: Failure: invalid literal for int() with base 16: 'program'
  Signal: 11
  SourcePackage: nautilus
  Stacktrace: No stack.
  StacktraceTop:
   
  ThreadStacktrace:
   
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/175/+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 1774635] Re: Xorg crashes - SIGABRT - after resuming from suspend

2018-06-01 Thread Vlad Dinulescu
** Information type changed from Private to Public

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

Title:
  Xorg crashes - SIGABRT - after resuming from suspend

Status in xorg-server package in Ubuntu:
  New

Bug description:
  In the last months, Xorg started crashing randomly after I resume from sleep. 
  I've installed Xubuntu 18.04 from scratch (keeping only the /home partition) 
hoping that the problem would be gone. But it isn't. 

  It seems to be related to the external monitor - ie when there is an
  external monitor plugged in and I suspend the computer, and when I
  resume there's only the laptop. But it doesn't always happen, so I
  don't have clear steps for reproducing.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  Date: Thu May 31 18:01:17 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1523633505
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e3]
  InstallationDate: Installed on 2018-05-22 (10 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. XPS 12-9Q33
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcCwd: /
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=0da52507-c787-46d7-9266-d53448c18283 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.asset.tag: 0
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1774635/+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 1421808] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xf86VTEnter()

2018-06-07 Thread Vlad Dinulescu
Hello,

For me this started to manifest in the last months; Xorg started crashing 
randomly after I resume from sleep.
In the meantime, I've installed Xubuntu 18.04 from scratch (keeping only the 
/home partition) hoping that the problem would be gone. But it isn't.

It seems to be related to the external monitor - ie when there is an
external monitor plugged in and I suspend the computer, and when I
resume there's only the laptop. But it doesn't always happen, so I don't
have clear steps for reproducing.  (My bug report was marked as
duplicate of this bug, https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1774635)

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

Title:
  Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xf86VTEnter()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  The error is reported on boot up.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb  8 12:36:52 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2013-04-24 (660 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130403)
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to vivid on 2015-01-30 (14 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1421808/+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 1421808] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xf86VTEnter()

2018-06-11 Thread Vlad Dinulescu
Hello,

Reproduction steps:

1. connect an external monitor (I connect mine through mini-DisplayPort, and I 
use only the external monitor, I do NOT use both the laptop screen and the 
external monitor)
2. with the external monitor connected, suspend the computer (I do it by 
running xfce4-session-logout --suspend, I have a shortcut for this)
3. with the laptop suspended, disconnect the monitor 
4. open the laptop, you'll be shown the Xdm login screen
5. log in
6. Xorg will crash, it will restart, and you'll see again the Xdm login screen


What works (how to avoid the crash)
1. connect an external monitor
2. before suspending the laptop, disconnect the external monitor
3. suspend the laptop
4. open the laptop, everything will be ok

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

Title:
  Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xf86VTEnter()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  The error is reported on boot up.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb  8 12:36:52 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2013-04-24 (660 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130403)
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to vivid on 2015-01-30 (14 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1421808/+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 1846890] Re: Unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so

2019-10-06 Thread Vlad Orlov
** Package changed: pluma (Ubuntu) => libpeas (Ubuntu)

** Summary changed:

- Unable to enable plugins External tools, Python Console, Quick Open, 
Snippets) because of missed 
/usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so
+ Pluma: unable to enable plugins External tools, Python Console, Quick Open, 
Snippets) because of missed 
/usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so

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

Title:
  Pluma: unable to enable plugins External tools, Python Console, Quick
  Open, Snippets) because of missed /usr/lib/x86_64-linux-
  gnu/libpeas-1.0/loaders/libpythonloader.so

Status in libpeas package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 19.10
  2. Launch Pluma
  3. Go to Edit -> Preferences, switch to Plugins tab
  4. Try enable all plugins by checking their checkmarks

  Expected results:
  * all plugins are enabled without errors or warnings;

  Actual results:
  * plugin(s) are not enabled, show the following errors in `pluma`'s terminal:

  ```
  $ pluma

  (pluma:1685): libpeas-WARNING **: 19:20:59.204: Failed to load module
  'pythonloader': /usr/lib/x86_64-linux-
  gnu/libpeas-1.0/loaders/libpythonloader.so: cannot open shared object
  file: No such file or directory

  (pluma:1685): libpeas-WARNING **: 19:20:59.205: Could not load plugin loader 
'python'
  ```

  Note: in previous releases the `libpythonloader.so` was located in
  libpeas-1.0-python2loader package (see
  
https://packages.ubuntu.com/search?suite=disco&arch=amd64&mode=exactfilename&searchon=contents&keywords=libpythonloader.so
  ) but this file is missed in 19.10 repository.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pluma 1.22.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Oct  5 19:23:02 2019
  InstallationDate: Installed on 2019-10-05 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191004)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1846890/+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 1846890] Re: Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonload

2019-10-06 Thread Vlad Orlov
** Attachment added: "Debdiff to fix Python 2 loader name"
   
https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1846890/+attachment/5294753/+files/libpeas-debdiff-eoan

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

Title:
  Pluma: unable to enable plugins External tools, Python Console, Quick
  Open, Snippets) because of missed /usr/lib/x86_64-linux-
  gnu/libpeas-1.0/loaders/libpythonloader.so

Status in libpeas package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 19.10
  2. Launch Pluma
  3. Go to Edit -> Preferences, switch to Plugins tab
  4. Try enable all plugins by checking their checkmarks

  Expected results:
  * all plugins are enabled without errors or warnings;

  Actual results:
  * plugin(s) are not enabled, show the following errors in `pluma`'s terminal:

  ```
  $ pluma

  (pluma:1685): libpeas-WARNING **: 19:20:59.204: Failed to load module
  'pythonloader': /usr/lib/x86_64-linux-
  gnu/libpeas-1.0/loaders/libpythonloader.so: cannot open shared object
  file: No such file or directory

  (pluma:1685): libpeas-WARNING **: 19:20:59.205: Could not load plugin loader 
'python'
  ```

  Note: in previous releases the `libpythonloader.so` was located in
  libpeas-1.0-python2loader package (see
  
https://packages.ubuntu.com/search?suite=disco&arch=amd64&mode=exactfilename&searchon=contents&keywords=libpythonloader.so
  ) but this file is missed in 19.10 repository.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pluma 1.22.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Oct  5 19:23:02 2019
  InstallationDate: Installed on 2019-10-05 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191004)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1846890/+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 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-10-07 Thread Vlad Orlov
Sorry, completely forgot about it... :-/

So bug 1828639 is now fixed. I guess no need to fix gconf triggers now?

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

Title:
  [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  During system upgrades, triggers for gconf2 might activate too early,
  while some of its dependencies aren't configured yet. This happens
  several times in a loop and stops the upgrade in the end.

  The attached debdiffs fix this issue by changing interest to interest-
  noawait in debian/gconf2.triggers file. The triggers will now activate
  near the end of upgrade.

  In addition, the debdiff for Bionic also contains a fix for FTBFS (bug
  1834211).

  [Test Case]

  Triggers for gconf2 are usually activated on changes in
  /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with
  GNOME) is most suitable for reproducing the issue. To reproduce it,
  install that edition, apply all updates, then try upgrading to the
  next release.

  [Regression Potential]

  None, interest-noawait trigger is known to work well in other packages
  (comment 31).

  [Other Info]

  Even if Cosmic goes EOL next month, the fix for it might be worth it
  for release upgrades.

  [Original Description]

  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome.
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+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 1576539] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  bug happened while i'm upgrading ubuntu version from 15.10 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri Apr 29 08:16:36 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-03-05 (54 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-04-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1576539/+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 1573662] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  error occured during regular "do-release-upgrade". System remains in
  unstable condition. dpkg --configure -a / apt-get -f install continues
  the process (still running).

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Fri Apr 22 17:05:44 2016
  DuplicateSignature: package:gconf2:3.2.6-3ubuntu6:Abhängigkeitsprobleme - 
Trigger bleiben unverarbeitet
  ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  InstallationDate: Installed on 2016-03-17 (35 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: 
Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1573662/+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 1618492] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con le dipendenze - trigger non elaborati

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con
  le dipendenze - trigger non elaborati

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  crash

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Aug 30 14:35:15 2016
  ErrorMessage: problemi con le dipendenze - trigger non elaborati
  InstallationDate: Installed on 2016-08-27 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con 
le dipendenze - trigger non elaborati
  UpgradeStatus: Upgraded to yakkety on 2016-08-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1618492/+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 1610029] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  when upgrading from 14.04 LTS to 16.04 LTS this error came up during
  the upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Aug  3 23:57:59 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1610029/+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 1618364] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com
  dependências - a deixar triggers por processar

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  After upgrade from xenial to yakkety

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Aug 30 09:34:31 2016
  ErrorMessage: problemas com dependências - a deixar triggers por processar
  InstallationDate: Installed on 2016-02-15 (196 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com 
dependências - a deixar triggers por processar
  UpgradeStatus: Upgraded to yakkety on 2016-08-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1618364/+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 1701447] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug is no longer a duplicate of bug 1632415
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  The bugs being reported were generated automatically (without any of
  my input) when I allowed the system to upgrade itself from 16.04 to
  16.10.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-58.63-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  Date: Thu Jun 29 21:58:13 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-11-27 (214 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2017-06-30 (0 days ago)
  mtime.conffile..etc.xdg.autostart.gsettings-data-convert.desktop: 
2017-01-03T13:15:58.771330

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1701447/+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 1698478] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  would load but with errors

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 16 17:22:13 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-06-16 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2017-06-16 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1698478/+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 1698600] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug is no longer a duplicate of bug 1632415
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  upgrading from 16.04 to 17.04  failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  Date: Sat Jun 17 18:19:27 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-09-13 (277 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2017-06-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1698600/+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 1651222] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug is no longer a duplicate of bug 1632415
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  upgrade done with fail to install package gconf2 3.2.6ubuntu7

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Dec 19 13:13:09 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-11-19 (29 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-12-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1651222/+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 1656553] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug is no longer a duplicate of bug 1645117
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  Error during partial update from 16.04 LTS to 16.10.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic i686
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  Date: Sat Jan 14 15:46:26 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-12-14 (31 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1656553/+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 1645117] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  --

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic i686
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  Date: Sun Nov 27 21:29:34 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-09-03 (85 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-11-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1645117/+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 1636962] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug is no longer a duplicate of bug 1632415
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 26 23:42:05 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-04-27 (181 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1636962/+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 1741658] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  System upgrage to Ubuntu 16.04 failed. During upgrade many packets were not 
installed:
  I wrote down the Dutch remarks "Kan gconf2 niet installeren" and many others. 
Translated:
  Failed to install during the systemupgrade:
  ==
  gconf2  (+ "gconf2 will possibly not work")
  gnupg-agent
  gnupg2
  libgdata22
  gvfs-backends
  adwaita-icon-theme-full
  libgail-3-0
  gstreamer1.0-plugins-bad
  gstreamer0.10-plugins-good
  gstreamer1.10-plugins-good
  libgssdp-1.0-3
  libupnp-1.0-4
  libupnp-igd-1.0-4
  libnice10
  gstreamer1.0-nice
  libfarstream-0.2-5
  libpurple0
  gnome-keyring
  libgpgme11
  libgmime-2.6-0
  libwebkitgtk-3.0-0
  geary
  gnome-icon-theme
  ===
  Hope the list is complete :-))
  Since then only logging-out is possible, but the menu items: "Close the 
system" ("Afsluiten" in Dutch)  nor "Restart" gave any effect. Caption of this 
menu is:

 Lubuntu
Session Zorin-OS-lite 16.04

  Best regards!
  Dirk De Backer
  mailto:debacker.d...@worldonline.be

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sat Jan  6 15:32:06 2018
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-12-19 (748 days ago)
  InstallationMedia: Zorin 9 trusty - Release i386 (20140811)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2018-01-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1741658/+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 1681137] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug is no longer a duplicate of bug 1632415
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  while upgrading from 16.04 to 16.10,
  it gave me this bug..

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sun Apr  9 01:01:29 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-08-01 (250 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2017-04-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1681137/+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 1632415] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  error after updating from 16.04.1 to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Tue Oct 11 22:08:46 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-25 (78 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1632415/+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 1634151] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade:
  vereistenproblemen - triggers blijven onbehandeld

Status in gconf package in Ubuntu:
  New

Bug description:
  Did an upgrade from Ubuntu 16.04 to 16.10, after rebooting the system
  the message occured

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Mon Oct 17 13:29:10 2016
  ErrorMessage: vereistenproblemen - triggers blijven onbehandeld
  InstallationDate: Installed on 2016-05-04 (166 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: 
vereistenproblemen - triggers blijven onbehandeld
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1634151/+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 1669632] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug is no longer a duplicate of bug 1632415
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Thu Mar  2 20:56:22 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-04-10 (326 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2017-03-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1669632/+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 1615116] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: beroendeproblem - lämnar utlösare obehandlade

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  beroendeproblem - lämnar utlösare obehandlade

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  Error received when upgrading from 16.04 to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Aug 19 18:49:10 2016
  ErrorMessage: beroendeproblem - lämnar utlösare obehandlade
  InstallationDate: Installed on 2016-02-08 (193 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu2
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: 
beroendeproblem - lämnar utlösare obehandlade
  UpgradeStatus: Upgraded to yakkety on 2016-08-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1615116/+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 1599846] Re: package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1568572 ***
https://bugs.launchpad.net/bugs/1568572

** This bug has been marked a duplicate of bug 1568572
   package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed

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

Title:
  package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to
  install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

Status in bamf package in Ubuntu:
  New

Bug description:
  Update failed while upgrading from xenial to yakkety.

  mahowi@T60:~$ lsb_release -rd
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10

  mahowi@T60:~$ apt-cache policy bamfdaemon
  bamfdaemon:
Installiert:   0.5.3~bzr0+16.10.20160705-0ubuntu1
Installationskandidat: 0.5.3~bzr0+16.10.20160705-0ubuntu1
Versionstabelle:
   *** 0.5.3~bzr0+16.10.20160705-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu yakkety/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic i686
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: i386
  Date: Thu Jul  7 13:39:38 2016
  ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  InstallationDate: Installed on 2016-07-06 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu1
   apt  1.3~exp1
  SourcePackage: bamf
  Title: package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to 
install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  UpgradeStatus: Upgraded to yakkety on 2016-07-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1599846/+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 1574123] Re: package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1568572 ***
https://bugs.launchpad.net/bugs/1568572

** This bug has been marked a duplicate of bug 1568572
   package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed

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

Title:
  package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in bamf package in Ubuntu:
  Confirmed

Bug description:
  during upgrade bamfdaemon was noch possible to install. Now it seems
  to be missiong? how to install it now? via packet-installer or
  terminal?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  Date: Sat Apr 23 20:17:09 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-08-21 (246 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: bamf
  Title: package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1574123/+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 1568572] Re: package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-25 Thread Vlad Orlov
Fixed in Xenial on 2016-07-18 by using interest-noawait in
debian/bamfdaemon.triggers file. More info at bug 1589097.

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

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

Title:
  package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in bamf package in Ubuntu:
  Fix Released

Bug description:
  I submitted this bug report because Ubuntu advised me to do so during
  an upgrade to Xenial from Wily.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1
  Uname: Linux 4.0.3-bisect-test-01-0559366f72c86288c8d3dc5cae91dfc2f6e26ad9 
x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sun Apr 10 19:23:53 2016
  DuplicateSignature: 
package:bamfdaemon:0.5.2~bzr0+15.10.20150627.1-0ubuntu1:dependency problems - 
leaving triggers unprocessed
  ErrorMessage: dependency problems - leaving triggers unprocessed
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10
  SourcePackage: bamf
  Title: package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-04-10 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1568572/+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 1574029] Re: Upgrade failed

2019-06-25 Thread Vlad Orlov
*** This bug is a duplicate of bug 1550292 ***
https://bugs.launchpad.net/bugs/1550292

** This bug has been marked a duplicate of bug 1550292
   package shared-mime-info 1.5-2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed

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

Title:
  Upgrade failed

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  At the end of the upgrade, a dialog box appeared "The upgrade has
  aborted. Your system could be in an unstable state. A recovery will
  run now (dpkg -configure - a). Nothing happened after closing the
  dialog box.

  
  After shutdown, boot up failed after grub tries to load something with this 
message "Starting up", then after 10 seconds this message "Gave up waiting 
for root device., common problems:.ALERT! UUID = 2476e..does not exist.

  The the boot process stopped at the initramfs prompt.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 17:34:29 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-11-12 (162 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1574029/+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 1834211] [NEW] [SRU] gconf FTBFS in Bionic

2019-06-25 Thread Vlad Orlov
Public bug reported:

[Impact]

Two issues make gconf FTBFS in Bionic:

- outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26
- missing dh-python in B-D

The debdiff attached below fixes these issues and makes gconf build
properly.

[Test Case]

Just install the needed build dependencies and try to build gconf. It
will fail with an error from gtk-doc.make. Second issue: if gtk-doc.make
is patched, the build will fail if dh-python isn't installed.

[Regression Potential]

None, you can't break it more than FTBFS :)

[Other Info]

Fixes are backported from Cosmic.

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


** Tags: bionic ftbfs

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

Title:
  [SRU] gconf FTBFS in Bionic

Status in gconf package in Ubuntu:
  New

Bug description:
  [Impact]

  Two issues make gconf FTBFS in Bionic:

  - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26
  - missing dh-python in B-D

  The debdiff attached below fixes these issues and makes gconf build
  properly.

  [Test Case]

  Just install the needed build dependencies and try to build gconf. It
  will fail with an error from gtk-doc.make. Second issue: if gtk-
  doc.make is patched, the build will fail if dh-python isn't installed.

  [Regression Potential]

  None, you can't break it more than FTBFS :)

  [Other Info]

  Fixes are backported from Cosmic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+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 1834211] Re: [SRU] gconf FTBFS in Bionic

2019-06-25 Thread Vlad Orlov
** Attachment added: "Debdiff with the fix for Bionic"
   
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+attachment/5273159/+files/gconf-debdiff-bionic

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

Title:
  [SRU] gconf FTBFS in Bionic

Status in gconf package in Ubuntu:
  New

Bug description:
  [Impact]

  Two issues make gconf FTBFS in Bionic:

  - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26
  - missing dh-python in B-D

  The debdiff attached below fixes these issues and makes gconf build
  properly.

  [Test Case]

  Just install the needed build dependencies and try to build gconf. It
  will fail with an error from gtk-doc.make. Second issue: if gtk-
  doc.make is patched, the build will fail if dh-python isn't installed.

  [Regression Potential]

  None, you can't break it more than FTBFS :)

  [Other Info]

  Fixes are backported from Cosmic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+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


  1   2   3   4   >