from:"Jani Uusitalo"

[Desktop-packages] [Bug 1940417]

2021-10-24 Thread Jani Uusitalo

I tested 95.0a1 (Nightly), and opening the hamburger menu (using the
steps I outlined above) works now.

Closing it is still partly broken though, as clicking on the menu button
doesn't close the menu; I think that is [bug
1694514](https://bugzilla.mozilla.org/show_bug.cgi?id=1694514).

For a workaround, clicking outside the menu (and the menu button) does
close the menu.

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

Title:
  On Wayland toolbar menus are sometimes invisible/flickering

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

Bug description:
  User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:91.0)
  Gecko/20100101 Firefox/91.0

  Steps to reproduce:

  Open Downloads panel, Library or Application menu form the Toolbar by
  clicking on the corresponding icons.

  Actual results:

  From version 90 I noticed that Library or other items in the Toolbar
  won't open when I click it. Instead it flickers a few times on mouse
  movement - it looks like it opens but it's not visible, it becomes
  visible a fraction of a second when I move the mouse otherwise it's
  completely transparent.

  Which Toolbar icon this affects seems random. I tried to fix it by
  resetting the Toolbar and disabling extensions which have icons in the
  Toolbar. Then I noticed that Library was working normal again but
  Downloads or Application Menu wouldn't open.

  When this happened with the Application Menu I could barely see the
  contents of the menu by moving the mouse which made the menu flicker.
  The cursor was able to select menu items in the menu but it was
  completely transparent.

  In the enclosed screenshot you can see I selected the Library menu
  item but it isn't opened.

  Expected results:

  The menus in the Toolbar should open like they used to.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeroen 3189 F pulseaudio
   /dev/snd/pcmC0D3p:   jeroen 3189 F...m pulseaudio
  BuildID: 20210804193234
  CasperMD5CheckResult: pass
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  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:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 21.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-05-22 (87 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 192.168.0.1 dev enp3s0 proto dhcp metric 20100 
   10.0.0.243 dev wgpia0 scope link 
   10.17.128.1 dev wgpia0 scope link 
   169.254.0.0/16 dev enp3s0 scope link metric 1000 
   192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.102 metric 
100
  Package: firefox 91.0+build2-0ubuntu0.21.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  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:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=91.0/20210804193234 (In use)
  RunningIncompatibleAddons: False
  Tags:  wayland-session hirsute
  Uname: Linux 5.11.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/29/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: VM60
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd04/29/2014:br4.6:svnASUSTeKComputerINC.:pnVM60:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnVM60:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: VM60
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.

To manage

[Desktop-packages] [Bug 1940417]

2021-09-26 Thread Jani Uusitalo

Also, I tested the 94.0a1 nightly now, and the issue is still present.

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

Title:
  On Wayland toolbar menus are sometimes invisible/flickering

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

Bug description:
  User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:91.0)
  Gecko/20100101 Firefox/91.0

  Steps to reproduce:

  Open Downloads panel, Library or Application menu form the Toolbar by
  clicking on the corresponding icons.

  Actual results:

  From version 90 I noticed that Library or other items in the Toolbar
  won't open when I click it. Instead it flickers a few times on mouse
  movement - it looks like it opens but it's not visible, it becomes
  visible a fraction of a second when I move the mouse otherwise it's
  completely transparent.

  Which Toolbar icon this affects seems random. I tried to fix it by
  resetting the Toolbar and disabling extensions which have icons in the
  Toolbar. Then I noticed that Library was working normal again but
  Downloads or Application Menu wouldn't open.

  When this happened with the Application Menu I could barely see the
  contents of the menu by moving the mouse which made the menu flicker.
  The cursor was able to select menu items in the menu but it was
  completely transparent.

  In the enclosed screenshot you can see I selected the Library menu
  item but it isn't opened.

  Expected results:

  The menus in the Toolbar should open like they used to.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeroen 3189 F pulseaudio
   /dev/snd/pcmC0D3p:   jeroen 3189 F...m pulseaudio
  BuildID: 20210804193234
  CasperMD5CheckResult: pass
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  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:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 21.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-05-22 (87 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 192.168.0.1 dev enp3s0 proto dhcp metric 20100 
   10.0.0.243 dev wgpia0 scope link 
   10.17.128.1 dev wgpia0 scope link 
   169.254.0.0/16 dev enp3s0 scope link metric 1000 
   192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.102 metric 
100
  Package: firefox 91.0+build2-0ubuntu0.21.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  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:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=91.0/20210804193234 (In use)
  RunningIncompatibleAddons: False
  Tags:  wayland-session hirsute
  Uname: Linux 5.11.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/29/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: VM60
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd04/29/2014:br4.6:svnASUSTeKComputerINC.:pnVM60:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnVM60:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: VM60
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.

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


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

[Desktop-packages] [Bug 1940417]

2021-09-26 Thread Jani Uusitalo

I ran mozregression like this (twice, to be sure):

MOZ_ENABLE_WAYLAND=1 mozregression --profile
/home/jani/.mozilla/firefox/fyaus28k.LP1940417 --bad 91 --good 89
--profile-persistence clone-first

Here's the result (it was the same for both bisects):

5:25.73 INFO: No more integration revisions, bisection finished.
5:25.73 INFO: Last good revision: 9f0fbb1431721c9eae68a3c94ae49a4d33fdb1f8
5:25.73 INFO: First bad revision: 7b82d177a6b979036f180329be6b029d690d9e0c
5:25.73 INFO: Pushlog:

https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=9f0fbb1431721c9eae68a3c94ae49a4d33fdb1f8=7b82d177a6b979036f180329be6b029d690d9e0c

According to [that
log](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=9f0fbb1431721c9eae68a3c94ae49a4d33fdb1f8=7b82d177a6b979036f180329be6b029d690d9e0c),
this
[changeset](https://hg.mozilla.org/integration/autoland/rev/7b82d177a6b979036f180329be6b029d690d9e0c)
was introduced to address
[#1661516](https://bugzilla.mozilla.org/show_bug.cgi?id=1661516).

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

Title:
  On Wayland toolbar menus are sometimes invisible/flickering

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

Bug description:
  User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:91.0)
  Gecko/20100101 Firefox/91.0

  Steps to reproduce:

  Open Downloads panel, Library or Application menu form the Toolbar by
  clicking on the corresponding icons.

  Actual results:

  From version 90 I noticed that Library or other items in the Toolbar
  won't open when I click it. Instead it flickers a few times on mouse
  movement - it looks like it opens but it's not visible, it becomes
  visible a fraction of a second when I move the mouse otherwise it's
  completely transparent.

  Which Toolbar icon this affects seems random. I tried to fix it by
  resetting the Toolbar and disabling extensions which have icons in the
  Toolbar. Then I noticed that Library was working normal again but
  Downloads or Application Menu wouldn't open.

  When this happened with the Application Menu I could barely see the
  contents of the menu by moving the mouse which made the menu flicker.
  The cursor was able to select menu items in the menu but it was
  completely transparent.

  In the enclosed screenshot you can see I selected the Library menu
  item but it isn't opened.

  Expected results:

  The menus in the Toolbar should open like they used to.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeroen 3189 F pulseaudio
   /dev/snd/pcmC0D3p:   jeroen 3189 F...m pulseaudio
  BuildID: 20210804193234
  CasperMD5CheckResult: pass
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  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:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 21.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-05-22 (87 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 192.168.0.1 dev enp3s0 proto dhcp metric 20100 
   10.0.0.243 dev wgpia0 scope link 
   10.17.128.1 dev wgpia0 scope link 
   169.254.0.0/16 dev enp3s0 scope link metric 1000 
   192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.102 metric 
100
  Package: firefox 91.0+build2-0ubuntu0.21.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  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:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=91.0/20210804193234 (In use)
  RunningIncompatibleAddons: False
  Tags:  wayland-session hirsute
  Uname: Linux 5.11.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/29/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602

[Desktop-packages] [Bug 1940417]

2021-09-13 Thread Jani Uusitalo

I can't speak for Jeroen, but I played around with the upstream builds
(both 92 and 91) and my faulty profile a bit and managed to isolate the
trigger combination for this: `MOZ_ENABLE_WAYLAND=1` and setting
`layout.css.devPixelsPerPx` to my preferred value of `1.2`; either
resetting `layout.css.devPixelsPerPx` to its default (`-1.0`), or
running Firefox without `MOZ_ENABLE_WAYLAND=1` will make the toolbar
items work again. [Here's the graphics portion of my
`about:support`](https://pastebin.mozilla.org/OdgM9Oox).

**So my steps to reproduce this are:**
1. start Firefox with `MOZ_ENABLE_WAYLAND=1`
2. set `layout.css.devPixelsPerPx` to `1.2`
3. click on the hamburger menu button

**What I expect to happen:**
For the hamburger menu content to show.

**What happens instead:**
The hamburger menu content flickers or doesn't show at all.

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

Title:
  On Wayland toolbar menus are sometimes invisible/flickering

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

Bug description:
  User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:91.0)
  Gecko/20100101 Firefox/91.0

  Steps to reproduce:

  Open Downloads panel, Library or Application menu form the Toolbar by
  clicking on the corresponding icons.

  Actual results:

  From version 90 I noticed that Library or other items in the Toolbar
  won't open when I click it. Instead it flickers a few times on mouse
  movement - it looks like it opens but it's not visible, it becomes
  visible a fraction of a second when I move the mouse otherwise it's
  completely transparent.

  Which Toolbar icon this affects seems random. I tried to fix it by
  resetting the Toolbar and disabling extensions which have icons in the
  Toolbar. Then I noticed that Library was working normal again but
  Downloads or Application Menu wouldn't open.

  When this happened with the Application Menu I could barely see the
  contents of the menu by moving the mouse which made the menu flicker.
  The cursor was able to select menu items in the menu but it was
  completely transparent.

  In the enclosed screenshot you can see I selected the Library menu
  item but it isn't opened.

  Expected results:

  The menus in the Toolbar should open like they used to.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeroen 3189 F pulseaudio
   /dev/snd/pcmC0D3p:   jeroen 3189 F...m pulseaudio
  BuildID: 20210804193234
  CasperMD5CheckResult: pass
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  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:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 21.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-05-22 (87 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 192.168.0.1 dev enp3s0 proto dhcp metric 20100 
   10.0.0.243 dev wgpia0 scope link 
   10.17.128.1 dev wgpia0 scope link 
   169.254.0.0/16 dev enp3s0 scope link metric 1000 
   192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.102 metric 
100
  Package: firefox 91.0+build2-0ubuntu0.21.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  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:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=91.0/20210804193234 (In use)
  RunningIncompatibleAddons: False
  Tags:  wayland-session hirsute
  Uname: Linux 5.11.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/29/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: VM60
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3

[Desktop-packages] [Bug 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze

2021-06-09 Thread Jani Uusitalo

There's no gnome-shell-extension-dashtodock package for focal [1], but I
did try with Dash to Dock from extensions.gnome.org, and could not
reproduce the issue with it. I tried with the default settings, as well
as after recreating the look & feel of Ubuntu Dock as much as possible.

Dash to Dock has customizable action for the scroll (to either switch
workspaces or windows, or to do nothing), and all of those also worked
just as expected.

I also noticed that using the two finger scroll function of the touchpad
on my laptop does *not* trigger this (whereas using the mouse on it
does).


* [1] 
https://packages.ubuntu.com/search?keywords=gnome-shell-extension-dashtodock

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

Title:
  Horizontal scroll over dock causes it to crash and disappear, and a
  temporary GUI freeze

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  # Steps to reproduce
  0. have a mouse with horizontal scrolling functionality (mine is a Microsoft 
Comfort Mouse 4500 with a tilting action for horizontal scroll)
  1. move mouse pointer over the dock
  2. use the mouse scroller to scroll horizontally

  # What I expect to happen
  Nothing

  # What happens
  Mouse pointer and everything on screen freezes. After a few seconds it 
unfreezes, but all the icons from the dock are missing. I have to log out and 
back in to restore the dock.

  # Other info
  Slightly similar to LP #1875106, but I'm not using imwheel.

  I am using Wayland.

  Syslog seems to always point to this one function: "The offending
  callback was get_preferred_height(), a vfunc". I'll attach the
  relevant part from one crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 20:35:37 2021
  InstallationDate: Installed on 2020-11-30 (182 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+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 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze

2021-06-08 Thread Jani Uusitalo

Do you want another log for that? Because (as I already mentioned
above), this also reproduces when using a newly-created user, so that
means no unsupported extensions.

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

Title:
Horizontal scroll over dock causes it to crash and disappear, and a
temporary GUI freeze

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Incomplete

Bug description:
# Steps to reproduce
0. have a mouse with horizontal scrolling functionality (mine is a Microsoft
Comfort Mouse 4500 with a tilting action for horizontal scroll)
1. move mouse pointer over the dock
2. use the mouse scroller to scroll horizontally

# What I expect to happen
Nothing

# What happens
Mouse pointer and everything on screen freezes. After a few seconds it
unfreezes, but all the icons from the dock are missing. I have to log out and
back in to restore the dock.

# Other info
Slightly similar to LP #1875106, but I'm not using imwheel.

I am using Wayland.

Syslog seems to always point to this one function: "The offending
callback was get_preferred_height(), a vfunc". I'll attach the
relevant part from one crash.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 31 20:35:37 2021
InstallationDate: Installed on 2020-11-30 (182 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+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 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze

2021-06-04 Thread Jani Uusitalo

I can reproduce the crash at will with the steps I listed above, so I
don't have to wait for it to happen. It also doesn't forcibly log me
out, so I can enter those commands by just having a terminal window
present when I trigger the issue. But I logged out here (after
triggering) anyway since you instructed me to log in, in case it
matters.

Also, there's lots of noise in these from Boinc, thanks to #1876313.

** Attachment added: "journal.txt"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+attachment/5502425/+files/journal.txt

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

Title:
Horizontal scroll over dock causes it to crash and disappear, and a
temporary GUI freeze

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Incomplete

# What I expect to happen
Nothing

# What happens
Mouse pointer and everything on screen freezes. After a few seconds it
unfreezes, but all the icons from the dock are missing. I have to log out and
back in to restore the dock.

# Other info
Slightly similar to LP #1875106, but I'm not using imwheel.

I am using Wayland.

Syslog seems to always point to this one function: "The offending
callback was get_preferred_height(), a vfunc". I'll attach the
relevant part from one crash.

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

[Desktop-packages] [Bug 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze

2021-06-04 Thread Jani Uusitalo

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+attachment/5502426/+files/prevboot.txt

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

Title:
  Horizontal scroll over dock causes it to crash and disappear, and a
  temporary GUI freeze

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  # Steps to reproduce
  0. have a mouse with horizontal scrolling functionality (mine is a Microsoft 
Comfort Mouse 4500 with a tilting action for horizontal scroll)
  1. move mouse pointer over the dock
  2. use the mouse scroller to scroll horizontally

  # What I expect to happen
  Nothing

  # What happens
  Mouse pointer and everything on screen freezes. After a few seconds it 
unfreezes, but all the icons from the dock are missing. I have to log out and 
back in to restore the dock.

  # Other info
  Slightly similar to LP #1875106, but I'm not using imwheel.

  I am using Wayland.

  Syslog seems to always point to this one function: "The offending
  callback was get_preferred_height(), a vfunc". I'll attach the
  relevant part from one crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 20:35:37 2021
  InstallationDate: Installed on 2020-11-30 (182 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+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 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze

2021-06-02 Thread Jani Uusitalo

1. There's nothing in /var/crash
2. There are no reports on the page for this computer.
3. Done, still nothing in /var/crash.

I don't know if this means it's not a true crash, although visually all
the indications are there.

I also verified that this reproduces when using a newly-created user
(with the only change from defaults for it being switching to Wayland),
and also on another computer (also running 20.04). I am limited to using
the one mouse that I have, so that all testing so far has been with the
same mouse.

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

Title:
Horizontal scroll over dock causes it to crash and disappear, and a
temporary GUI freeze

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Incomplete

# What I expect to happen
Nothing

# What happens
Mouse pointer and everything on screen freezes. After a few seconds it
unfreezes, but all the icons from the dock are missing. I have to log out and
back in to restore the dock.

# Other info
Slightly similar to LP #1875106, but I'm not using imwheel.

I am using Wayland.

Syslog seems to always point to this one function: "The offending
callback was get_preferred_height(), a vfunc". I'll attach the
relevant part from one crash.

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

[Desktop-packages] [Bug 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze

2021-05-31 Thread Jani Uusitalo

** Attachment added: "syslog Stack trace"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+attachment/5501476/+files/syslog

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

Title:
  Horizontal scroll over dock causes it to crash and disappear, and a
  temporary GUI freeze

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  # Steps to reproduce
  0. have a mouse with horizontal scrolling functionality (mine is a Microsoft 
Comfort Mouse 4500 with a tilting action for horizontal scroll)
  1. move mouse pointer over the dock
  2. use the mouse scroller to scroll horizontally

  # What I expect to happen
  Nothing

  # What happens
  Mouse pointer and everything on screen freezes. After a few seconds it 
unfreezes, but all the icons from the dock are missing. I have to log out and 
back in to restore the dock.

  # Other info
  Slightly similar to LP #1875106, but I'm not using imwheel.

  I am using Wayland.

  Syslog seems to always point to this one function: "The offending
  callback was get_preferred_height(), a vfunc". I'll attach the
  relevant part from one crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 20:35:37 2021
  InstallationDate: Installed on 2020-11-30 (182 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+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 1930304] [NEW] Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze

2021-05-31 Thread Jani Uusitalo

Public bug reported:

# Steps to reproduce
0. have a mouse with horizontal scrolling functionality (mine is a Microsoft 
Comfort Mouse 4500 with a tilting action for horizontal scroll)
1. move mouse pointer over the dock
2. use the mouse scroller to scroll horizontally

# What I expect to happen
Nothing

# What happens
Mouse pointer and everything on screen freezes. After a few seconds it 
unfreezes, but all the icons from the dock are missing. I have to log out and 
back in to restore the dock.

# Other info
Slightly similar to LP #1875106, but I'm not using imwheel.

I am using Wayland.

Syslog seems to always point to this one function: "The offending
callback was get_preferred_height(), a vfunc". I'll attach the relevant
part from one crash.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 31 20:35:37 2021
InstallationDate: Installed on 2020-11-30 (182 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

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


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

** Description changed:

  # Steps to reproduce
  0. have a mouse with horizontal scrolling functionality (mine is a Microsoft 
Comfort Mouse 4500 with a tilting action for horizontal scroll)
  1. move mouse pointer over the dock
  2. use the mouse scroller to scroll horizontally
  
  # What I expect to happen
  Nothing
  
  # What happens
  Mouse pointer and everything on screen freezes. After a few seconds it 
unfreezes, but all the icons from the dock are missing. I have to log out and 
back in to restore the dock.
  
  # Other info
- Slightly similar to #1875106, but I'm not using imwheel.
+ Slightly similar to LP #1875106, but I'm not using imwheel.
  
  I am using Wayland.
  
  Syslog seems to always point to this one function: "The offending
  callback was get_preferred_height(), a vfunc". I'll attach the relevant
  part from one crash.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 20:35:37 2021
  InstallationDate: Installed on 2020-11-30 (182 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

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

Title:
  Horizontal scroll over dock causes it to crash and disappear, and a
  temporary GUI freeze

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  # Steps to reproduce
  0. have a mouse with horizontal scrolling functionality (mine is a Microsoft 
Comfort Mouse 4500 with a tilting action for horizontal scroll)
  1. move mouse pointer over the dock
  2. use the mouse scroller to scroll horizontally

  # What I expect to happen
  Nothing

  # What happens
  Mouse pointer and everything on screen freezes. After a few seconds it 
unfreezes, but all the icons from the dock are missing. I have to log out and 
back in to restore the dock.

  # Other info
  Slightly similar to LP #1875106, but I'm not using imwheel.

  I am using Wayland.

  Syslog seems to always point to this one function: "The offending
  callback was get_preferred_height(), a vfunc". I'll attach the
  relevant part from one crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 20:35:37 2021

[Desktop-packages] [Bug 1874808]

2021-05-02 Thread Jani Uusitalo

### Steps to reproduce

1. Open about:config
2. Search for autoplay in the settings
3. Set `media.autoplay.default` to `1` ("Block Audio", which is the default)
4. Set `media.autoplay.blocking_policy` to `2`
5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033
6. Try to unmute the video (either by clicking Twitch player's speaker control 
button, or by dragging the accompanying volume slider)

### What I expect to happen
For the audio to be unmuted.

### What happens instead
The audio remains muted, and the volume control/indicator remains in the muted 
position.

---

I'm unmotivated to report this to Twitch, as I'm unsure about the
precise meaning of `media.autoplay.blocking_policy`, and I currently
don't use the non-working value for it myself. Feel free to
downprioritize this as you see fit, unless the original reporter is
still affected. Here's [my downstream report over at
Launchpad](https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1874808)
though, just for reference. (I'll update it too.)

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

Title:
  Twitch video can not be unmuted when media.autoplay.blocking_policy=2,
  media.autoplay.default=1

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

Bug description:
  With `media.autoplay.blocking_policy` set to 2 and
  `media.autoplay.default` set to 1 (block audio, which is the default),
  a Twitch video can not be unmuted.

  == Steps to reproduce ==

  1. Open about:config
  2. Search for autoplay in the settings
  3. Set media.autoplay.default to 1 ("Block Audio", which is the default)
  4. Set media.autoplay.blocking_policy to 2
  5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033
  6. Try to unmute the video (either by clicking Twitch player's speaker 
control button, or by dragging the accompanying volume slider)

  == What I expect to happen ==
  For the audio to be unmuted.

  == What happens instead ==
  The audio remains muted, and the volume control/indicator remains in the 
muted position.

  == Other info ==
  This is present in Firefox 88. I tried to update the versions info below 
using apport-collect, but it failed.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 16:33:46 2020
  InstallationDate: Installed on 2016-10-13 (1289 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BuildID: 20210415204500
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-30 (148 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: firefox 88.0+build2-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Tags:  focal wayland-session
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare ssh sudo vboxusers
  _MarkForUpload: True
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1874808/+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 1874808]

2021-05-02 Thread Jani Uusitalo

Hi Alex!

It does not appear to have been fully fixed by Firefox 88 for me at
least, although the conditions have changed slightly, and the remaining
broken behavior is now slightly different too.

First, to update my note above: `media.autoplay.enabled.user-gestures-
needed` has been superseded by `media.autoplay.blocking_policy`, and
setting the latter to `2` is now required to trigger the issue (as it
manifests presently); with the setting at either `0` or `1` I haven't
been able to reproduce any variation of the issue.

Now, the video doesn't get paused anymore, but the unmuting also does
not work: clicking the muted indicator just always resets it back to
muted, instead of actually unmuting.

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

Title:
  Twitch video can not be unmuted when media.autoplay.blocking_policy=2,
  media.autoplay.default=1

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

Bug description:
  With `media.autoplay.blocking_policy` set to 2 and
  `media.autoplay.default` set to 1 (block audio, which is the default),
  a Twitch video can not be unmuted.

  == Steps to reproduce ==

  1. Open about:config
  2. Search for autoplay in the settings
  3. Set media.autoplay.default to 1 ("Block Audio", which is the default)
  4. Set media.autoplay.blocking_policy to 2
  5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033
  6. Try to unmute the video (either by clicking Twitch player's speaker 
control button, or by dragging the accompanying volume slider)

  == What I expect to happen ==
  For the audio to be unmuted.

  == What happens instead ==
  The audio remains muted, and the volume control/indicator remains in the 
muted position.

  == Other info ==
  This is present in Firefox 88. I tried to update the versions info below 
using apport-collect, but it failed.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 16:33:46 2020
  InstallationDate: Installed on 2016-10-13 (1289 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BuildID: 20210415204500
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-30 (148 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: firefox 88.0+build2-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Tags:  focal wayland-session
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare ssh sudo vboxusers
  _MarkForUpload: True
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1874808/+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 1874808] ProcEnviron.txt

2021-04-28 Thread Jani Uusitalo

apport information

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

** Attachment removed: "HookError_source_firefox.txt"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1874808/+attachment/5493042/+files/HookError_source_firefox.txt

** Description changed:

  With `media.autoplay.blocking_policy` set to 2 and
  `media.autoplay.default` set to 1 (block audio, which is the default), a
  Twitch video can not be unmuted.
  
  == Steps to reproduce ==
  
  1. Open about:config
  2. Search for autoplay in the settings
  3. Set media.autoplay.default to 1 ("Block Audio", which is the default)
  4. Set media.autoplay.blocking_policy to 2
  5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033
  6. Try to unmute the video (either by clicking Twitch player's speaker 
control button, or by dragging the accompanying volume slider)
  
  == What I expect to happen ==
  For the audio to be unmuted.
  
  == What happens instead ==
  The audio remains muted, and the volume control/indicator remains in the 
muted position.
+ 
+ == Other info ==
+ This is present in Firefox 88. I tried to update the versions info below 
using apport-collect, but it failed.
  
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 16:33:46 2020
  InstallationDate: Installed on 2016-10-13 (1289 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BuildID: 20210415204500
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-30 (148 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: firefox 88.0+build2-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Tags:  focal wayland-session
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare ssh sudo vboxusers
  _MarkForUpload: True
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

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

Title:
  Twitch video can not be unmuted when media.autoplay.blocking_policy=2,
  media.autoplay.default=1

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

Bug description:
  With `media.autoplay.blocking_policy` set to 2 and
  `media.autoplay.default` set to 1 (block audio, which is the default),
  a Twitch video can not be unmuted.

  == Steps to reproduce ==

  1. Open about:config
  2. Search for autoplay in the settings
  3. Set media.autoplay.default to 1 ("Block Audio", which is the default)
  4. Set media.autoplay.blocking_policy to 2
  5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033
  6. Try to unmute the video (either by clicking Twitch player's speaker 
control button, or by dragging the accompanying volume slider)

  == What I expect to happen ==
  For the audio to be unmuted.

  == What happens instead ==
  The audio remains muted, and the volume control/indicator remains in the 
muted position.

  == Other info ==
  This is present in Firefox 88. I tried to update the versions info below 
using apport-collect, but it failed.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 16:33:46 2020
  InstallationDate: Installed on 2016-10-13 (1289 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No

[Desktop-packages] [Bug 1874808] HookError_source_firefox.txt

2021-04-28 Thread Jani Uusitalo

apport information

** Attachment added: "HookError_source_firefox.txt"
   
https://bugs.launchpad.net/bugs/1874808/+attachment/5493042/+files/HookError_source_firefox.txt

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

Title:
  Twitch video can not be unmuted when media.autoplay.blocking_policy=2,
  media.autoplay.default=1

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

Bug description:
  With `media.autoplay.blocking_policy` set to 2 and
  `media.autoplay.default` set to 1 (block audio, which is the default),
  a Twitch video can not be unmuted.

  == Steps to reproduce ==

  1. Open about:config
  2. Search for autoplay in the settings
  3. Set media.autoplay.default to 1 ("Block Audio", which is the default)
  4. Set media.autoplay.blocking_policy to 2
  5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033
  6. Try to unmute the video (either by clicking Twitch player's speaker 
control button, or by dragging the accompanying volume slider)

  == What I expect to happen ==
  For the audio to be unmuted.

  == What happens instead ==
  The audio remains muted, and the volume control/indicator remains in the 
muted position.

  == Other info ==
  This is present in Firefox 88. I tried to update the versions info below 
using apport-collect, but it failed.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 16:33:46 2020
  InstallationDate: Installed on 2016-10-13 (1289 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BuildID: 20210415204500
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-30 (148 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: firefox 88.0+build2-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Tags:  focal wayland-session
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare ssh sudo vboxusers
  _MarkForUpload: True
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1874808/+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 1874808] ProcCpuinfoMinimal.txt

2021-04-28 Thread Jani Uusitalo

apport information

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

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

Title:
  Twitch video can not be unmuted when media.autoplay.blocking_policy=2,
  media.autoplay.default=1

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

Bug description:
  With `media.autoplay.blocking_policy` set to 2 and
  `media.autoplay.default` set to 1 (block audio, which is the default),
  a Twitch video can not be unmuted.

  == Steps to reproduce ==

  1. Open about:config
  2. Search for autoplay in the settings
  3. Set media.autoplay.default to 1 ("Block Audio", which is the default)
  4. Set media.autoplay.blocking_policy to 2
  5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033
  6. Try to unmute the video (either by clicking Twitch player's speaker 
control button, or by dragging the accompanying volume slider)

  == What I expect to happen ==
  For the audio to be unmuted.

  == What happens instead ==
  The audio remains muted, and the volume control/indicator remains in the 
muted position.

  == Other info ==
  This is present in Firefox 88. I tried to update the versions info below 
using apport-collect, but it failed.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 16:33:46 2020
  InstallationDate: Installed on 2016-10-13 (1289 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BuildID: 20210415204500
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-30 (148 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: firefox 88.0+build2-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Tags:  focal wayland-session
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare ssh sudo vboxusers
  _MarkForUpload: True
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1874808/+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 1874808] Re: Unmuting Twitch video pauses playback, when media.autoplay.enabled.user-gestures-needed=false, media.autoplay.default=1

2021-04-28 Thread Jani Uusitalo

apport information

** Description changed:

- With `media.autoplay.enabled.user-gestures-needed` set to false and
- `media.autoplay.default` set to 1 (block audio), which is the default
- (and other autoplay-related settings in their defaults as well), a
- Twitch video can only be either paused or playing muted; unmuting the
- video pauses it and vice versa.
+ With `media.autoplay.blocking_policy` set to 2 and
+ `media.autoplay.default` set to 1 (block audio, which is the default), a
+ Twitch video can not be unmuted.
  
  == Steps to reproduce ==
+ 
  1. Open about:config
  2. Search for autoplay in the settings
- 3. Set media.autoplay.enabled.user-gestures-needed to false
- 4. Set media.autoplay.default to 1
+ 3. Set media.autoplay.default to 1 ("Block Audio", which is the default)
+ 4. Set media.autoplay.blocking_policy to 2
  5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033
- 6. Try to unmute the video
- 
- == What happens ==
- The video is unmuted, but also paused
+ 6. Try to unmute the video (either by clicking Twitch player's speaker 
control button, or by dragging the accompanying volume slider)
  
  == What I expect to happen ==
- For the video to continue playing, unmuted
+ For the audio to be unmuted.
+ 
+ == What happens instead ==
+ The audio remains muted, and the volume control/indicator remains in the 
muted position.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 16:33:46 2020
  InstallationDate: Installed on 2016-10-13 (1289 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fi_FI.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fi_FI.UTF-8
+  SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- Unmuting Twitch video pauses playback, when 
media.autoplay.enabled.user-gestures-needed=false, media.autoplay.default=1 
+ Twitch video can not be unmuted when media.autoplay.blocking_policy=2, 
media.autoplay.default=1

** Tags added: apport-collected

** Description changed:

  With `media.autoplay.blocking_policy` set to 2 and
  `media.autoplay.default` set to 1 (block audio, which is the default), a
  Twitch video can not be unmuted.
  
  == Steps to reproduce ==
  
  1. Open about:config
  2. Search for autoplay in the settings
  3. Set media.autoplay.default to 1 ("Block Audio", which is the default)
  4. Set media.autoplay.blocking_policy to 2
  5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033
  6. Try to unmute the video (either by clicking Twitch player's speaker 
control button, or by dragging the accompanying volume slider)
  
  == What I expect to happen ==
  For the audio to be unmuted.
  
  == What happens instead ==
  The audio remains muted, and the volume control/indicator remains in the 
muted position.
  
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 16:33:46 2020
  InstallationDate: Installed on 2016-10-13 (1289 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.16
+ Architecture: amd64
+ BuildID: 20210415204500
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-11-30 (148 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: firefox 88.0+build2-0ubuntu0.20.04.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
+ Tags:  focal wayland-session
+ Uname: Linux 5.8.0-50-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare ssh sudo vboxusers
+ _MarkForUpload: True
+ modified.conffile..etc.default.apport: [modified]

[Desktop-packages] [Bug 1889784] Re: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland)

2020-10-10 Thread Jani Uusitalo

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

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

Title:
  Hardware-accelerated video decoding (VA-API) broken in Firefox 79
  (Wayland)

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  After updating Firefox from 78 to 79, hardware-accelerated video
  decoding no longer works properly in Wayland: streaming video gets cut
  off with an error message from the service.

  == Steps to reproduce ==
  1. Follow the steps in [1] to enable VA-API.
  2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), 
press play

  == What I expect to happen ==
  For the video be played without issues (as it did with Firefox 78).

  == What happens ==
  After playing for a while (anything from just a few seconds to a couple of 
minutes), the video stops and is replaced by a service-specific error message, 
such as error #3000 (in case of Twitch). Even when playing, the video also 
flickers green. After reloading the tab, the video again plays for a few 
seconds before the error message reappears.

  == Other info ==
  A fix is apparently already in the works upstream [2].

  
  * [1] 
https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/
  * [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 79.0+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BuildID: 20200720193547
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 31 17:07:50 2020
  InstallationDate: Installed on 2016-10-13 (1387 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1889784/+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 1889784] [NEW] Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland)

2020-07-31 Thread Jani Uusitalo

Public bug reported:

After updating Firefox from 78 to 79, hardware-accelerated video
decoding no longer works properly in Wayland: streaming video gets cut
off with an error message from the service.

== Steps to reproduce ==
1. Follow the steps in [1] to enable VA-API.
2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), 
press play

== What I expect to happen ==
For the video be played without issues (as it did with Firefox 78).

== What happens ==
After playing for a while (anything from just a few seconds to a couple of 
minutes), the video stops and is replaced by a service-specific error message, 
such as error #3000 (in case of Twitch). Even when playing, the video also 
flickers green. After reloading the tab, the video again plays for a few 
seconds before the error message reappears.

== Other info ==
A fix is apparently already in the works upstream [2].


* [1] 
https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/
* [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 79.0+build1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BuildID: 20200720193547
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 31 17:07:50 2020
InstallationDate: Installed on 2016-10-13 (1387 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877

** Affects: firefox
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug focal wayland-session

** Bug watch added: Mozilla Bugzilla #1645671
   https://bugzilla.mozilla.org/show_bug.cgi?id=1645671

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1645671
   Importance: Unknown
   Status: Unknown

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

Title:
  Hardware-accelerated video decoding (VA-API) broken in Firefox 79
  (Wayland)

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

Bug description:
  After updating Firefox from 78 to 79, hardware-accelerated video
  decoding no longer works properly in Wayland: streaming video gets cut
  off with an error message from the service.

  == Steps to reproduce ==
  1. Follow the steps in [1] to enable VA-API.
  2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), 
press play

  == What I expect to happen ==
  For the video be played without issues (as it did with Firefox 78).

  == What happens ==
  After playing for a while (anything from just a few seconds to a couple of 
minutes), the video stops and is replaced by a service-specific error message, 
such as error #3000 (in case of Twitch). Even when playing, the video also 
flickers green. After reloading the tab, the video again plays for a few 
seconds before the error message reappears.

  == Other info ==
  A fix is apparently already in the works upstream [2].

  
  * [1] 
https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/
  * [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 79.0+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BuildID: 20200720193547
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 31 17:07:50 2020
  InstallationDate: Installed on 2016-10-13 (1387 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877

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

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

[Desktop-packages] [Bug 1871868] Re: Shell dialog text is truncated and ellipsized

2020-07-28 Thread Jani Uusitalo

I can confirm that 3.36.4-1ubuntu1~20.04.1 from -proposed fixed the
issue (in Boxes) for me, i.e. the dialog text is now wrapped and hence
entirely legible.

** Attachment added: "Fully visible text after installing package from 
-proposed"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871868/+attachment/5396556/+files/20200728_163529.jpg

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  Shell dialog text is truncated and ellipsized

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Shell modal dialogs contain text that may be truncated when using
  certain locales

  [ Test case ]

  - Start a virtual machine with GNOME Boxes
  - The keyboard prompt should be all visible

  [ Regression potential ]

  Text isn't properly rendered or the dialog is not all visible in the
  display

  

  When trying to start a virtual machine with Gnome Boxes, I get a
  prompt about keyboard shortcuts. The prompt text is localized, but
  translated back to English (I think, based on [1]) it says:

  Boxes wants to inhibit shortcuts

  You can restore shortcuts by pressing Super+Escape.

  In my locale (Finnish), it says

  Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa.

  Voit palauttaa pikanäppäinten toiminnan painamalla Super...

  (sic; see attached photo)

  So the actual key combination is truncated, defeating the point of
  that part of the text.

  This isn't a localization error (AFAICT; see [2]). It's caused by the
  text being forced to fit on a single line of an arbitrarily fixed
  width, instead of wrapping to span as many lines as needed.

  (I'm reporting this against gnome-shell as opposed gnome-boxes based
  on [3]. Feel free to reassign as necessary.)

  * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28
  * [2] 
https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10show=allsearch=pikan%C3%A4pp%C3%A4inten
  * [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 18:29:14 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-13 (1274 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1SourcePackage: 
gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1871868/+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 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)

2020-05-15 Thread Jani Uusitalo

After doing manual dconf cleanup, I've been unable to reproduce the
issue. That's since posting the previous comment, so a few days now. So
I think I'll hold off on reporting this upstream for the time being, but
I'll go ahead and do that if the problem still manifests itself.

Thanks again, Daniel.

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

Title:
  WL: compositor bug: The compositor tried to use an object from one
  client in a 'wl_pointer.enter' for a different client (resulting in
  Gnome terminal crashing)

Status in gnome-terminal package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to 20.04 and switching to Wayland, Gnome terminal
  occasionally crashes. I interpret the corresponding logs to mean that
  it's actually Wayland that fails to do something in the background,
  which then takes down Gnome terminal:

  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The 
compositor tried to use an object from one client in a 'wl_pointer.enter' for a 
different client.
  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client 
communication (pid 11639)
  touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events 
from display: Katkennut putki
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Main process exited, code=exited, status=1/FAILURE
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Failed with result 'exit-code'.

  I have yet to nail down the precise circumstances, as this has (so
  far) been somewhat rare, having occurred perhaps once or twice a week.

  Since the log mentions pointer, I should perhaps mention that I've set
  `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome
  terminal also exhibits other misbehaviour wrt. to this, occasionally
  refusing to get focus, or alternatively losing the focus, despite
  mouse cursor being over the terminal window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.8-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
  Uname: Linux 5.4.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 15:22:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed
   xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2016-10-13 (1302 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic 
root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name:

[Desktop-packages] [Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)

2020-05-12 Thread Jani Uusitalo

I removed all but Desktop Icons, Ubuntu AppIndicators and Ubuntu Dock,
rebooted and then reproduced the issue. Luckily I've found one way to
reproduce this, albeit somewhat convoluted and still a bit unreliable,
involving Synaptic and window tiling. And as it doesn't seem to trigger
the issue when using another account, I'm now working through settings
differences between the two in hopes of finding something crucial.

While doing so, I did discover that dconf-editor is similarly affected:

touko 12 16:09:32 saegusa gnome-shell[8208]: WL: compositor bug: The 
compositor tried to use an object from one client in a 'wl_pointer.enter' for a 
different client.
touko 12 16:09:32 saegusa gnome-shell[8208]: WL: error in client 
communication (pid 12364)
touko 12 16:09:32 saegusa dconf-editor[12364]: Error reading events from 
display: Katkennut putki
touko 12 16:09:32 saegusa boinc[2098]: No protocol specified
touko 12 16:09:32 saegusa boinc[2098]: No protocol specified
touko 12 16:09:33 saegusa boinc[2098]: No protocol specified
touko 12 16:09:33 saegusa boinc[2098]: No protocol specified
touko 12 16:09:34 saegusa gnome-shell[8208]: WL: compositor bug: The 
compositor tried to use an object from one client in a 'wl_pointer.enter' for a 
different client.
touko 12 16:09:34 saegusa boinc[2098]: No protocol specified
touko 12 16:09:34 saegusa boinc[2098]: No protocol specified
touko 12 16:09:34 saegusa gnome-shell[8208]: WL: error in client 
communication (pid 12796)
touko 12 16:09:34 saegusa gnome-terminal-[12796]: Error reading events from 
display: Katkennut putki
touko 12 16:09:34 saegusa systemd[3569]: gnome-terminal-server.service: 
Main process exited, code=exited, status=1/FAILURE
touko 12 16:09:34 saegusa systemd[3569]: gnome-terminal-server.service: 
Failed with result 'exit-code'.
touko 12 16:09:34 saegusa systemd[3569]: 
vte-spawn-da1941e8-60e5-48e5-868b-7348dd1158c7.scope: Succeeded.
touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to 
desktop: this.layout.get_child_at(...) is null
touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to 
desktop: this.layout.get_child_at(...) is null
touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to 
desktop: this.layout.get_child_at(...) is null
touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to 
desktop: this.layout.get_child_at(...) is null

Looks like dconf-editor did not exit with FAILURE, but the dconf-editor
window did disappear just as Gnome terminal's did.

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

Title:
  WL: compositor bug: The compositor tried to use an object from one
  client in a 'wl_pointer.enter' for a different client (resulting in
  Gnome terminal crashing)

Status in gnome-terminal package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to 20.04 and switching to Wayland, Gnome terminal
  occasionally crashes. I interpret the corresponding logs to mean that
  it's actually Wayland that fails to do something in the background,
  which then takes down Gnome terminal:

  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The 
compositor tried to use an object from one client in a 'wl_pointer.enter' for a 
different client.
  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client 
communication (pid 11639)
  touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events 
from display: Katkennut putki
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Main process exited, code=exited, status=1/FAILURE
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Failed with result 'exit-code'.

  I have yet to nail down the precise circumstances, as this has (so
  far) been somewhat rare, having occurred perhaps once or twice a week.

  Since the log mentions pointer, I should perhaps mention that I've set
  `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome
  terminal also exhibits other misbehaviour wrt. to this, occasionally
  refusing to get focus, or alternatively losing the focus, despite
  mouse cursor being over the terminal window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.8-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
  Uname: Linux 5.4.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64

[Desktop-packages] [Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)

2020-05-11 Thread Jani Uusitalo

Happened again:

May 11 17:05:50 saegusa gnome-shell[3619]: WL: compositor bug: The 
compositor tried to use an object from one client in a 'wl_pointer.enter' for a 
different client.
May 11 17:05:50 saegusa gnome-shell[3619]: WL: error in client 
communication (pid 5170)
May 11 17:05:50 saegusa gnome-terminal-[5170]: Error reading events from 
display: Katkennut putki
May 11 17:05:50 saegusa systemd[3544]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE
May 11 17:05:50 saegusa systemd[3544]: gnome-terminal-server.service: 
Failed with result 'exit-code'.
May 11 17:05:50 saegusa systemd[3544]: 
vte-spawn-b269c64d-5376-49ec-83fc-9f4806ac4b30.scope: Succeeded.
May 11 17:05:50 saegusa systemd[3544]: 
vte-spawn-3294a176-7b32-4995-a11b-fe0fea8b07bc.scope: Succeeded.
May 11 17:05:50 saegusa systemd[3544]: 
vte-spawn-0b59afd0-1aed-4081-a7d1-801e7c405399.scope: Succeeded.
May 11 17:05:51 saegusa systemd[3544]: Started Application launched by 
gnome-shell.

But there's still nothing in /var/crash, nor on the Error Tracker (aside
from the aforementioned, unrelated crash from last week).

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

Title:
  WL: compositor bug: The compositor tried to use an object from one
  client in a 'wl_pointer.enter' for a different client (resulting in
  Gnome terminal crashing)

Status in gnome-terminal package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Since upgrading to 20.04 and switching to Wayland, Gnome terminal
  occasionally crashes. I interpret the corresponding logs to mean that
  it's actually Wayland that fails to do something in the background,
  which then takes down Gnome terminal:

  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The 
compositor tried to use an object from one client in a 'wl_pointer.enter' for a 
different client.
  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client 
communication (pid 11639)
  touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events 
from display: Katkennut putki
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Main process exited, code=exited, status=1/FAILURE
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Failed with result 'exit-code'.

  I have yet to nail down the precise circumstances, as this has (so
  far) been somewhat rare, having occurred perhaps once or twice a week.

  Since the log mentions pointer, I should perhaps mention that I've set
  `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome
  terminal also exhibits other misbehaviour wrt. to this, occasionally
  refusing to get focus, or alternatively losing the focus, despite
  mouse cursor being over the terminal window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.8-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
  Uname: Linux 5.4.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 15:22:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed
   xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2016-10-13 (1302 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic

[Desktop-packages] [Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)

2020-05-11 Thread Jani Uusitalo

** Attachment added: "syslog.5-excerpt.log"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1877568/+attachment/5369829/+files/syslog.5-excerpt.log

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

Title:
  WL: compositor bug: The compositor tried to use an object from one
  client in a 'wl_pointer.enter' for a different client (resulting in
  Gnome terminal crashing)

Status in gnome-terminal package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Since upgrading to 20.04 and switching to Wayland, Gnome terminal
  occasionally crashes. I interpret the corresponding logs to mean that
  it's actually Wayland that fails to do something in the background,
  which then takes down Gnome terminal:

  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The 
compositor tried to use an object from one client in a 'wl_pointer.enter' for a 
different client.
  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client 
communication (pid 11639)
  touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events 
from display: Katkennut putki
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Main process exited, code=exited, status=1/FAILURE
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Failed with result 'exit-code'.

  I have yet to nail down the precise circumstances, as this has (so
  far) been somewhat rare, having occurred perhaps once or twice a week.

  Since the log mentions pointer, I should perhaps mention that I've set
  `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome
  terminal also exhibits other misbehaviour wrt. to this, occasionally
  refusing to get focus, or alternatively losing the focus, despite
  mouse cursor being over the terminal window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.8-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
  Uname: Linux 5.4.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 15:22:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed
   xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2016-10-13 (1302 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic 
root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A

[Desktop-packages] [Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)

2020-05-11 Thread Jani Uusitalo

Turns out the online service was just a little slow to update, and there
are in fact reports sent. But the only one post-20.04-upgrade is [1]
from last week, which is a gnome-shell crash and IIRC, unrelated to the
terminal issue here. It seemed to be triggered by something related to
media files and Nautilus, and the logs from the time are different; I'm
attaching them here. (I had separated gnome-shell logs out from the main
syslog, but I've since reverted back to having everything in syslog.)

* [1] https://errors.ubuntu.com/oops/26828e26-8fc9-11ea-
acd0-fa163e983629


** Attachment added: "gnome-shell.log"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1877568/+attachment/5369828/+files/gnome-shell.log

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

Title:
  WL: compositor bug: The compositor tried to use an object from one
  client in a 'wl_pointer.enter' for a different client (resulting in
  Gnome terminal crashing)

Status in gnome-terminal package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Since upgrading to 20.04 and switching to Wayland, Gnome terminal
  occasionally crashes. I interpret the corresponding logs to mean that
  it's actually Wayland that fails to do something in the background,
  which then takes down Gnome terminal:

  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The 
compositor tried to use an object from one client in a 'wl_pointer.enter' for a 
different client.
  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client 
communication (pid 11639)
  touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events 
from display: Katkennut putki
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Main process exited, code=exited, status=1/FAILURE
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Failed with result 'exit-code'.

  I have yet to nail down the precise circumstances, as this has (so
  far) been somewhat rare, having occurred perhaps once or twice a week.

  Since the log mentions pointer, I should perhaps mention that I've set
  `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome
  terminal also exhibits other misbehaviour wrt. to this, occasionally
  refusing to get focus, or alternatively losing the focus, despite
  mouse cursor being over the terminal window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.8-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
  Uname: Linux 5.4.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 15:22:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed
   xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2016-10-13 (1302 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic 
root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag:

[Desktop-packages] [Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)

2020-05-11 Thread Jani Uusitalo

Thanks for the instructions, Daniel! I found no crash files either
locally or online, so I've implemented the workaround now, and will try
to trigger the crash again.

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

Title:
  WL: compositor bug: The compositor tried to use an object from one
  client in a 'wl_pointer.enter' for a different client (resulting in
  Gnome terminal crashing)

Status in gnome-terminal package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Since upgrading to 20.04 and switching to Wayland, Gnome terminal
  occasionally crashes. I interpret the corresponding logs to mean that
  it's actually Wayland that fails to do something in the background,
  which then takes down Gnome terminal:

  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The 
compositor tried to use an object from one client in a 'wl_pointer.enter' for a 
different client.
  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client 
communication (pid 11639)
  touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events 
from display: Katkennut putki
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Main process exited, code=exited, status=1/FAILURE
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Failed with result 'exit-code'.

  I have yet to nail down the precise circumstances, as this has (so
  far) been somewhat rare, having occurred perhaps once or twice a week.

  Since the log mentions pointer, I should perhaps mention that I've set
  `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome
  terminal also exhibits other misbehaviour wrt. to this, occasionally
  refusing to get focus, or alternatively losing the focus, despite
  mouse cursor being over the terminal window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.8-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
  Uname: Linux 5.4.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 15:22:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed
   xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2016-10-13 (1302 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic 
root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A

[Desktop-packages] [Bug 1877568] [NEW] WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)

2020-05-08 Thread Jani Uusitalo

Public bug reported:

Since upgrading to 20.04 and switching to Wayland, Gnome terminal
occasionally crashes. I interpret the corresponding logs to mean that
it's actually Wayland that fails to do something in the background,
which then takes down Gnome terminal:

touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The 
compositor tried to use an object from one client in a 'wl_pointer.enter' for a 
different client.
touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client 
communication (pid 11639)
touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events from 
display: Katkennut putki
touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded.
touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded.
touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Main process exited, code=exited, status=1/FAILURE
touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Failed with result 'exit-code'.

I have yet to nail down the precise circumstances, as this has (so far)
been somewhat rare, having occurred perhaps once or twice a week.

Since the log mentions pointer, I should perhaps mention that I've set
`org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome
terminal also exhibits other misbehaviour wrt. to this, occasionally
refusing to get focus, or alternatively losing the focus, despite mouse
cursor being over the terminal window.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xwayland 2:1.20.8-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
Uname: Linux 5.4.0-30-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May  8 15:22:28 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed (WARNING! 
Diff between built and installed module!)
 fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed (WARNING! 
Diff between built and installed module!)
 xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed
 xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
InstallationDate: Installed on 2016-10-13 (1302 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic 
root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1505
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H77-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Tue Mar 20 15:09:56 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


** Tags:

[Desktop-packages] [Bug 1874808] [NEW] Unmuting Twitch video pauses playback, when media.autoplay.enabled.user-gestures-needed=false, media.autoplay.default=1

2020-04-24 Thread Jani Uusitalo

Public bug reported:

With `media.autoplay.enabled.user-gestures-needed` set to false and
`media.autoplay.default` set to 1 (block audio), which is the default
(and other autoplay-related settings in their defaults as well), a
Twitch video can only be either paused or playing muted; unmuting the
video pauses it and vice versa.

== Steps to reproduce ==
1. Open about:config
2. Search for autoplay in the settings
3. Set media.autoplay.enabled.user-gestures-needed to false
4. Set media.autoplay.default to 1
5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033
6. Try to unmute the video

== What happens ==
The video is unmuted, but also paused

== What I expect to happen ==
For the video to continue playing, unmuted

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 75.0+build3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BuildID: 20200403170909
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 16:33:46 2020
InstallationDate: Installed on 2016-10-13 (1289 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: firefox
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug focal wayland-session

** Bug watch added: Mozilla Bugzilla #1631642
   https://bugzilla.mozilla.org/show_bug.cgi?id=1631642

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1631642
   Importance: Unknown
   Status: Unknown

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

Title:
  Unmuting Twitch video pauses playback, when media.autoplay.enabled
  .user-gestures-needed=false, media.autoplay.default=1

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

Bug description:
  With `media.autoplay.enabled.user-gestures-needed` set to false and
  `media.autoplay.default` set to 1 (block audio), which is the default
  (and other autoplay-related settings in their defaults as well), a
  Twitch video can only be either paused or playing muted; unmuting the
  video pauses it and vice versa.

  == Steps to reproduce ==
  1. Open about:config
  2. Search for autoplay in the settings
  3. Set media.autoplay.enabled.user-gestures-needed to false
  4. Set media.autoplay.default to 1
  5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033
  6. Try to unmute the video

  == What happens ==
  The video is unmuted, but also paused

  == What I expect to happen ==
  For the video to continue playing, unmuted

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 16:33:46 2020
  InstallationDate: Installed on 2016-10-13 (1289 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1874808/+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 1871868] Re: Keyboard shortcut restoring shortcut cut short when localized

2020-04-10 Thread Jani Uusitalo

Done. Thanks, Sebastien!

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

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2616
   Importance: Unknown
   Status: Unknown

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

Title:
  Keyboard shortcut restoring shortcut cut short when localized

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

Bug description:
  When trying to start a virtual machine with Gnome Boxes, I get a
  prompt about keyboard shortcuts. The prompt text is localized, but
  translated back to English (I think, based on [1]) it says:

  Boxes wants to inhibit shortcuts

  You can restore shortcuts by pressing Super+Escape.

  In my locale (Finnish), it says

  Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa.

  Voit palauttaa pikanäppäinten toiminnan painamalla Super...

  (sic; see attached photo)

  So the actual key combination is truncated, defeating the point of
  that part of the text.

  This isn't a localization error (AFAICT; see [2]). It's caused by the
  text being forced to fit on a single line of an arbitrarily fixed
  width, instead of wrapping to span as many lines as needed.

  (I'm reporting this against gnome-shell as opposed gnome-boxes based
  on [3]. Feel free to reassign as necessary.)

  * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28
  * [2] 
https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10show=allsearch=pikan%C3%A4pp%C3%A4inten
  * [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 18:29:14 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-13 (1274 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1871868/+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 1871868] [NEW] Keyboard shortcut restoring shortcut cut short when localized

2020-04-09 Thread Jani Uusitalo

Public bug reported:

When trying to start a virtual machine with Gnome Boxes, I get a prompt
about keyboard shortcuts. The prompt text is localized, but translated
back to English (I think, based on [1]) it says:

Boxes wants to inhibit shortcuts

You can restore shortcuts by pressing Super+Escape.

In my locale (Finnish), it says

Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa.

Voit palauttaa pikanäppäinten toiminnan painamalla Super...

(sic; see attached photo)

So the actual key combination is truncated, defeating the point of that
part of the text.

This isn't a localization error (AFAICT; see [2]). It's caused by the
text being forced to fit on a single line of an arbitrarily fixed width,
instead of wrapping to span as many lines as needed.

(I'm reporting this against gnome-shell as opposed gnome-boxes based on
[3]. Feel free to reassign as necessary.)

* [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28
* [2] 
https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10show=allsearch=pikan%C3%A4pp%C3%A4inten
* [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.0-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
Uname: Linux 5.4.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  9 18:29:14 2020
DisplayManager: gdm3
InstallationDate: Installed on 2016-10-13 (1274 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago)

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


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

** Attachment added: "Localized prompt about keyboard shortcuts being inhibited"
   
https://bugs.launchpad.net/bugs/1871868/+attachment/5350374/+files/20200409_180221.jpg

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

Title:
  Keyboard shortcut restoring shortcut cut short when localized

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When trying to start a virtual machine with Gnome Boxes, I get a
  prompt about keyboard shortcuts. The prompt text is localized, but
  translated back to English (I think, based on [1]) it says:

  Boxes wants to inhibit shortcuts

  You can restore shortcuts by pressing Super+Escape.

  In my locale (Finnish), it says

  Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa.

  Voit palauttaa pikanäppäinten toiminnan painamalla Super...

  (sic; see attached photo)

  So the actual key combination is truncated, defeating the point of
  that part of the text.

  This isn't a localization error (AFAICT; see [2]). It's caused by the
  text being forced to fit on a single line of an arbitrarily fixed
  width, instead of wrapping to span as many lines as needed.

  (I'm reporting this against gnome-shell as opposed gnome-boxes based
  on [3]. Feel free to reassign as necessary.)

  * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28
  * [2] 
https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10show=allsearch=pikan%C3%A4pp%C3%A4inten
  * [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 18:29:14 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-13 (1274 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871868/+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 1871868] Re: Keyboard shortcut restoring shortcut cut short when localized

2020-04-09 Thread Jani Uusitalo

Oh and I'm using Wayland, in case it matters here. Haven't yet tried
whether Xorg is similarly affected.

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

Title:
  Keyboard shortcut restoring shortcut cut short when localized

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When trying to start a virtual machine with Gnome Boxes, I get a
  prompt about keyboard shortcuts. The prompt text is localized, but
  translated back to English (I think, based on [1]) it says:

  Boxes wants to inhibit shortcuts

  You can restore shortcuts by pressing Super+Escape.

  In my locale (Finnish), it says

  Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa.

  Voit palauttaa pikanäppäinten toiminnan painamalla Super...

  (sic; see attached photo)

  So the actual key combination is truncated, defeating the point of
  that part of the text.

  This isn't a localization error (AFAICT; see [2]). It's caused by the
  text being forced to fit on a single line of an arbitrarily fixed
  width, instead of wrapping to span as many lines as needed.

  (I'm reporting this against gnome-shell as opposed gnome-boxes based
  on [3]. Feel free to reassign as necessary.)

  * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28
  * [2] 
https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10show=allsearch=pikan%C3%A4pp%C3%A4inten
  * [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 18:29:14 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-13 (1274 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871868/+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 1754125] Re: Rhythmbox stays running in the background after quit

2020-04-06 Thread Jani Uusitalo

For some of the depressing history of this, see bug #875002 (which has
been incorrectly marked as fixed by someone without a clue) from way
back in 2011.

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

Title:
  Rhythmbox stays running in the background after quit

Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  If you do ps -alx you will see rhythmbox process still running. It
  causes opening rhythmbox to hang when trying to open again

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-1ubuntu1
  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: ubuntu:GNOME
  Date: Wed Mar  7 13:21:51 2018
  InstallationDate: Installed on 2018-03-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+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 1871107] [NEW] Popup menu jumps to top left window corner when focus follows mouse (in Wayland)

2020-04-06 Thread Jani Uusitalo

Public bug reported:

I'm using 20.04 and a Wayland session. My preferred focus mode is to
have it follow the mouse cursor:

$ gsettings get org.gnome.desktop.wm.preferences focus-mode
'mouse'

Unfortunately this causes GTK apps' popup (RMB) menu to jump to the app
window corner when opened. I'm attaching a screencast, where I
demonstrate the bug first, then reset focus-mode to 'click' to
demonstrate the bug no longer manifesting. (Please excuse the flashing.
It's just a video artefact caused by Gnome's built in screen recorder,
which was the only one that at least somewhat worked.)

This has been reported upstream, where a fix was recently merged:
https://gitlab.gnome.org/GNOME/mutter/issues/1103

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: mutter 3.36.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29
Uname: Linux 5.4.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  6 16:02:37 2020
InstallationDate: Installed on 2016-10-13 (1270 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
SourcePackage: mutter
UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago)

** Affects: mutter
 Importance: Unknown
 Status: Unknown

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


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

** Attachment added: "testi.webm"
   https://bugs.launchpad.net/bugs/1871107/+attachment/5347736/+files/testi.webm

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #1103
   https://gitlab.gnome.org/GNOME/mutter/issues/1103

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/issues/1103
   Importance: Unknown
   Status: Unknown

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

Title:
  Popup menu jumps to top left window corner when focus follows mouse
  (in Wayland)

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  New

Bug description:
  I'm using 20.04 and a Wayland session. My preferred focus mode is to
  have it follow the mouse cursor:

  $ gsettings get org.gnome.desktop.wm.preferences focus-mode
  'mouse'

  Unfortunately this causes GTK apps' popup (RMB) menu to jump to the
  app window corner when opened. I'm attaching a screencast, where I
  demonstrate the bug first, then reset focus-mode to 'click' to
  demonstrate the bug no longer manifesting. (Please excuse the
  flashing. It's just a video artefact caused by Gnome's built in screen
  recorder, which was the only one that at least somewhat worked.)

  This has been reported upstream, where a fix was recently merged:
  https://gitlab.gnome.org/GNOME/mutter/issues/1103

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29
  Uname: Linux 5.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 16:02:37 2020
  InstallationDate: Installed on 2016-10-13 (1270 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1871107/+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 1798074] Re: LIbreoffice crashes on startup

2019-06-26 Thread Jani Uusitalo

Happy to report that the proposed packages did fix the issue for me
also. Thanks everyone!

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

Title:
  LIbreoffice crashes on startup

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Committed
Status in libreoffice-l10n source package in Bionic:
  Fix Committed
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * This effects all bionic and cosmic users who have 'libcpd*' 'cpdb*'
  packages installed.

   * The fix is currently in LibreOffice 6.2.0+ on disco and eoan.

  [Test Case]

   1. apt install cpdb-backend-gcp
   2. run LibreOffice

  [Regression Potential]

   * We're backporting a patch that has already been applied to 6.2.0+
  with no regression, so potential for regression here is low.

   * A combination of autopkgtests and manual testing should provide
  reasonable confidence that no regressions sneaked in.

  [Original Description]

  On starting up LibreOffice, it crashes. Starting from a terminal with
  just "libreoffice", I see the "general open a document" libreoffice
  window and a popup dialog titled "LibreOffice 6.0 Document Recovery",
  with text "Due to an unexpected error, LibreOffice crashed. All the
  files you were working on will now be saved. The next time LibreOffice
  is launched, your files will be recovered automatically. The following
  files will be recovered:" (and no files to be recovered are listed).
  Clicking "OK" on this dialog hides it and the general window, and then
  shows them both again; clicking OK on that dialog exits. LibreOffice
  does not start.

  Running "libreoffice --norestore" gives a stack trace:

  $ libreoffice --norestore
  Application Error

  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1]
  
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7fa00baf60f5]
  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0)[0x7fa00baf64c0]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fa00baf654c]
  /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x414d4)[0x7f9ff8b524d4]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7fa0111f68ce]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7fa0111f8075]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d12fa3)[0x7fa010221fa3]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cee756)[0x7fa0111fd756]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7fa0111fd860]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7fa0102430c5]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x55dd01f4578b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fa00dee5b97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x55dd01f457ca]

  I have tried entirely removing my profile, ~/.config/libreoffice , but
  the same problem still exhibits.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-common 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu

[Desktop-packages] [Bug 1798074] Re: LIbreoffice crashes on startup

2019-05-13 Thread Jani Uusitalo

@Marcus: yup, that seems to be it:

jani@saegusa:~$ dpkg -l 'libcpd*' 'cpdb*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Nimi VersioArkkitehtuuri Kuvaus
+++--=-=-==
ii  cpdb-backend-gcp 1.0.0-0ubuntu2amd64 Common Print 
Dialog Backends - Google Cloud Print Back
ii  libcpdb-libs-common0:amd 1.1.1-0ubuntu1amd64 Common Print 
Dialog Backends - Interface Library for B
jani@saegusa:~$ SAL_DISABLE_CPD=true libreoffice --norestore
func=xmlSecCheckVersionExt:file=xmlsec.c:line=188:obj=unknown:subj=unknown:error=19:invalid
 version:mode=abi compatible;expected minor version=2;real minor 
version=2;expected subminor version=25;real subminor version=26

That is, no stack trace nor other apparent problems when starting LO
with SAL_DISABLE_CPD=true.

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

Title:
  LIbreoffice crashes on startup

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

Bug description:
  On starting up LibreOffice, it crashes. Starting from a terminal with
  just "libreoffice", I see the "general open a document" libreoffice
  window and a popup dialog titled "LibreOffice 6.0 Document Recovery",
  with text "Due to an unexpected error, LibreOffice crashed. All the
  files you were working on will now be saved. The next time LibreOffice
  is launched, your files will be recovered automatically. The following
  files will be recovered:" (and no files to be recovered are listed).
  Clicking "OK" on this dialog hides it and the general window, and then
  shows them both again; clicking OK on that dialog exits. LibreOffice
  does not start.

  Running "libreoffice --norestore" gives a stack trace:


  $ libreoffice --norestore
  Application Error

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1]
  
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7fa00baf60f5]
  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0)[0x7fa00baf64c0]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fa00baf654c]
  /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x414d4)[0x7f9ff8b524d4]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7fa0111f68ce]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7fa0111f8075]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d12fa3)[0x7fa010221fa3]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cee756)[0x7fa0111fd756]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7fa0111fd860]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7fa0102430c5]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x55dd01f4578b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fa00dee5b97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x55dd01f457ca]

  I have tried entirely removing my profile, ~/.config/libreoffice , but
  the same problem still exhibits.

  ProblemType: Bug
  DistroRelease: Ubuntu

[Desktop-packages] [Bug 1798074] Re: LIbreoffice crashes on startup

2019-05-04 Thread Jani Uusitalo

Can't speak for Stuart, but I'm the other one affected, and still so:

jani@saegusa:~$ apt-cache policy libreoffice
libreoffice:
  Asennettu: 1:6.0.7-0ubuntu0.18.04.5
  Ehdokas:   1:6.0.7-0ubuntu0.18.04.5
  Versiotaulukko:
 *** 1:6.0.7-0ubuntu0.18.04.5 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
500 http://archive.ubuntu.com/ubuntu bionic-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 1:6.0.3-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
jani@saegusa:~$ libreoffice --norestore
Application Error


Fatal exception: Signal 6
Stack:
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f5cb050b568]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3a6)[0x7f5cb05343a6]
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f5cb0145f20]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f5cb0145e97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f5cb0147801]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2d5c882)[0x7f5cb34ae882]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7f5cb343a2b2]
/usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d470)[0x7f5cb245f470]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2cedc5d)[0x7f5cb343fc5d]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7f5cb050e3b2]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c26f)[0x7f5cb053426f]
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f5cb0145f20]
/lib/x86_64-linux-gnu/libc.so.6(+0xb1646)[0x7f5cb01b8646]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7f5cae74dce4]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2d6aa3b)[0x7f5cb34bca3b]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc92d6)[0x7f5cae7432d6]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9518)[0x7f5cae743518]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d1a3)[0x7f5cae7071a3]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8dbc6)[0x7f5cae707bc6]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc1082)[0x7f5cae73b082]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d1a3)[0x7f5cae7071a3]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d1d9)[0x7f5cae7071d9]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7f5cae15b285]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c650)[0x7f5cae15b650]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f5cae15b6dc]
/usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x41444)[0x7f5c9ac63444]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7f5cb343a9be]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7f5cb343c165]
/usr/lib/libreoffice/program/libmergedlo.so(+0x1d12e93)[0x7f5cb2464e93]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2cef846)[0x7f5cb3441846]
/usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f5cb3441950]
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7f5cb2485fb5]
/usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x557ff5eff78b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f5cb0128b97]
/usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x557ff5eff7ca]

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

Title:
  LIbreoffice crashes on startup

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  On starting up LibreOffice, it crashes. Starting from a terminal with
  just "libreoffice", I see the "general open a document" libreoffice
  window and a popup dialog titled "LibreOffice 6.0 Document Recovery",
  with text "Due to an unexpected error, LibreOffice crashed. All the
  files you were working on will now be saved. The next time LibreOffice
  is launched, your files will be recovered automatically. The following
  files will be recovered:" (and no files to be recovered are listed).
  Clicking "OK" on this dialog hides it and the general window, and then
  shows them both again; clicking OK on that dialog exits. LibreOffice
  does not start.

  Running "libreoffice --norestore" gives a stack trace:


  $ libreoffice --norestore
  Application Error

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d]

[Desktop-packages] [Bug 1820514] Re: Saving a web page from Tom's Hardware forums fails

2019-03-19 Thread Jani Uusitalo

Yep, retrying does work.

I've now reported this to Mozilla and linked to it. Thanks, Olivier!


** Bug watch added: Mozilla Bugzilla #1536530
   https://bugzilla.mozilla.org/show_bug.cgi?id=1536530

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1536530
   Importance: Unknown
   Status: Unknown

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

Title:
  Saving a web page from Tom's Hardware forums fails

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

Bug description:
  == Steps to reproduce ==
  1. Open 
https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/
  2. Right-click and select 'Save page as'. Point the dialog to your directory 
of choice.

  == What I expect to happen ==
  For the directory to contain a downloaded copy of the page.

  == What happens ==
  There's no copy of the page in the target directory. Going to about:downloads 
reveals that the download has failed, without further details.

  == Other info ==
  I'm reporting this from up-to-date Disco, albeit with a 4.* kernel (as gdm 
currently fails to start in my VirtualBox VM with 5.*) but it's equally 
reproducible in Bionic.

  Any page under https://forums.tomshardware.com/ seems to trigger this,
  but I have yet to come across other sites that do. Pages can even be
  saved from the main Tom's Hardware domain
  (https://www.tomshardware.com/) without issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 66.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
  Uname: Linux 4.19.0-9-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jani   1324 F pulseaudio
  BuildID: 20190315094614
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 17 15:37:04 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-09-30 (167 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1820514/+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 1820514] Re: Saving a web page from Tom's Hardware forums fails

2019-03-18 Thread Jani Uusitalo

Tested all combinations of both (Ctrl-s/context menu in safe mode and
normal mode), all with the same results. Could this be locale-dependent?
The UI is in English in safe mode though, so I'm guessing safe mode
should be locale-independent, as I'm on fi_FI.UTF-8 otherwise.

And just to clarify: my testing of Bionic was on real hardware as well,
and I ran these latest tests on Cosmic on another computer (real
hardware).

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

Title:
  Saving a web page from Tom's Hardware forums fails

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  == Steps to reproduce ==
  1. Open 
https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/
  2. Right-click and select 'Save page as'. Point the dialog to your directory 
of choice.

  == What I expect to happen ==
  For the directory to contain a downloaded copy of the page.

  == What happens ==
  There's no copy of the page in the target directory. Going to about:downloads 
reveals that the download has failed, without further details.

  == Other info ==
  I'm reporting this from up-to-date Disco, albeit with a 4.* kernel (as gdm 
currently fails to start in my VirtualBox VM with 5.*) but it's equally 
reproducible in Bionic.

  Any page under https://forums.tomshardware.com/ seems to trigger this,
  but I have yet to come across other sites that do. Pages can even be
  saved from the main Tom's Hardware domain
  (https://www.tomshardware.com/) without issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 66.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
  Uname: Linux 4.19.0-9-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jani   1324 F pulseaudio
  BuildID: 20190315094614
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 17 15:37:04 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-09-30 (167 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1820514/+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 1820514] [NEW] Saving a web page from Tom's Hardware forums fails

2019-03-17 Thread Jani Uusitalo

Public bug reported:

== Steps to reproduce ==
1. Open 
https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/
2. Right-click and select 'Save page as'. Point the dialog to your directory of 
choice.

== What I expect to happen ==
For the directory to contain a downloaded copy of the page.

== What happens ==
There's no copy of the page in the target directory. Going to about:downloads 
reveals that the download has failed, without further details.

== Other info ==
I'm reporting this from up-to-date Disco, albeit with a 4.* kernel (as gdm 
currently fails to start in my VirtualBox VM with 5.*) but it's equally 
reproducible in Bionic.

Any page under https://forums.tomshardware.com/ seems to trigger this,
but I have yet to come across other sites that do. Pages can even be
saved from the main Tom's Hardware domain
(https://www.tomshardware.com/) without issues.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: firefox 66.0+build3-0ubuntu1
ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
Uname: Linux 4.19.0-9-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jani   1324 F pulseaudio
BuildID: 20190315094614
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 17 15:37:04 2019
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2018-09-30 (167 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930)
IpRoute:
 default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
 169.254.0.0/16 dev enp0s3 scope link metric 1000
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-bug disco

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

Title:
  Saving a web page from Tom's Hardware forums fails

Status in firefox package in Ubuntu:
  New

Bug description:
  == Steps to reproduce ==
  1. Open 
https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/
  2. Right-click and select 'Save page as'. Point the dialog to your directory 
of choice.

  == What I expect to happen ==
  For the directory to contain a downloaded copy of the page.

  == What happens ==
  There's no copy of the page in the target directory. Going to about:downloads 
reveals that the download has failed, without further details.

  == Other info ==
  I'm reporting this from up-to-date Disco, albeit with a 4.* kernel (as gdm 
currently fails to start in my VirtualBox VM with 5.*) but it's equally 
reproducible in Bionic.

  Any page under https://forums.tomshardware.com/ seems to trigger this,
  but I have yet to come across other sites that do. Pages can even be
  saved from the main Tom's Hardware domain
  (https://www.tomshardware.com/) without issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 66.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
  Uname: Linux 4.19.0-9-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jani   1324 F pulseaudio
  BuildID: 20190315094614
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 17 15:37:04 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or

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

2019-02-07 Thread Jani Uusitalo

A new log; still nothing useful from colord AFAICT, despite the
--verbose.

** Attachment added: "Unrecoverable failure with gsd-color --verbose"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+attachment/5236695/+files/joured.log

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

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

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

Bug description:
  I've had this happen a couple of times now since upgrading to 18.04:
  soon (perhaps within a minute) after logging in, Gnome session ends
  abruptly and I'm thrown back to the login screen. IIRC, in both
  instances this occurred on the first login after boot, so it does not
  reoccur on the subsequent re-login, and not on every login (very
  rarely in fact), and for now I have no better steps to reproduce this
  other than "boot, log in".

  Bug #1663839 (reported against 17.04) seems similar, as does bug
  #1731428 (reported against 17.10).

  journalctl output during the issue:

  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Color.desktop
  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but 
the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 17:07:14 2018
  InstallationDate: Installed on 2016-10-13 (550 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+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 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

2019-01-24 Thread Jani Uusitalo

...except that --debug isn't one of gsd-color's recognized parameters,
and adding it caused GDM to fail to start. I changed it to --verbose
which is available.

10.08 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color 
--help-all
Usage:
  gsd-color [OPTION?] color

Help Options:
  -h, --help   Show help options
  --help-all   Show all help options
  --help-gtk   Show GTK+ Options

GTK+ Options
  --class=CLASSProgram class as used by the window manager
  --name=NAME  Program name as used by the window manager
  --gdk-debug=FLAGSGDK debugging flags to set
  --gdk-no-debug=FLAGS GDK debugging flags to unset
  --gtk-module=MODULES Load additional GTK+ modules
  --g-fatal-warnings   Make all warnings fatal
  --gtk-debug=FLAGSGTK+ debugging flags to set
  --gtk-no-debug=FLAGS GTK+ debugging flags to unset

Application Options:
  --exit-time  Exit after n seconds time
  --dummy-name Name when using the dummy daemon
  -v, --verboseVerbose
  --display=DISPLAYX display to use

There's also --gtk-debug and --gdk-debug, but I could do with a little
help for what to select for those, as just giving 'all' seems a little
counterproductive (for instance, "touchscreen" and "interactive" don't
seem very useful here).

10.03 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color 
--gtk-debug help 
Supported debug values: misc plugsocket text tree updates keybindings 
multihead modules geometry icontheme printing builder size-request no-css-cache 
baselines pixel-cache no-pixel-cache interactive touchscreen actions resize 
layout all help

10.04 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color 
--gdk-debug help
Supported debug values: events misc dnd xim nograbs input cursor multihead 
xinerama draw eventloop frames settings opengl all help
Error parsing option --gdk-debug

(Looks like --gdk-debug reports an error with 'help', despite having
just listed it as one of the options.)

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

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

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

Bug description:
  I've had this happen a couple of times now since upgrading to 18.04:
  soon (perhaps within a minute) after logging in, Gnome session ends
  abruptly and I'm thrown back to the login screen. IIRC, in both
  instances this occurred on the first login after boot, so it does not
  reoccur on the subsequent re-login, and not on every login (very
  rarely in fact), and for now I have no better steps to reproduce this
  other than "boot, log in".

  Bug #1663839 (reported against 17.04) seems similar, as does bug
  #1731428 (reported against 17.10).

  journalctl output during the issue:

  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Color.desktop
  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but 
the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 17:07:14 2018
  InstallationDate: Installed on 2016-10-13 (550 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+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 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

2019-01-23 Thread Jani Uusitalo

Sure, I've now set it up thus and will post the results once I hit this
again (it seems pretty unpredictable, so could be anything from days to
weeks).

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

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

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

Bug description:
  I've had this happen a couple of times now since upgrading to 18.04:
  soon (perhaps within a minute) after logging in, Gnome session ends
  abruptly and I'm thrown back to the login screen. IIRC, in both
  instances this occurred on the first login after boot, so it does not
  reoccur on the subsequent re-login, and not on every login (very
  rarely in fact), and for now I have no better steps to reproduce this
  other than "boot, log in".

  Bug #1663839 (reported against 17.04) seems similar, as does bug
  #1731428 (reported against 17.10).

  journalctl output during the issue:

  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Color.desktop
  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but 
the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 17:07:14 2018
  InstallationDate: Installed on 2016-10-13 (550 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+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 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

2019-01-23 Thread Jani Uusitalo

Here you go. Had this occur twice in a row just now, so my original
theory of the second login never failing was false.


** Attachment added: "journalctl from a boot with two dead whales"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+attachment/5231688/+files/joured.log

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

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

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

Bug description:
  I've had this happen a couple of times now since upgrading to 18.04:
  soon (perhaps within a minute) after logging in, Gnome session ends
  abruptly and I'm thrown back to the login screen. IIRC, in both
  instances this occurred on the first login after boot, so it does not
  reoccur on the subsequent re-login, and not on every login (very
  rarely in fact), and for now I have no better steps to reproduce this
  other than "boot, log in".

  Bug #1663839 (reported against 17.04) seems similar, as does bug
  #1731428 (reported against 17.10).

  journalctl output during the issue:

  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Color.desktop
  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but 
the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 17:07:14 2018
  InstallationDate: Installed on 2016-10-13 (550 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+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 1808690] Re: Page content slightly transparent, reveals content from another window below

2018-12-16 Thread Jani Uusitalo

** Attachment added: "Same screenshot with added hints about see-through 
content"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1808690/+attachment/5222692/+files/spectral-highlights.png

** Description changed:

  Under some circumstances, content from another Firefox window hidden
- behind another leaks onto the top one. Reproducible in both Bionic and
- Disco, reporting this from Disco.
+ behind another leaks onto the top one. Reproducible in both Bionic (with
+ Intel graphics) and Disco (in a VirtualBox VM), reporting this from
+ Disco.
  
  == Steps to reproduce ==
  1. Open one Firefox window, drag it to the right side of screen to fill the 
right half, and navigate to https://www.twitch.tv/rifftrax
  2. Open another Firefox window, maximize it on top of the first one, and use 
this topmost window to open https://www.youtube.com/watch?v=P5dxd-ocaE8
  
  == What happens ==
  White parts of content in Firefox window #1 cast a spectral shadow on the 
black parts of content in Firefox window #2. It's quite subtle, but luckily can 
be caught in screenshots: see attachments below. Pausing the Youtube video 
seems to make the effect to go away (the transparency disappears).
  
  == What I'd expect to happen ==
  For the topmost window to be completely opaque, i.e. not to see anything from 
behind the topmost window.
  
  == Other info ==
  Though I don't think this is tied the two sites I've used as an example, 
they're the first and only ones I've happened to encounter this with. I've yet 
to find other reports this, apart from one /r/Fedora thread mentioning 
something similar: 
https://www.reddit.com/r/Fedora/comments/7m9m4h/youtube_videos_are_transparent_kind_of_in_firefox/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 64.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
  Uname: Linux 4.19.0-9-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  jani   1748 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  jani   1748 F pulseaudio
  BuildID: 20181207223303
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 16 15:30:58 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-09-30 (76 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930)
  IpRoute:
-  default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
-  10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
-  169.254.0.0/16 dev enp0s3 scope link metric 1000
+  default via 10.0.2.2 dev enp0s3 proto dhcp metric 100
+  10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100
+  169.254.0.0/16 dev enp0s3 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fi_FI.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fi_FI.UTF-8
+  SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=64.0/20181207223303
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

** Description changed:

  Under some circumstances, content from another Firefox window hidden
  behind another leaks onto the top one. Reproducible in both Bionic (with
  Intel graphics) and Disco (in a VirtualBox VM), reporting this from
  Disco.
  
  == Steps to reproduce ==
  1. Open one Firefox window, drag it to the right side of screen to fill the 
right half, and navigate to https://www.twitch.tv/rifftrax
- 2. Open another Firefox window, maximize it on top of the first one, and use 
this topmost window to open https://www.youtube.com/watch?v=P5dxd-ocaE8
+ 2. Open another Firefox window, maximize it on top of the first one, and use 
this topmost window to open

[Desktop-packages] [Bug 1808690] [NEW] Page content slightly transparent, reveals content from another window below

2018-12-16 Thread Jani Uusitalo

Public bug reported:

Under some circumstances, content from one Firefox window hidden behind
another leaks onto the top one. Reproducible in both Bionic (with Intel
graphics) and Disco (in a VirtualBox VM), reporting this from Disco.

== Steps to reproduce ==
1. Open one Firefox window, drag it to the right side of screen to fill the 
right half, and navigate to https://www.twitch.tv/rifftrax
2. Open another Firefox window, maximize it on top of the first one, and use 
this topmost window to open https://www.youtube.com/watch?v=P5dxd-ocaE8 and 
expand the Youtube view to 'theatre' mode

== What happens ==
White parts of content in Firefox window #1 cast a spectral shadow on the black 
parts of content in Firefox window #2. It's quite subtle, but luckily can be 
caught in screenshots: see attachments below. Pausing the Youtube video seems 
to make the effect to go away (the transparency disappears).

== What I'd expect to happen ==
For the topmost window to be completely opaque, i.e. not to see anything from 
behind the topmost window whether the video is playing or not.

== Other info ==
Though I don't think this is tied the two sites I've used as an example, 
they're the first and only ones I've happened to encounter this with. I've yet 
to find other reports about this, apart from one /r/Fedora thread mentioning 
something similar: 
https://www.reddit.com/r/Fedora/comments/7m9m4h/youtube_videos_are_transparent_kind_of_in_firefox/

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: firefox 64.0+build3-0ubuntu1
ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
Uname: Linux 4.19.0-9-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jani   1748 F pulseaudio
BuildID: 20181207223303
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 16 15:30:58 2018
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2018-09-30 (76 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930)
IpRoute:
 default via 10.0.2.2 dev enp0s3 proto dhcp metric 100
 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100
 169.254.0.0/16 dev enp0s3 scope link metric 1000
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=64.0/20181207223303
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-bug disco

** Attachment added: "Untouched screenshot of top window revealing content from 
another window below"
   
https://bugs.launchpad.net/bugs/1808690/+attachment/5222682/+files/Kuvakaappaus%20-%202018-12-16%2015-05-24.png

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

Title:
  Page content slightly transparent, reveals content from another window
  below

Status in firefox package in Ubuntu:
  New

Bug description:
  Under some circumstances, content from one Firefox window hidden
  behind another leaks onto the top one. Reproducible in both Bionic
  (with Intel graphics) and Disco (in a VirtualBox VM), reporting this
  from Disco.

  == Steps to reproduce ==
  1. Open one Firefox window, drag it to the right side of screen to fill the 
right half, and navigate to https://www.twitch.tv/rifftrax
  2. Open another Firefox window, maximize it on top of the first one, and use 
this topmost window to open https://www.youtube.com/watch?v=P5dxd-ocaE8 and 
expand the Youtube view to 'theatre' mode

  == What happens ==
  White parts of content in Firefox window #1 cast a spectral shadow on the 
black parts of content in Firefox window #2. It's quite subtle, but luckily can 
be caught in screenshots: see attachments below. Pausing the Youtube video 
seems to make the effect to go away (the transparency

[Desktop-packages] [Bug 1803534] Re: Backport uuid based cache file naming scheme

2018-12-04 Thread Jani Uusitalo

I've hit an issue, which I believe I've now isolated to have come from
upgrading fontconfig (and related packages) from 2.12.6-0ubuntu2 to
2.12.6-0ubuntu2.3 from -proposed: if I start Firefox and afterwards
start Gparted or Synaptic, Firefox starts eating up all of my CPU.
Eventually all letters in the Gparted/Synaptic UI turn into boxes.

Syslog typically then says something like below:

Dec  4 13:41:50 saegusa synaptic.desktop[30027]: (synaptic:30028): 
Pango-WARNING **: 13:41:50.995: failed to create cairo scaled font, expect ugly 
output. the offending font is 'DejaVu Sans 11'
Dec  4 13:41:50 saegusa synaptic.desktop[30027]: (synaptic:30028): 
Pango-WARNING **: 13:41:50.995: font_face status is: out of memory
Dec  4 13:41:50 saegusa synaptic.desktop[30027]: (synaptic:30028): 
Pango-WARNING **: 13:41:50.995: scaled_font status is: out of memory
Dec  4 13:41:50 saegusa synaptic.desktop[30027]: (synaptic:30028): 
Pango-WARNING **: 13:41:50.995: shaping failure, expect ugly output. 
shape-engine='PangoFcShapeEngine', font='DejaVu Sans 11', text='Päivitä'
Dec  4 13:41:51 saegusa synaptic.desktop[30027]: (synaptic:30028): 
Pango-WARNING **: 13:41:51.007: failed to create cairo scaled font, expect ugly 
output. the offending font is 'DejaVu Sans 11'
Dec  4 13:41:51 saegusa synaptic.desktop[30027]: (synaptic:30028): 
Pango-WARNING **: 13:41:51.007: font_face status is: out of memory
Dec  4 13:41:51 saegusa synaptic.desktop[30027]: (synaptic:30028): 
Pango-WARNING **: 13:41:51.007: scaled_font status is: out of memory

The computer has 32 GB of memory and there's plenty still usable when
this occurs, so the OOM seems incorrect to me.

To be sure, I rolled back entirely from -proposed (which caused the
issue to go away), then re-enabled -proposed and upgraded just
fontconfig, and the issue reappeared.

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

Title:
  Backport uuid based cache file naming scheme

Status in fontconfig package in Ubuntu:
  New
Status in fontconfig source package in Bionic:
  Fix Committed

Bug description:
  Fontconfig 2.13.0 changed the cache file naming scheme to be based on
  the contents of ".uuid" file in the directory rather than a hash of
  the directory name.  On a pure debs system this doesn't really matter
  since everything is using the same libfontconfig.so.

  When snaps are involved, it can lead to some apps not seeing the cache
  files produced by a different fontconfig version.  In particular,
  while libfontconfig 2.13 can reuse 2.12's cache files for read only
  directories, the reverse is not true.  This will be a problem for apps
  built on top of the "core18" base snap when run on later Ubuntu
  releases (cosmic, disco, etc).

  By providing a backport of the UUID cache file feature to bionic for
  use by snap applications, we'd avoid this.  Having it in bionic-
  updates would be ideal so that snapcraft picks it up automatically.

  [Impact]

   * This update changes how fontconfig cache files are named, instead
  of using md5($dir), it instead uses the contents of a $dir/.uuid file.
  No changes are made to the format of the cache file contents.

   * This change is primarily intended for use by snap applications
  built with core18: as the updated libfontconfig will fall back to the
  md5 cache file names for read-only directories without a .uuid file,
  they will be able to reuse cache files from any host system running
  fontconfig >= 2.11.95

  [Test Case]

   * After installing the update, cache files should be generated in
  /var/cache/fontconfig/ with names like "07b67f7a-16ea-4440-9b6c-
  21fc9153568c-le64.cache-7" (note the extra dashes not present in the
  MD5 based cache file names).

  [Regression Potential]

   * Applications using a non-default libfontconfig could end up not
  finding the new cache files and regenerating them in
  ~/.cache/fontconfig.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+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 1798103] Re: Text highlight mismatch in view-source when layout.css.devPixelsPerPx is >= 1.2

2018-11-17 Thread Jani Uusitalo

Thanks Olivier, I've now added the link to my upstream report.

** Bug watch added: Mozilla Bugzilla #1508043
   https://bugzilla.mozilla.org/show_bug.cgi?id=1508043

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1508043
   Importance: Unknown
   Status: Unknown

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

Title:
  Text highlight mismatch in view-source when layout.css.devPixelsPerPx
  is >= 1.2

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

Bug description:
  == The issue ==
  Search and text selection highlighting visuals get mismatched with the actual 
selection in view-source when the value of `layout.css.devPixelsPerPx` is 1.2 
or larger.

  == Steps to reproduce ==
  * Open `about:config`, find `layout.css.devPixelsPerPx` and change the value 
from default (-1.0) to 1.2.
  * Open a view-source view with long lines: 
`view-source:https://www.youtube.com/user/10asti10`
  * hit Ctrl+f, search for rss
  * using the LMB, try selecting some text, then copy and paste it somewhere

  == What happens ==
  Screenshot 1: the highlighted text on the page is not ”rss”. The highlight 
doesn’t even adhere to letter widths.

  Screenshot 2: the pasted text is not even close to what you’ve
  selected to copy.

  == What I expect to happen ==
  For the search to hightlight an occurence of ”rss”, and for the pasted text 
to correspond to what I’ve selected from the view-source view.

  == Other info ==
  * In my testing, a devPixelsPerPx value of 1.1 seems to not trigger this, 
whereas 1.2 and anything above does.
  * In addition to 18.04 (whence the attached info is from) I’ve reproduced 
this in a VM running up-to-date 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 62.0.3+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BuildID: 20181002130007
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 16:59:28 2018
  InstallationDate: Installed on 2016-10-13 (733 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1798103/+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 1793861] Re: libreoffice crashes when libvclplug_gtk3lo is installed

2018-11-05 Thread Jani Uusitalo

LO 1:6.0.6-0ubuntu0.18.04.1 in Bionic is likewise affected, and the
workaround also works here.

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

Title:
  libreoffice crashes when libvclplug_gtk3lo is installed

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  running on ubuntu cosmic with proposed packages.
  uninstalling libreoffice-gtk3 is a workaround.
  here is a stackdump, hope it helps...

  130 NETZAGENTUR\josef@joebook ~ % loffice --norestore 

:(
  Application Error

  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3cfb3)[0x7f9c5c1b7fb3]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d1c3)[0x7f9c5c1b81c3]
  /lib/x86_64-linux-gnu/libc.so.6(+0x41100)[0x7f9c5bf9d100]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f9c5bf9d077]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f9c5bf7e535]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x11ec2fa)[0x7f9c5d3c42fa]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0x90)[0x7f9c5f00c630]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1efaa17)[0x7f9c5e0d2a17]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2e39beb)[0x7f9c5f011beb]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x17202)[0x7f9c5c192202]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d08f)[0x7f9c5c1b808f]
  /lib/x86_64-linux-gnu/libc.so.6(+0x41100)[0x7f9c5bf9d100]
  /lib/x86_64-linux-gnu/libc.so.6(+0x183f11)[0x7f9c5c0dff11]
  
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7f9c5ad645a4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2eb3fef)[0x7f9c5f08bfef]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9996)[0x7f9c5ad59996]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9ba8)[0x7f9c5ad59ba8]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f203)[0x7f9c5ad1f203]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8fad6)[0x7f9c5ad1fad6]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc1812)[0x7f9c5ad51812]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f203)[0x7f9c5ad1f203]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f239)[0x7f9c5ad1f239]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7f9c5ab6cae8]
  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4ded8)[0x7f9c5ab6ced8]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f9c5ab6cf6c]
  /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x89923)[0x7f9c4fc4a923]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7f9c5f00cb0e]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7f9c5f00e285]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1f00376)[0x7f9c5e0d8376]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2e3b376)[0x7f9c5f013376]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f9c5f013470]
  /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x91)[0x7f9c5e0f4a21]
  /usr/lib/libreoffice/program/soffice.bin(+0x107b)[0x55b8274e107b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f9c5bf8009b]
  /usr/lib/libreoffice/program/soffice.bin(+0x10ba)[0x55b8274e10ba]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-gtk3 1:6.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Sep 22 09:40:07 2018
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1793861/+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 1778422] Re: evince responds to mouse location when it does not have focus. Scrolls wildly up or down.

2018-11-03 Thread Jani Uusitalo

This happens in 18.04 too. Bug #1650076 does also, and I'm not 100 %
sure if these are two different issues or the same. I was able to
reproduce #1650076 with the steps listed there, but just before that I
had Evince following my scroll wheel despite being unfocussed, and I had
not selected anything in the PDF before that (at least not knowingly). I
haven't found the steps to reproduce this without the selection though.

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

Title:
  evince responds to mouse location when it does not have focus. Scrolls
  wildly up or down.

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Evince sometimes gets into a state when it scrolls all the way up or
  all the way down in a document, based on where the mouse cursor is,
  even though evince does not have the focus, and any of the other
  windows is actively receiving input / etc, ie obviously has focus.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-45.50-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 24 11:57:21 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (218 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1778422/+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 1798103] Re: Text highlight mismatch in view-source when layout.css.devPixelsPerPx is >= 1.2

2018-10-16 Thread Jani Uusitalo

** Attachment added: "pasted text is not even close to what you've selected to 
copy"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798103/+attachment/5201768/+files/screenshot-2.png

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

Title:
  Text highlight mismatch in view-source when layout.css.devPixelsPerPx
  is >= 1.2

Status in firefox package in Ubuntu:
  New

Bug description:
  == The issue ==
  Search and text selection highlighting visuals get mismatched with the actual 
selection in view-source when the value of `layout.css.devPixelsPerPx` is 1.2 
or larger.

  == Steps to reproduce ==
  * Open `about:config`, find `layout.css.devPixelsPerPx` and change the value 
from default (-1.0) to 1.2.
  * Open a view-source view with long lines: 
`view-source:https://www.youtube.com/user/10asti10`
  * hit Ctrl+f, search for rss
  * using the LMB, try selecting some text, then copy and paste it somewhere

  == What happens ==
  Screenshot 1: the highlighted text on the page is not ”rss”. The highlight 
doesn’t even adhere to letter widths.

  Screenshot 2: the pasted text is not even close to what you’ve
  selected to copy.

  == What I expect to happen ==
  For the search to hightlight an occurence of ”rss”, and for the pasted text 
to correspond to what I’ve selected from the view-source view.

  == Other info ==
  * In my testing, a devPixelsPerPx value of 1.1 seems to not trigger this, 
whereas 1.2 and anything above does.
  * In addition to 18.04 (whence the attached info is from) I’ve reproduced 
this in a VM running up-to-date 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 62.0.3+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BuildID: 20181002130007
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 16:59:28 2018
  InstallationDate: Installed on 2016-10-13 (733 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798103/+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 1798103] [NEW] Text highlight mismatch in view-source when layout.css.devPixelsPerPx is >= 1.2

2018-10-16 Thread Jani Uusitalo

Public bug reported:

== The issue ==
Search and text selection highlighting visuals get mismatched with the actual 
selection in view-source when the value of `layout.css.devPixelsPerPx` is 1.2 
or larger.

== Steps to reproduce ==
* Open `about:config`, find `layout.css.devPixelsPerPx` and change the value 
from default (-1.0) to 1.2.
* Open a view-source view with long lines: 
`view-source:https://www.youtube.com/user/10asti10`
* hit Ctrl+f, search for rss
* using the LMB, try selecting some text, then copy and paste it somewhere

== What happens ==
Screenshot 1: the highlighted text on the page is not ”rss”. The highlight 
doesn’t even adhere to letter widths.

Screenshot 2: the pasted text is not even close to what you’ve selected
to copy.

== What I expect to happen ==
For the search to hightlight an occurence of ”rss”, and for the pasted text to 
correspond to what I’ve selected from the view-source view.

== Other info ==
* In my testing, a devPixelsPerPx value of 1.1 seems to not trigger this, 
whereas 1.2 and anything above does.
* In addition to 18.04 (whence the attached info is from) I’ve reproduced this 
in a VM running up-to-date 18.10.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 62.0.3+build1-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BuildID: 20181002130007
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 16 16:59:28 2018
InstallationDate: Installed on 2016-10-13 (733 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "highlighted text on the page is not ”rss”"
   
https://bugs.launchpad.net/bugs/1798103/+attachment/5201764/+files/screenshot-1.png

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

Title:
  Text highlight mismatch in view-source when layout.css.devPixelsPerPx
  is >= 1.2

Status in firefox package in Ubuntu:
  New

Bug description:
  == The issue ==
  Search and text selection highlighting visuals get mismatched with the actual 
selection in view-source when the value of `layout.css.devPixelsPerPx` is 1.2 
or larger.

  == Steps to reproduce ==
  * Open `about:config`, find `layout.css.devPixelsPerPx` and change the value 
from default (-1.0) to 1.2.
  * Open a view-source view with long lines: 
`view-source:https://www.youtube.com/user/10asti10`
  * hit Ctrl+f, search for rss
  * using the LMB, try selecting some text, then copy and paste it somewhere

  == What happens ==
  Screenshot 1: the highlighted text on the page is not ”rss”. The highlight 
doesn’t even adhere to letter widths.

  Screenshot 2: the pasted text is not even close to what you’ve
  selected to copy.

  == What I expect to happen ==
  For the search to hightlight an occurence of ”rss”, and for the pasted text 
to correspond to what I’ve selected from the view-source view.

  == Other info ==
  * In my testing, a devPixelsPerPx value of 1.1 seems to not trigger this, 
whereas 1.2 and anything above does.
  * In addition to 18.04 (whence the attached info is from) I’ve reproduced 
this in a VM running up-to-date 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 62.0.3+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BuildID: 20181002130007
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 16:59:28 2018
  InstallationDate: Installed on 2016-10-13 (733 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798103/+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 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu

2018-09-08 Thread Jani Uusitalo

All right. Thanks, Jeremy!

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

Title:
  "New Tab" disappeared from the GNOME Terminal menu

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in gnome-terminal source package in Bionic:
  Fix Released

Bug description:
  Impact
  --
  GNOME Terminal removed the New Tab menu option before Ubuntu 16.04 LTS. Tabs 
are a really popular feature in terminals and it's annoying to have this 
feature hidden.

  Test Case
  -
  Install the update.
  Close all terminals.
  Open a terminal.
  In the File menu should be New Tab and New Window menu items. Both should 
work.

  Regression Potential
  
  Restoring the previous behavior is now a one-line hidden configure option.

  Enabling that option removes the "Open new terminals in" option
  mentioned in the workaround.

  This build option is set in Fedora (and other distros that use the
  Fedora tweaks) and is not believed to have any negative consequences.

  Other Info
  --
  There are no plans at this time to try to backport this change to Ubuntu 
16.04 LTS or 17.10 because it would not be a simple one-line change there. (The 
configure flag was enabled in git commit 0820b385 .)

  https://debarshiray.wordpress.com/2018/05/11/gnome-terminal-separate-
  menu-items-for-opening-tabs-and-windows/

  Workaround
  --
  In Edit > Preferences (General) you can set "Open new terminals in Tab". Now, 
the File > New Window menu item opens a new tab instead of a new window.

  Original Bug Report
  ---
  There is not a "New Tab" option in the file menu of GNOME Terminal anymore on 
Ubuntu Bionic. It looks like it disappeared after some recent update. However, 
the CTRL + Shift + T shortcut works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1747171/+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 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu

2018-09-07 Thread Jani Uusitalo

Okay, did it! https://gitlab.gnome.org/GNOME/gnome-terminal/issues/30

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

Title:
  "New Tab" disappeared from the GNOME Terminal menu

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in gnome-terminal source package in Bionic:
  Fix Released

Bug description:
  Impact
  --
  GNOME Terminal removed the New Tab menu option before Ubuntu 16.04 LTS. Tabs 
are a really popular feature in terminals and it's annoying to have this 
feature hidden.

  Test Case
  -
  Install the update.
  Close all terminals.
  Open a terminal.
  In the File menu should be New Tab and New Window menu items. Both should 
work.

  Regression Potential
  
  Restoring the previous behavior is now a one-line hidden configure option.

  Enabling that option removes the "Open new terminals in" option
  mentioned in the workaround.

  This build option is set in Fedora (and other distros that use the
  Fedora tweaks) and is not believed to have any negative consequences.

  Other Info
  --
  There are no plans at this time to try to backport this change to Ubuntu 
16.04 LTS or 17.10 because it would not be a simple one-line change there. (The 
configure flag was enabled in git commit 0820b385 .)

  https://debarshiray.wordpress.com/2018/05/11/gnome-terminal-separate-
  menu-items-for-opening-tabs-and-windows/

  Workaround
  --
  In Edit > Preferences (General) you can set "Open new terminals in Tab". Now, 
the File > New Window menu item opens a new tab instead of a new window.

  Original Bug Report
  ---
  There is not a "New Tab" option in the file menu of GNOME Terminal anymore on 
Ubuntu Bionic. It looks like it disappeared after some recent update. However, 
the CTRL + Shift + T shortcut works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1747171/+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 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu

2018-09-07 Thread Jani Uusitalo

Jeremy: If this is indeed the popular choice then I fully respect that.
I just wanted to voice my disgruntlement, since I feel the way this was
set by upstream is much simpler. Sorry for being late with it, didn't
realize this was getting overridden before the change already came into
effect.

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

Title:
  "New Tab" disappeared from the GNOME Terminal menu

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in gnome-terminal source package in Bionic:
  Fix Released

Bug description:
  Impact
  --
  GNOME Terminal removed the New Tab menu option before Ubuntu 16.04 LTS. Tabs 
are a really popular feature in terminals and it's annoying to have this 
feature hidden.

  Test Case
  -
  Install the update.
  Close all terminals.
  Open a terminal.
  In the File menu should be New Tab and New Window menu items. Both should 
work.

  Regression Potential
  
  Restoring the previous behavior is now a one-line hidden configure option.

  Enabling that option removes the "Open new terminals in" option
  mentioned in the workaround.

  This build option is set in Fedora (and other distros that use the
  Fedora tweaks) and is not believed to have any negative consequences.

  Other Info
  --
  There are no plans at this time to try to backport this change to Ubuntu 
16.04 LTS or 17.10 because it would not be a simple one-line change there. (The 
configure flag was enabled in git commit 0820b385 .)

  https://debarshiray.wordpress.com/2018/05/11/gnome-terminal-separate-
  menu-items-for-opening-tabs-and-windows/

  Workaround
  --
  In Edit > Preferences (General) you can set "Open new terminals in Tab". Now, 
the File > New Window menu item opens a new tab instead of a new window.

  Original Bug Report
  ---
  There is not a "New Tab" option in the file menu of GNOME Terminal anymore on 
Ubuntu Bionic. It looks like it disappeared after some recent update. However, 
the CTRL + Shift + T shortcut works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1747171/+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 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu

2018-05-26 Thread Jani Uusitalo

Urgh, I'd argue that changing this back *is* a regression. The merged
menu item has been the default since (at least) 16.04, and now the
cognitive load of opening a new tab has suddenly increased: instead of
"new terminal" I now again have to pick the one I want (which is always
tabs for me) from two options each time, instead of just the one.

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

Title:
  "New Tab" disappeared from the GNOME Terminal menu

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in gnome-terminal source package in Bionic:
  Fix Released

Bug description:
  Impact
  --
  GNOME Terminal removed the New Tab menu option before Ubuntu 16.04 LTS. Tabs 
are a really popular feature in terminals and it's annoying to have this 
feature hidden.

  Test Case
  -
  Install the update.
  Close all terminals.
  Open a terminal.
  In the File menu should be New Tab and New Window menu items. Both should 
work.

  Regression Potential
  
  Restoring the previous behavior is now a one-line hidden configure option.

  Enabling that option removes the "Open new terminals in" option
  mentioned in the workaround.

  This build option is set in Fedora (and other distros that use the
  Fedora tweaks) and is not believed to have any negative consequences.

  Other Info
  --
  There are no plans at this time to try to backport this change to Ubuntu 
16.04 LTS or 17.10 because it would not be a simple one-line change there. (The 
configure flag was enabled in git commit 0820b385 .)

  https://debarshiray.wordpress.com/2018/05/11/gnome-terminal-separate-
  menu-items-for-opening-tabs-and-windows/

  Workaround
  --
  In Edit > Preferences (General) you can set "Open new terminals in Tab". Now, 
the File > New Window menu item opens a new tab instead of a new window.

  Original Bug Report
  ---
  There is not a "New Tab" option in the file menu of GNOME Terminal anymore on 
Ubuntu Bionic. It looks like it disappeared after some recent update. However, 
the CTRL + Shift + T shortcut works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1747171/+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 1767806] Re: Position of left-tiled windows not restored correctly when another left-tiled window present

2018-05-18 Thread Jani Uusitalo

Thanks, I've now reported this at: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/287

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

Title:
  Position of left-tiled windows not restored correctly when another
  left-tiled window present

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When another window is maximized or tiled to the left side of the
  screen, re-opening an application whose window was previously tiled to
  the left side does not restore that windows' previous position.
  Instead such windows open at varying distances from the dock, untiled.

  
  = Steps to reproduce *expected* behavior (with a newly created user) =

  1. open Firefox, drag the window to the left edge of the screen to tile it 
there (filling up the left half of horizontal screen space)
  2. close Firefox
  3. open Nautilus, make sure that the window floats (i.e. is unmaximized and 
not tiled to either side of screen)
  4. open Firefox

  == What happens ==
  As expected, Firefox's window is tiled to the left edge of screen, 
immediately to the right side of the dock.

  
  = Steps to reproduce *unexpected* behavior (with a newly created user) =
  1. open Firefox, drag the window to the left edge of the screen to tile it 
there (filling up the left half of horizontal screen space)
  2. close Firefox
  3. open Nautilus, *maximize its window*
  4. open Firefox

  == What happens ==
  Firefox's window opens slightly to the right off the right edge of the dock 
(with a gap between the dock and the window).
  == What I expect to happen ==
  I expect Firefox's window to be tiled to the left edge of screen, immediately 
to the right side of the dock, just as it did following the first recipe above.

  
  = Further information =
  Either maximizing or tiling Nautilus' window to the left edge of the screen 
(at step #3) triggers the issue. Tiling it to the *right* edge of the screen 
does not.

  Using Gnome Terminal instead of Nautilus triggers the issue just as
  well, I suspect any other application will though I've only
  systematically tested these two so far.

  From battling with this in my daily use I also know that the distance
  of incorrectly restored windows from the dock varies: different
  applications open at different distances. The precise mechanics of
  this still elude me, though the distances do appear to be multiples of
  25 pixels.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 29 16:32:37 2018
  InstallationDate: Installed on 2016-10-13 (562 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767806/+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 1747891] Re: gsd-color[1032]: failed to set screen _ICC_PROFILE

2018-05-15 Thread Jani Uusitalo

** Bug watch added: GNOME Bug Tracker #749338
   https://bugzilla.gnome.org/show_bug.cgi?id=749338

** Also affects: gnome-settings-daemon via
   https://bugzilla.gnome.org/show_bug.cgi?id=749338
   Importance: Unknown
   Status: Unknown

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

Title:
  gsd-color[1032]: failed to set screen _ICC_PROFILE

Status in GNOME Settings Daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged:

  gsd-color[1032]: failed to set screen _ICC_PROFILE: Failed to open
  file “/home/oem/.local/share/icc/edid-
  3ed66b5b66c8e176b2d44c8563cdad28.icc”: Permission denied

  
  This is related to (colormgr get-profiles output):

  Filename:  
/var/lib/gdm3/.local/share/icc/edid-3ed66b5b66c8e176b2d44c8563cdad28.icc
  Profile ID:icc-b11214f828f359ffc2d54bd918e8de7b
  Metadata:  CMF_version=3.26.2
  Metadata:  EDID_serial=SN-1
  Metadata:  CMF_binary=gnome-settings-daemon
  Metadata:  EDID_md5=3ed66b5b66c8e176b2d44c8563cdad28
  Metadata:  CMF_product=gnome-settings-daemon
  Metadata:  EDID_mnft=MTC
  Metadata:  FILE_checksum=b11214f828f359ffc2d54bd918e8de7b
  Metadata:  EDID_model=MON-SIS289
  Metadata:  DATA_source=edid
  Metadata:  MAPPING_device_id=xrandr-Mars-Tech 
Corporation-MON-SIS289-SN-1
  Metadata:  EDID_manufacturer=Mars-Tech Corporation

  Actual rights (set by the default install):

  oem@ubuntu:~$ ls -l /home/oem/.local/share/icc/
  -rw-rw-r-- 1 oem oem 1552 Dec  1 20:22 
edid-3ed66b5b66c8e176b2d44c8563cdad28.icc

  I've tried to follow that howto; but it should be set out of the box:
  
https://askubuntu.com/questions/199661/how-do-you-set-system-display-color-profiles-in-xubuntu-and-lubuntu

  note: if that apply to an other package than gsd, please do change/add

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Feb  7 12:11:12 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1747891/+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 1764417] [NEW] Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

2018-04-16 Thread Jani Uusitalo

Public bug reported:

I've had this happen a couple of times now since upgrading to 18.04:
soon (perhaps within a minute) after logging in, Gnome session ends
abruptly and I'm thrown back to the login screen. IIRC, in both
instances this occurred on the first login after boot, so it does not
reoccur on the subsequent re-login, and not on every login (very rarely
in fact), and for now I have no better steps to reproduce this other
than "boot, log in".

Bug #1663839 (reported against 17.04) seems similar, as does bug
#1731428 (reported against 17.10).

journalctl output during the issue:

Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Color.desktop
Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but 
the fail whale is dead. Sorry

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-settings-daemon 3.28.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 16 17:07:14 2018
InstallationDate: Installed on 2016-10-13 (550 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

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

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

Bug description:
  I've had this happen a couple of times now since upgrading to 18.04:
  soon (perhaps within a minute) after logging in, Gnome session ends
  abruptly and I'm thrown back to the login screen. IIRC, in both
  instances this occurred on the first login after boot, so it does not
  reoccur on the subsequent re-login, and not on every login (very
  rarely in fact), and for now I have no better steps to reproduce this
  other than "boot, log in".

  Bug #1663839 (reported against 17.04) seems similar, as does bug
  #1731428 (reported against 17.10).

  journalctl output during the issue:

  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Color.desktop
  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but 
the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 17:07:14 2018
  InstallationDate: Installed on 2016-10-13 (550 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+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 1754284] Re: Totem is tearing when fullscreen in Xorg sessions

2018-04-10 Thread Jani Uusitalo

In addition to Totem, Firefox also exhibits this with fullscreen HTML5
video. Here's a good test: https://www.youtube.com/watch?v=5xkNy9gfKOg

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

Title:
  Totem is tearing when fullscreen in Xorg sessions

Status in mutter package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Totem is tearing when fullscreen in Xorg sessions.

  This is probably to do with composite unredirecting... In compiz we
  have a workaround to avoid this tearing by disallowing unredirect
  ("bypass") in known problematic video players. But I'm not sure if
  mutter has such a workaround/whitelist/blacklist we can use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1754284/+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 1734891] Re: nautilus crashed with SIGSEGV in nautilus_list_model_get_all_iters_for_file()

2018-04-09 Thread Jani Uusitalo

My bug #1762400 got marked as a duplicate for this one, but I don't have
Dropbox installed.

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

Title:
  nautilus crashed with SIGSEGV in
  nautilus_list_model_get_all_iters_for_file()

Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Hello,

  I'm working with nautilus and crash.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.0-0ubuntu1
  Uname: Linux 4.15.0-041500rc1-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 28 11:17:57 2017
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'253'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x547+255+180'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.desktop' b'home-icon-visible' b'true'
  InstallationDate: Installed on 2017-10-13 (45 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x5592953dfc28 
:mov0x10(%rbx),%rsi
   PC (0x5592953dfc28) ok
   source "0x10(%rbx)" (0xffc0) not located in a known VMA region 
(needed readable region)!
   destination "%rsi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   nautilus_list_model_get_all_iters_for_file ()
   nautilus_list_model_get_first_iter_for_file ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in 
nautilus_list_model_get_all_iters_for_file()
  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/1734891/+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 1762400] Re: nautilus crashed with SIGSEGV in nautilus_list_model_get_all_iters_for_file() when trying to open a password-protected 7z archive

2018-04-09 Thread Jani Uusitalo

*** This bug is a duplicate of bug 1734891 ***
https://bugs.launchpad.net/bugs/1734891

Possible duplicates with bug #1607919

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

Title:
  nautilus crashed with SIGSEGV in
  nautilus_list_model_get_all_iters_for_file() when trying to open a
  password-protected 7z archive

Status in nautilus package in Ubuntu:
  New

Bug description:
  == Steps to reproduce ==
  1. Create a password protected 7z archive: `echo hello >hello.txt; 7z a 
hello.7z hello.txt -ppassword`
  2. Left-click the archive in Nautilus

  == What happens ==
  Nautilus shows an empty window, and together with gnome-shell they eat up the 
CPU until you close the Nautilus window. Alternatively, a crash report prompt 
appears.

  == What I expect to happen ==
  Preferably to prompt for a password and then open the archive contents. At 
the very least to not eat all the CPU, and inform the user that Nautilus is 
incapable of handling this file format.

  == Other info ==
  I don't have Dropbox installed unlike in bug #1734891.

  Upstream issue: https://gitlab.gnome.org/GNOME/nautilus/issues/51

  Red Hat issue: https://bugzilla.redhat.com/show_bug.cgi?id=1499401

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 15:02:59 2018
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2016-10-13 (542 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x55785367f8b8 
:mov0x10(%rbx),%rsi
   PC (0x55785367f8b8) ok
   source "0x10(%rbx)" (0xffc0) not located in a known VMA region 
(needed readable region)!
   destination "%rsi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   nautilus_list_model_get_all_iters_for_file ()
   nautilus_list_model_get_first_iter_for_file ()
   ()
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in 
nautilus_list_model_get_all_iters_for_file()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-transmission dip lp lpadmin lxd plugdev 
sambashare ssh sudo vboxusers
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1762400/+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 1733908] Re: In Firefox 57 (Quantum), HTML links' context menu appears in the wrong place

2018-04-01 Thread Jani Uusitalo

Haven't seen this since upgrading to 18.04, and can't reproduce it
following the instructions anymore either, so it appears to be fixed.

** Changed in: firefox (Ubuntu)
   Status: New => Fix Released

** Summary changed:

- In Firefox 57 (Quantum), HTML links' context menu appears in the wrong place
+ HTML links' context menu appears in the wrong place (since Firefox 57 Quantum)

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

Title:
  HTML links' context menu appears in the wrong place (since Firefox 57
  Quantum)

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to Quantum, the right mouse button context menu for
  HTML links pops up in the wrong place when the Firefox window is
  pushed to either side of my screen (so that the window takes up half
  of the horizontal space). The issue appears similar to what has been
  reported in bug #1721614, but for me the issue does not occur with the
  hamburger menu or other UI elements, only with links on webpages, and
  the menu highlighting behavior is different: in my issue the
  highlighting occurs normally only once I point the cursor at the menu.

  == Steps to reproduce ==
  1. Create a new profile and start Firefox using the profile.
  2. Expand the window to fill the screen (if not already).
  3. Enter search terms into the URL bar and hit enter to bring up a search 
results page.
  4. Right-click a search result title to bring up the context menu. Left-click 
outside it to close it.
  5. Grab the window title bar and push the window to the right edge of screen 
to resize the window to span half of screen horizontally. Release the title bar.
  4. Right click the search result title again.

  == What happens ==
  The menu pops up on way off from where the mouse cursor is. See attached 
screenshot.

  == What should happen ==
  The context menu should pop up next to mouse cursor.

  == Possible culprit ==
  This seems to be somehow tied to localization: if I uninstall 
firefox-locale-*, then create a new Firefox profile, with this new profile the 
menu pops up where it should. I'm using Finnish locale, but this is 
reproducible with just firefox-local-en too, although the mispositioning 
differs between locales (Finnish pushes the menu off to the left, whereas 
English pushes it down and to the right).

  == Workaround ==
  Don't right-click on the page before resizing the window (that is, skip step 
#4 above). This seems to be the trigger.

  == Other info ==
  I'm able reproduce this in a (16.04) VM just as well as on the host desktop.

  In case the collected data doesn't include this, my primary display is
  2560 × 1440p, and the only display connected. xrandr output:

  Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
  VGA-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1 disconnected (normal left inverted right x axis y axis)
  DP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 527mm x 296mm
     2560x1440 59.95*+
     2048x1152 59.90
     1920x1200 59.88
     1920x1080 60.0050.0059.9424.0023.98
     1920x1080i60.0050.0059.94
     1600x1200 60.00
     1680x1050 59.95
     1280x1024 75.0260.02
     1280x800  59.81
     1152x864  75.00
     1280x720  60.0050.0059.94
     1024x768  75.0360.00
     800x600   75.0060.32
     720x576   50.00
     720x480   60.0059.94
     640x480   75.0060.0059.94
     720x400   70.08
  HDMI-2 disconnected (normal left inverted right x axis y axis)
  HDMI-3 disconnected (normal left inverted right x axis y axis)
  DP-2 disconnected (normal left inverted right x axis y axis)
  DP-3 disconnected (normal left inverted right x axis y axis)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 57.0+build4-0ubuntu0.16.04.5
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  BuildID: 20171115095126
  CurrentDesktop: Unity
  Date: Wed Nov 22 18:35:05 2017
  InstallationDate: Installed on 2016-10-13 (405 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1733908/+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 1664054] Re: issues when saving image (different from #1064332)

2018-03-31 Thread Jani Uusitalo

This is currently still present in Bionic's Shotwell 0.28.1-0ubuntu1.

** Also affects: shotwell via
   https://bugzilla.gnome.org/show_bug.cgi?id=738486
   Importance: Unknown
   Status: Unknown

** Summary changed:

- issues when saving image (different from #1064332)
+ After saving image, Shotwell still thinks image is unsaved

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

Title:
  After saving image, Shotwell still thinks image is unsaved

Status in Shotwell:
  Unknown
Status in shotwell package in Ubuntu:
  Confirmed

Bug description:
  Shotwell 0.20.2, Ubuntu 14.04, Mate desktop environment 1.8.2

  
  When trying to save a modified image, the following happens:

  1) ctrl-S does not work (and is dimmed) -- only non-shortcut File >
  Save works

  2) the new version of the image is actually saved on the hard drive
  (file manager shows new dates and time, and if the image is opened in
  another image viewer, the changes are there)

  3) but shotwell itself sees the image as unsaved (with a star on the
  left side of the file name in the window banner) and will ask twice if
  you want to save it when you close the window.

  
  Unlike bug #1064332, no freezing happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/shotwell/+bug/1664054/+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 1760056] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()

2018-03-30 Thread Jani Uusitalo

*** This bug is a duplicate of bug 1724439 ***
https://bugs.launchpad.net/bugs/1724439

** Description changed:

  Had been AFK for a couple of hours with the display turned off, came
  back and turned it on when this occurred.
  
- I've redirected Gnome shell related log etries away from my syslog so
+ I've redirected Gnome Shell related log entries away from my syslog so
  I'm attaching the separate log here.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 30 12:02:25 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-10-13 (532 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
-  PATH=(custom, user)
-  XDG_RUNTIME_DIR=
-  LANG=fi_FI.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, user)
+  XDG_RUNTIME_DIR=
+  LANG=fi_FI.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0x7ff6e1385c24 :mov
0x18(%rax),%eax
-  PC (0x7ff6e1385c24) ok
-  source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
-  destination "%eax" ok
+  Segfault happened at: 0x7ff6e1385c24 :mov
0x18(%rax),%eax
+  PC (0x7ff6e1385c24) ok
+  source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
+  destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  meta_window_get_monitor () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
-  ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
-  ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
-  () at /usr/lib/libgjs.so.0
-  () at /usr/lib/libgjs.so.0
+  meta_window_get_monitor () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
+  ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
+  ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
+  () at /usr/lib/libgjs.so.0
+  () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-transmission dip lp lpadmin lxd plugdev 
sambashare ssh sudo vboxusers

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_monitor()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Had been AFK for a couple of hours with the display turned off, came
  back and turned it on when this occurred.

  I've redirected Gnome Shell related log entries away from my syslog so
  I'm attaching the separate log here.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 30 12:02:25 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-10-13 (532 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff6e1385c24 :mov
0x18(%rax),%eax
   PC (0x7ff6e1385c24) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_monitor () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-transmission dip lp lpadmin lxd plugdev 
sambashare ssh sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760056/+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 1742443] Re: Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot

2018-03-23 Thread Jani Uusitalo

Looks like you can still enter 'Print' in dconf-editor for a custom
action (/org/gnome/settings-daemon/plugins/media-keys/custom-
keybindings/customN/binding), so at least there's that.

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

Title:
  Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04
  gnome-screenshot v 3.25.0-0ubuntu2 (amd64)

  Using the PrtSc button, alone or in combination with shift, alt or
  ctrl, doesn't trigger the gnome-screenshot window that asks to save
  the image.

  The screen blinks (so the button is intercepted) but no window is
  triggered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1742443/+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 1742443] Re: Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot

2018-03-23 Thread Jani Uusitalo

It seems that PrintScreen is now bound to Gnome Settings Daemon, which
is used to take screenshots instead of gnome-screenshot. Keyboard
settings (in Gnome settings) still has a screenshot shortcuts section in
the keyboard shortcut settings, but those too now only trigger Gnome
Settings Daemon's screenshot feature, not gnome-screenshot.

What's worse, disabling those shortcuts does not allow for remapping
PrintScreen back to gnome-screenshot using a custom shortcut, as
pressing PrintScreen in the shortcut selector window still just triggers
the GSD 'blink' instead of registering PrintScreen as the new shortcut
key for the custom command. Only the screenshot section's pre-defined
actions allow for PrintScreen to be grabbed. (At least that's what it
does here.)

When the screenshot shortcuts are disabled, nothing is apparently saved
anywhere despite the blink effect. The "Save a screenshot to Pictures"
shortcut has to be defined for the screenshots to actually get saved,
and then they will be unconditionally saved to $XDG_PICTURES_DIR:
https://bugzilla.gnome.org/show_bug.cgi?id=699642


** Bug watch added: GNOME Bug Tracker #699642
   https://bugzilla.gnome.org/show_bug.cgi?id=699642

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

Title:
  Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04
  gnome-screenshot v 3.25.0-0ubuntu2 (amd64)

  Using the PrtSc button, alone or in combination with shift, alt or
  ctrl, doesn't trigger the gnome-screenshot window that asks to save
  the image.

  The screen blinks (so the button is intercepted) but no window is
  triggered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1742443/+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 1710641] Re: Viewer fails to save a JPEG with non-JPEG filename extension

2018-03-09 Thread Jani Uusitalo

** Bug watch added: GNOME Bug Tracker #794195
https://bugzilla.gnome.org/show_bug.cgi?id=794195

** Also affects: shotwell via
https://bugzilla.gnome.org/show_bug.cgi?id=794195
Importance: Unknown
Status: Unknown

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

Title:
Viewer fails to save a JPEG with non-JPEG filename extension

Status in Shotwell:
Unknown
Status in shotwell package in Ubuntu:
New

Bug description:
== Steps to reproduce ==
1. Download
https://upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Car_crash_1.jpg/193px-Car_crash_1.jpg?download
2. Open the image in Shotwell Viewer: $ shotwell 193px-Car_crash_1.jpg
3. Select File > Save As...
4. Select OK (without changing Format from "Current", or any other parameters)
5. Enter "193px-Car_crash_1.png" (without quotes) as the filename, select OK

== What happens ==
The viewer now displays a black screen, with the text "Photo source file
missing:" followed by the (.png-ending) image path entered in the dialog. The
file has not been saved.

== What I expect to happen ==
For the (now misnamed) .png-ending file to have been saved, and be opened in
the Viewer.

== Other notes ==
* If a file with the .png ending already exists, and I try overwriting it
with the JPEG, the black error screen does not appear, and the viewer appears
as if it had saved the file. But the file hasn't actually been saved; if
193px-Car_crash_1.png was an empty file before seemingly overwriting it, it
remains empty.
* I'm (intentionally) not doing an actual Format change in the first Save As
dialog here. If I do select PNG as the format, then saving the file does work
as expected (using any filename extension).
* I used .png just as an example here. Any variant of /jpe?g/i as the
extension seems to work as expected, whereas anything else (.gif, .foo etc.)
results in the same "file missing" error as above.
* If the original file is a PNG file, saving it with .jpg (or any other
extension for that matter) seems to work as expected.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Aug 14 17:22:25 2017
InstallationDate: Installed on 2016-10-13 (305 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
SourcePackage: shotwell
UpgradeStatus: No upgrade log present (probably fresh install)

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

[Desktop-packages] [Bug 1733908] [NEW] In Firefox 57 (Quantum), HTML links' context menu appears in the wrong place

2017-11-22 Thread Jani Uusitalo

Public bug reported:

After upgrading to Quantum, the right mouse button context menu for HTML
links pops up in the wrong place when the Firefox window is pushed to
either side of my screen (so that the window takes up half of the
horizontal space). The issue appears similar to what has been reported
in bug #1721614, but for me the issue does not occur with the hamburger
menu or other UI elements, only with links on webpages, and the menu
highlighting behavior is different: in my issue the highlighting occurs
normally only once I point the cursor at the menu.

== Steps to reproduce ==
1. Create a new profile and start Firefox using the profile.
2. Expand the window to fill the screen (if not already).
3. Enter search terms into the URL bar and hit enter to bring up a search 
results page.
4. Right-click a search result title to bring up the context menu. Left-click 
outside it to close it.
5. Grab the window title bar and push the window to the right edge of screen to 
resize the window to span half of screen horizontally. Release the title bar.
4. Right click the search result title again.

== What happens ==
The menu pops up on way off from where the mouse cursor is. See attached 
screenshot.

== What should happen ==
The context menu should pop up next to mouse cursor.

== Possible culprit ==
This seems to be somehow tied to localization: if I uninstall firefox-locale-*, 
then create a new Firefox profile, with this new profile the menu pops up where 
it should. I'm using Finnish locale, but this is reproducible with just 
firefox-local-en too, although the mispositioning differs between locales 
(Finnish pushes the menu off to the left, whereas English pushes it down and to 
the right).

== Workaround ==
Don't right-click on the page before resizing the window (that is, skip step #4 
above). This seems to be the trigger.

== Other info ==
I'm able reproduce this in a (16.04) VM just as well as on the host desktop.

In case the collected data doesn't include this, my primary display is
2560 × 1440p, and the only display connected. xrandr output:

Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 
527mm x 296mm
   2560x1440 59.95*+
   2048x1152 59.90
   1920x1200 59.88
   1920x1080 60.0050.0059.9424.0023.98
   1920x1080i60.0050.0059.94
   1600x1200 60.00
   1680x1050 59.95
   1280x1024 75.0260.02
   1280x800  59.81
   1152x864  75.00
   1280x720  60.0050.0059.94
   1024x768  75.0360.00
   800x600   75.0060.32
   720x576   50.00
   720x480   60.0059.94
   640x480   75.0060.0059.94
   720x400   70.08
HDMI-2 disconnected (normal left inverted right x axis y axis)
HDMI-3 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 57.0+build4-0ubuntu0.16.04.5
ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
BuildID: 20171115095126
CurrentDesktop: Unity
Date: Wed Nov 22 18:35:05 2017
InstallationDate: Installed on 2016-10-13 (405 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "Screenshot with the context menu off to the left of mouse 
cursor (Finnish locale)"
   
https://bugs.launchpad.net/bugs/1733908/+attachment/5012949/+files/Kuvakaappaus%202017-11-22%2018-21-38.png

** Description changed:

  After upgrading to Quantum, the right mouse button context menu for HTML
  links pops up in the wrong place when the Firefox window is pushed to
  either side of my screen (so that the window takes up half of the
  horizontal space). The issue appears similar to what has been reported
- in LP #1721614 (particularly as it appears in the video attached by the
+ in bug #1721614 (particularly as it appears in the video attached by the
  submitter), but for me the issue does not occur with the hamburger menu
  or other UI elements, only with links on webpages.
  
  == Steps to reproduce ==
  1. Create a new profile and start Firefox using the profile.
  2. Expand the window to fill the screen (if not already).
  3. Enter search terms into the URL bar and hit enter to bring up a search 
results page.
  4. Right-click a search result title to bring up the context menu. Left-click 
outside it to close it.
  5. Grab the window title

[Desktop-packages] [Bug 1710641] [NEW] Viewer fails to save a JPEG with non-JPEG filename extension

2017-08-14 Thread Jani Uusitalo

Public bug reported:

== Steps to reproduce ==
1. Download 
https://upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Car_crash_1.jpg/193px-Car_crash_1.jpg?download
2. Open the image in Shotwell Viewer: $ shotwell 193px-Car_crash_1.jpg
3. Select File > Save As...
4. Select OK (without changing Format from "Current", or any other parameters)
5. Enter "193px-Car_crash_1.png" (without quotes) as the filename, select OK

== What happens ==
The viewer now displays a black screen, with the text "Photo source file 
missing:" followed by the (.png-ending) image path entered in the dialog. The 
file has not been saved.

== What I expect to happen ==
For the (now misnamed) .png-ending file to have been saved, and be opened in 
the Viewer.

== Other notes ==
* If a file with the .png ending already exists, and I try overwriting it with 
the JPEG, the black error screen does not appear, and the viewer appears as if 
it had saved the file. But the file hasn't actually been saved; if 
193px-Car_crash_1.png was an empty file before seemingly overwriting it, it 
remains empty.
* I'm (intentionally) not doing an actual Format change in the first Save As 
dialog here. If I do select PNG as the format, then saving the file does work 
as expected (using any filename extension).
* I used .png just as an example here. Any variant of /jpe?g/i as the extension 
seems to work as expected, whereas anything else (.gif, .foo etc.) results in 
the same "file missing" error as above.
* If the original file is a PNG file, saving it with .jpg (or any other 
extension for that matter) seems to work as expected.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Aug 14 17:22:25 2017
InstallationDate: Installed on 2016-10-13 (305 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
SourcePackage: shotwell
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Viewer fails to save a JPEG with non-JPEG filename extension

Status in shotwell package in Ubuntu:
  New

Bug description:
  == Steps to reproduce ==
  1. Download 
https://upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Car_crash_1.jpg/193px-Car_crash_1.jpg?download
  2. Open the image in Shotwell Viewer: $ shotwell 193px-Car_crash_1.jpg
  3. Select File > Save As...
  4. Select OK (without changing Format from "Current", or any other parameters)
  5. Enter "193px-Car_crash_1.png" (without quotes) as the filename, select OK

  == What happens ==
  The viewer now displays a black screen, with the text "Photo source file 
missing:" followed by the (.png-ending) image path entered in the dialog. The 
file has not been saved.

  == What I expect to happen ==
  For the (now misnamed) .png-ending file to have been saved, and be opened in 
the Viewer.

  == Other notes ==
  * If a file with the .png ending already exists, and I try overwriting it 
with the JPEG, the black error screen does not appear, and the viewer appears 
as if it had saved the file. But the file hasn't actually been saved; if 
193px-Car_crash_1.png was an empty file before seemingly overwriting it, it 
remains empty.
  * I'm (intentionally) not doing an actual Format change in the first Save As 
dialog here. If I do select PNG as the format, then saving the file does work 
as expected (using any filename extension).
  * I used .png just as an example here. Any variant of /jpe?g/i as the 
extension seems to work as expected, whereas anything else (.gif, .foo etc.) 
results in the same "file missing" error as above.
  * If the original file is a PNG file, saving it with .jpg (or any other 
extension for that matter) seems to work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 14 17:22:25 2017
  InstallationDate: Installed on 2016-10-13 (305 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: shotwell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1693520] [NEW] Interrupting (Ctrl-C) jpegtran causes data loss when -outfile points to input file

2017-05-25 Thread Jani Uusitalo

Public bug reported:

For optimizing files in-place with jpegtran, especially from scripts and
when dealing with lots of pictures, it's handy to be able to specify
input file as -outfile.

But there's a catch:

Steps to reproduce:
0. Have a large JPEG file, or, alternatively, somewhat slow CPU
1. `jpegtran -optimize -copy all -perfect -outfile large.jpg large.jpg`
2. Hit Ctrl-C before the command finishes

Result:
You now have a broken large.jpg with only part, if any, of the image data 
remaining.

What I expect to happen:
To have large.jpg as it was before I invoked jpegtran.

Workarounds:
Obviously the traditional workaround of specifying an intermediate temporary 
output file, then replacing the original with the temporary file only once 
jpegtran has finished.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libjpeg-turbo-progs 1.4.2-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 25 17:16:16 2017
InstallationDate: Installed on 2016-10-13 (224 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
SourcePackage: libjpeg-turbo
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libjpeg-turbo (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 libjpeg-turbo in Ubuntu.
https://bugs.launchpad.net/bugs/1693520

Title:
  Interrupting (Ctrl-C) jpegtran causes data loss when -outfile points
  to input file

Status in libjpeg-turbo package in Ubuntu:
  New

Bug description:
  For optimizing files in-place with jpegtran, especially from scripts
  and when dealing with lots of pictures, it's handy to be able to
  specify input file as -outfile.

  But there's a catch:

  Steps to reproduce:
  0. Have a large JPEG file, or, alternatively, somewhat slow CPU
  1. `jpegtran -optimize -copy all -perfect -outfile large.jpg large.jpg`
  2. Hit Ctrl-C before the command finishes

  Result:
  You now have a broken large.jpg with only part, if any, of the image data 
remaining.

  What I expect to happen:
  To have large.jpg as it was before I invoked jpegtran.

  Workarounds:
  Obviously the traditional workaround of specifying an intermediate temporary 
output file, then replacing the original with the temporary file only once 
jpegtran has finished.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-turbo-progs 1.4.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 25 17:16:16 2017
  InstallationDate: Installed on 2016-10-13 (224 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: libjpeg-turbo
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1693520/+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 899671] Re: Aisleriot Freecell does not report the game number

2017-02-03 Thread Jani Uusitalo

** Bug watch added: GNOME Bug Tracker #409779
   https://bugzilla.gnome.org/show_bug.cgi?id=409779

** Also affects: aisleriot via
   https://bugzilla.gnome.org/show_bug.cgi?id=409779
   Importance: Unknown
   Status: Unknown

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

Title:
  Aisleriot Freecell does not report the game number

Status in Aisleriot:
  Unknown
Status in aisleriot package in Ubuntu:
  Confirmed

Bug description:
  When starting a new Freecell game, Aisleriot does not show the game
  number (the seed value from which the card layout was generated.)

  All other Freecell games on all platforms I've tried do this, so that
  you can record when you lose a game and retry it later, exchange hard
  games with your friends and so on. This includes Win32 Freecell,
  Windows 7 Freecell, the 3rd party Freecell Plus, the Mac OS X Freecell
  by the late Alisdair McDiarmid of http://randomoracle.org/ and so on.

  This is not a bug but a feature request, but I can't find any author
  or any direct contact for the team to report it. This is the only way
  I know, I'm afraid.

  Associated functionality: enter a game number to retry a previous
  game, as opposed to just getting a new random game every time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aisleriot/+bug/899671/+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 1221955] Re: GNOME_KEYRING_RESULT_IO_ERROR from launchpadlib

2017-01-14 Thread Jani Uusitalo

** Bug watch added: Debian Bug tracker #659036
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659036

** Also affects: gnome-keyring (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659036
   Importance: Unknown
   Status: Unknown

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

Title:
  GNOME_KEYRING_RESULT_IO_ERROR from launchpadlib

Status in GNOME Keyring:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Debian:
  Unknown

Bug description:
  I have no reliable way to reproduce it, but every now and then when
  using pull-ppa-source (from lp:kubuntu-dev-tools) the script fails
  with this error: (tokens stripped from output)

  Gkr-Message: received an invalid, unencryptable, or non-utf8 secret
  Gkr-Message: call to daemon returned an invalid response: (null).(null)()
  Gkr-Message: received an invalid, unencryptable, or non-utf8 secret
  Gkr-Message: call to daemon returned an invalid response: (null).(null)()
  The authorization page:
   
(https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INTEGRATION)
  should be opening in your browser. Use your browser to authorize
  this program to access Launchpad on your behalf.
  Press any key to continue or wait (5) seconds...
  Waiting to hear from Launchpad about your decision...
  00:24:38 unnamed app(24933) ClientApp::doIt: Creating ClientApp
  00:24:38 kioclient(24933) ClientApp::kde_open: 
KUrl("https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INTEGRATION")
  00:24:38 kioclient(24933)/kio (KRun) KRun::slotTimeout: KRun(0x269dbe0)  
slotTimeout called
  00:24:38 kioclient(24933)/kio (KRun) KRun::init: INIT called
  00:24:38 kioclient(24933)/kdecore (KSycoca) KSycocaPrivate::openDatabase: 
Trying to open ksycoca from "/var/tmp/kdecache-yofel/ksycoca4"
  00:24:38 kioclient(24933)/kfile (kdelibs) KRecentDocument::add: 
KRecentDocument::add for  
"https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INT
  EGRATION"
  00:24:38 kioclient(24933)/kio (KRun) runTempService: runTempService: first 
url  
"https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INTEGRATION"
  00:24:38 kioclient(24933)/kio (KRun) supportedProtocols: supportedProtocols: 
("KIO")
  00:24:38 kioclient(24933)/kio (KRun) runTempService: runTempService: KProcess 
args= ("/usr/bin/firefox", 
"https://launchpad.net/+authorize-token?oauth_token=<>_permiss
  ion=DESKTOP_INTEGRATION")
  00:24:38 kioclient(24933)/kdecore (KStartupInfo) 
KStartupInfo::createNewStartupId: creating:  
"yofel-T510;1378506278;233618;24933_TIME0" : ""
  00:24:38 kioclient(24933)/kdecore (KStartupInfo) KStartupInfo::sendStartup: 
sending  "new:  ID="yofel-T510;1378506278;233618;24933_TIME0"   BIN="firefox" 
DESCRIPTION="Launching " DESKTOP=1 WM
  CLASS="0" HOSTNAME=yofel-T510 NAME="firefox" SCREEN=0"
  00:24:38 kioclient(24933)/kdecore (KStartupInfo) KStartupInfo::sendChange: 
sending  "change:  ID="yofel-T510;1378506278;233618;24933_TIME0"   PID=24935"
  00:24:38 kioclient(24933)/kio (KRun) KRun::slotTimeout: KRun(0x269dbe0)  
slotTimeout called

  (process:24935): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
  Gtk-Message: Failed to load module "canberra-gtk-module"
  Gtk-Message: Failed to load module "canberra-gtk-module"
  00:24:38 kioclient(24933)/kio (KRun) KProcessRunner::slotProcessExited: 
"firefox" exitCode= 0 exitStatus= 0
  00:24:38 kioclient(24933)/kdecore (KStartupInfo) KStartupInfo::sendFinish: 
sending  "remove:  ID="yofel-T510;1378506278;233618;24933_TIME0"   
HOSTNAME=yofel-T510 PID=24935"
  Gkr-Message: secret service operation failed: The secret was transferred or 
encrypted in an invalid way.
  Traceback (most recent call last):
    File "/usr/bin/pull-ppa-source", line 49, in 
  lp = Launchpad.login_with("pull-ppa-source", "production")
    File "/usr/lib/python2.7/dist-packages/launchpadlib/launchpad.py", line 
539, in login_with
  credential_save_failed, version)
    File "/usr/lib/python2.7/dist-packages/launchpadlib/launchpad.py", line 
346, in _authorize_token_and_login
  credentials = authorization_engine(credentials, credential_store)
    File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line 
520, in __call__
  credential_store.save(credentials, self.unique_consumer_id)
    File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line 
276, in save
  raise e
  keyring.errors.PasswordSetError: GNOME_KEYRING_RESULT_IO_ERROR

  Happens usually when using the kubuntu ppa packages batch backport
  script which calls pull-ppa-source about 160 times (once for every KDE
  SC source).

  ProblemType: BugDistroRelease: Ubuntu 13.10
  Package: gnome-keyring 3.8.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7

[Desktop-packages] [Bug 1345573] Re: Horizontal lines flashing on screen briefly

2016-07-22 Thread Jani Uusitalo

Haven't seen this once since upgrading to 16.04 back in April, so I'm
pretty sure the issue has been fixed. Yay!

** Changed in: xorg (Ubuntu)
   Status: Expired => Fix Released

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I don't recall seeing this with -lts-saucy or other previous Xorg packages. 
It was so obvious right after upgrading that either it never occurred before or 
was so rare or quick to flash away that it didn't register.
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1345573/+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 1485024] Re: context menu appears on wrong monitor when window is on rightmost of 3 monitors

2015-09-15 Thread Jani Uusitalo

With more testing I found that the context menu position depends
(perhaps solely) on whether my mouse pointer is on the left side or the
right side of the horizontal half of the rightmost monitor: if you
imagine a vertical line dividing the rightmost monitor's display area
into two equal-sized halves, right-clicking anywhere on the left side of
that line brings up the menu on the correct display, whereas right-
clicking anywhere on the right side brings it up on the wrong display.

(That is why I first made the mistake of thinking links weren't
affected: the ones I tried first just happened to be on the left side.)

Unfortunately I don't have a third display to verify that I'm really
seeing a different manifestation of the same bug as Nathaniel, of one
that depends on the monitor count.

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

Title:
  context menu appears on wrong monitor when window is on rightmost of 3
  monitors

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  This is a triple-head setup with 3 monitors arranged horizontally.

  When the chromium window is on either the left or middle monitor,
  right-clicking on a tab or normal web page displays a context menu at
  the mouse pointer (i.e. normal context menu behavior).

  When the chromium window is on the right monitor, right clicking on a
  tab or page displays a context menu on the right edge of the middle
  monitor (but at the expected vertical location). This is the bug.

  Interestingly, if the mouse pointer is close enough to the right edge
  of the right monitor when right clicking, the context menu appears in
  the expected place (on the right monitor near the mouse pointer, but
  "pushed in" so the whole menu fits on the screen without overflowing
  off the right edge).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: chromium-browser 43.0.2357.130-0ubuntu0.15.04.1.1174
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  DRM.card0.DP.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.1:
   edid-base64: 
AP///wAEafEkAQEBASIUAQOANR547sT2o1dKnCMRT1S/7wBxT4GAgUCVAKlAswDRwAEBAjqAGHE4LUBYLEUAEyshAAAe/QA4TB9TEQAKICAgICAg/ABWSzI0NgogICAgICAg/wBBOExNUVMwMzU3NzgKAIo=
   dpms: On
   modes: 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1280x960 
1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 
640x480 640x480 640x480 640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0.HDMI.A.2:
   edid-base64: 
AP///wAEacEkAQEBARMXAQOANR546pJlplVVnygNUFS/7wBxT4GAgUCVAKlAswDRwAEBAjqAGHE4LUBYLEUAEyshAAAe/QAyTB5TEQAKICAgICAg/ABWSzI0OAogICAgICAg/wBENUxNUVMwMjE5MDIKAJE=
   dpms: On
   modes: 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1280x960 
1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 
640x480 640x480 640x480 640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0.HDMI.A.3:
   edid-base64: 
AP///wAEafIkAQEBAQ8WAQOANR547sT2o1dKnCMRT1S/7wBxT4GAgUCVAKlAswDRwAEBAjqAGHE4LUBYLEUAEyshAAAe/QA4TB9TEQAKICAgICAg/ABWVzI0NgogICAgICAg/wBDNExNUVMwMjAyMzkKAZ0CAx7xS5AFBAMCARESExQfIwkHB4MBAABlAwwAEAAaNoCgcDgeQDAgNQATKyEAABpmIVaqUQAeMEaPMwATKyEAAB4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgBHYAYcRwWIFgsJQATKyEAAJ8AOQ==
   dpms: On
   modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 
1920x1080i 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1366x768 
1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 
800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 
640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0.VGA.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  Date: Fri Aug 14 11:24:58 2015
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
   '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/'
  DetectedPlugins:
   
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  Load-Avg-1min: 0.69
  Load-Processes-Running-Percent:   0.1%
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M

[Desktop-packages] [Bug 1345573] Re: Horizontal lines flashing on screen briefly

2015-09-05 Thread Jani Uusitalo

Just adding a note that this does still occur under 14.04, to which I
recently upgraded. Naturally this was to be expected, given that the
issue first occurred after switching to the Trusty HWE pack in 12.04.

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I don't recall seeing this with -lts-saucy or other previous Xorg packages. 
It was so obvious right after upgrading that either it never occurred before or 
was so rare or quick to flash away that it didn't register.
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1345573/+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 1485024] Re: context menu appears on wrong monitor when window is on rightmost of 3 monitors

2015-09-01 Thread Jani Uusitalo

I can reproduce this on a two-monitor setup: right-clicking in Chromium
on the right monitor brings up context menu on the left monitor. Right-
clicking on the left monitor works as expected.

I cannot reproduce the workaround: here the context menu opens on the
left monitor no matter how close to the right edge of the right monitor
I right-click Chromium.

I recently upgraded from 12.04 to 14.04, and this issue appeared with
the upgrade. 12.04 currently has Chromium 37.0.2062.120, whereas 14.04
has version 44.0.2403.89.

Upstream has a similar bug report about right-clicking links [1], but
for me at least right-clicking links is *not* affected: the issue occurs
only for the tabs' context menu and for web page right-clicks outside
links, whereas the context menu of links opens on the right monitor.

Also, LP bug #1430393 [2] looks related, and is also reproducible here:
(left-clicking) the main menu button also opens the menu on the wrong
monitor.

* [1] https://code.google.com/p/chromium/issues/detail?id=409287
* [2] https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1430393


** Bug watch added: code.google.com/p/chromium/issues #409287
   http://code.google.com/p/chromium/issues/detail?id=409287

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

Title:
  context menu appears on wrong monitor when window is on rightmost of 3
  monitors

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  This is a triple-head setup with 3 monitors arranged horizontally.

  When the chromium window is on either the left or middle monitor,
  right-clicking on a tab or normal web page displays a context menu at
  the mouse pointer (i.e. normal context menu behavior).

  When the chromium window is on the right monitor, right clicking on a
  tab or page displays a context menu on the right edge of the middle
  monitor (but at the expected vertical location). This is the bug.

  Interestingly, if the mouse pointer is close enough to the right edge
  of the right monitor when right clicking, the context menu appears in
  the expected place (on the right monitor near the mouse pointer, but
  "pushed in" so the whole menu fits on the screen without overflowing
  off the right edge).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: chromium-browser 43.0.2357.130-0ubuntu0.15.04.1.1174
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  DRM.card0.DP.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.1:
   edid-base64: 
AP///wAEafEkAQEBASIUAQOANR547sT2o1dKnCMRT1S/7wBxT4GAgUCVAKlAswDRwAEBAjqAGHE4LUBYLEUAEyshAAAe/QA4TB9TEQAKICAgICAg/ABWSzI0NgogICAgICAg/wBBOExNUVMwMzU3NzgKAIo=
   dpms: On
   modes: 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1280x960 
1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 
640x480 640x480 640x480 640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0.HDMI.A.2:
   edid-base64: 
AP///wAEacEkAQEBARMXAQOANR546pJlplVVnygNUFS/7wBxT4GAgUCVAKlAswDRwAEBAjqAGHE4LUBYLEUAEyshAAAe/QAyTB5TEQAKICAgICAg/ABWSzI0OAogICAgICAg/wBENUxNUVMwMjE5MDIKAJE=
   dpms: On
   modes: 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1280x960 
1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 
640x480 640x480 640x480 640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0.HDMI.A.3:
   edid-base64: 
AP///wAEafIkAQEBAQ8WAQOANR547sT2o1dKnCMRT1S/7wBxT4GAgUCVAKlAswDRwAEBAjqAGHE4LUBYLEUAEyshAAAe/QA4TB9TEQAKICAgICAg/ABWVzI0NgogICAgICAg/wBDNExNUVMwMjAyMzkKAZ0CAx7xS5AFBAMCARESExQfIwkHB4MBAABlAwwAEAAaNoCgcDgeQDAgNQATKyEAABpmIVaqUQAeMEaPMwATKyEAAB4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgBHYAYcRwWIFgsJQATKyEAAJ8AOQ==
   dpms: On
   modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 
1920x1080i 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1366x768 
1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 
800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 
640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0.VGA.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  Date: Fri Aug 14 11:24:58 2015
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
   '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/'
  DetectedPlugins:
   
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  Load-Avg-1min: 0.69
  Load-Processes-Running-Percent:   0.1%
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic

[Desktop-packages] [Bug 1485024] Re: context menu appears on wrong monitor when window is on rightmost of 3 monitors

2015-09-01 Thread Jani Uusitalo

Spoke too soon: looks like the context menu for links just also turned
affected. I swear they worked fine when I was writing the previous
comment!

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

Title:
  context menu appears on wrong monitor when window is on rightmost of 3
  monitors

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  This is a triple-head setup with 3 monitors arranged horizontally.

  When the chromium window is on either the left or middle monitor,
  right-clicking on a tab or normal web page displays a context menu at
  the mouse pointer (i.e. normal context menu behavior).

  When the chromium window is on the right monitor, right clicking on a
  tab or page displays a context menu on the right edge of the middle
  monitor (but at the expected vertical location). This is the bug.

  Interestingly, if the mouse pointer is close enough to the right edge
  of the right monitor when right clicking, the context menu appears in
  the expected place (on the right monitor near the mouse pointer, but
  "pushed in" so the whole menu fits on the screen without overflowing
  off the right edge).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: chromium-browser 43.0.2357.130-0ubuntu0.15.04.1.1174
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  DRM.card0.DP.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.1:
   edid-base64: 
AP///wAEafEkAQEBASIUAQOANR547sT2o1dKnCMRT1S/7wBxT4GAgUCVAKlAswDRwAEBAjqAGHE4LUBYLEUAEyshAAAe/QA4TB9TEQAKICAgICAg/ABWSzI0NgogICAgICAg/wBBOExNUVMwMzU3NzgKAIo=
   dpms: On
   modes: 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1280x960 
1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 
640x480 640x480 640x480 640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0.HDMI.A.2:
   edid-base64: 
AP///wAEacEkAQEBARMXAQOANR546pJlplVVnygNUFS/7wBxT4GAgUCVAKlAswDRwAEBAjqAGHE4LUBYLEUAEyshAAAe/QAyTB5TEQAKICAgICAg/ABWSzI0OAogICAgICAg/wBENUxNUVMwMjE5MDIKAJE=
   dpms: On
   modes: 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1280x960 
1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 
640x480 640x480 640x480 640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0.HDMI.A.3:
   edid-base64: 
AP///wAEafIkAQEBAQ8WAQOANR547sT2o1dKnCMRT1S/7wBxT4GAgUCVAKlAswDRwAEBAjqAGHE4LUBYLEUAEyshAAAe/QA4TB9TEQAKICAgICAg/ABWVzI0NgogICAgICAg/wBDNExNUVMwMjAyMzkKAZ0CAx7xS5AFBAMCARESExQfIwkHB4MBAABlAwwAEAAaNoCgcDgeQDAgNQATKyEAABpmIVaqUQAeMEaPMwATKyEAAB4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgBHYAYcRwWIFgsJQATKyEAAJ8AOQ==
   dpms: On
   modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 
1920x1080i 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1366x768 
1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 
800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 
640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0.VGA.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  Date: Fri Aug 14 11:24:58 2015
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
   '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/'
  DetectedPlugins:
   
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  Load-Avg-1min: 0.69
  Load-Processes-Running-Percent:   0.1%
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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:

[Desktop-packages] [Bug 1464871] [NEW] Instead of separate Desktop Actions for Play and Pause, have a single Play/Pause (like Totem)

2015-06-13 Thread Jani Uusitalo

Public bug reported:

The Unity Dash context menu for Rhythmbox currently has separate items
for Play and Pause. I think Totem does better by eliminating those
for a single Play/Pause item which does both. I also think the
interface should be consistent across these two applications. Rhythmbox-
client even supports the same parameter as totem for this (--play-
pause), so I created a patch for rhythmbox.desktop based on
totem.desktop, which should accomplish what I'm after.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: rhythmbox 3.2.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6
Uname: Linux 3.19.0-17-generic x86_64
ApportVersion: 2.17.3-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jun 13 17:05:52 2015
InstallationDate: Installed on 2011-07-06 (1437 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110531.1)
SourcePackage: rhythmbox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

** Patch added: Replaces separate play  pause Desktop Actions with a single 
play/pause Action
   
https://bugs.launchpad.net/bugs/1464871/+attachment/4414240/+files/rhythmbox.desktop.patch

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

Title:
  Instead of separate Desktop Actions for Play and Pause, have a single
  Play/Pause (like Totem)

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  The Unity Dash context menu for Rhythmbox currently has separate items
  for Play and Pause. I think Totem does better by eliminating those
  for a single Play/Pause item which does both. I also think the
  interface should be consistent across these two applications.
  Rhythmbox-client even supports the same parameter as totem for this
  (--play-pause), so I created a patch for rhythmbox.desktop based on
  totem.desktop, which should accomplish what I'm after.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: rhythmbox 3.2.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6
  Uname: Linux 3.19.0-17-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 17:05:52 2015
  InstallationDate: Installed on 2011-07-06 (1437 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110531.1)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1464871/+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 1345573] Re: Horizontal lines flashing on screen briefly

2015-05-27 Thread Jani Uusitalo

I can, but it'll be hard to get definitive evidence as the phenomenon
can be quite elusive, and I cannot run the daily for very long periods
(as it gets in the way of productivity). Obviously, if I catch it even
once on the daily, it'll be proof enough that the issue persists, but on
the other hand, not seeing the issue may just mean it didn't happen to
occur during the time running from the daily.

(Upgrading the system to latest release would be a surer way to find
out, but for now I intend to keep running 12.04 until the next LTS,
16.04.)

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I don't recall seeing this with -lts-saucy or other previous Xorg packages. 
It was so obvious right after upgrading that either it never occurred before or 
was so rare or quick to flash away that it didn't register.
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404592/+files/CurrentDmesg.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] MonitorsUser.xml.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: MonitorsUser.xml.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404599/+files/MonitorsUser.xml.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] Lsusb.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/1345573/+attachment/4404598/+files/Lsusb.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] UdevDb.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: UdevDb.txt
   https://bugs.launchpad.net/bugs/1345573/+attachment/4404604/+files/UdevDb.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] XorgLogOld.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: XorgLogOld.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404608/+files/XorgLogOld.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] Dependencies.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404593/+files/Dependencies.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] BootLog.gz

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: BootLog.gz
   https://bugs.launchpad.net/bugs/1345573/+attachment/4404591/+files/BootLog.gz

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] LightdmLog.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: LightdmLog.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404596/+files/LightdmLog.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] ProcCpuinfo.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: ProcCpuinfo.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404600/+files/ProcCpuinfo.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] Xrandr.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: Xrandr.txt
   https://bugs.launchpad.net/bugs/1345573/+attachment/4404609/+files/Xrandr.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] ProcModules.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404603/+files/ProcModules.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] DpkgLog.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: DpkgLog.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404594/+files/DpkgLog.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] Lspci.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/1345573/+attachment/4404597/+files/Lspci.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

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

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: ProcEnviron.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404601/+files/ProcEnviron.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] Re: Horizontal lines flashing on screen briefly

2015-05-26 Thread Jani Uusitalo

apport information

** Tags added: apport-collected compiz-0.9 ubuntu

** Description changed:

  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had recurring
  graphical glitches on screen, with short black horizontal lines
  appearing briefly on screen (on top of normal contents), particularly
  when switching between applications. The lines appear only for a few 100
  ms before going away (just enough to register in your eye that there's
  something there), so I've been trying to make a screen recording to
  capture it, but of course the phenomenon goes away when I do (perhaps
  RecordMyDesktop does something with the screen that makes it less likely
  to appear).
  
  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).
  
  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
+ --- 
+ .tmp.unity.support.test.0:
+  
+ ApportVersion: 2.0.1-0ubuntu17.9
+ Architecture: amd64
+ CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
+ CompositorRunning: compiz
+ DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
+ DistroCodename: precise
+ DistroRelease: Ubuntu 12.04
+ DistroVariant: ubuntu
+ DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
+ ExtraDebuggingInterest: Yes,
+ GraphicsCard:
+  Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
+Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
+ InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
+ MachineType: System manufacturer System Product Name
+ MarkForUpload: True
+ Package: xorg 1:7.6+12ubuntu2
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
+ Tags:  precise running-unity ubuntu compiz-0.9
+ Uname: Linux 3.13.0-53-generic x86_64
+ UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
+ UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
+ dmi.bios.date: 10/17/2014
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1505
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: P8H77-M PRO
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev X.0x
+ dmi.chassis.asset.tag: Asset-1234567890
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Chassis Manufacture
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
+ dmi.product.name: System Product Name
+ dmi.product.version: System Version
+ dmi.sys.vendor: System manufacturer
+ version.compiz: compiz 1:0.9.7.12-0ubuntu4
+ version.ia32-libs: ia32-libs N/A
+ version.libdrm2: libdrm2 2.4.52-1~precise2
+ version.libgl1-mesa-dri: libgl1-mesa-dri N/A
+ version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
+ version.libgl1-mesa-glx: libgl1-mesa-glx N/A
+ version.xserver-xorg-core: xserver-xorg-core N/A
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
+ version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404590/+files/BootDmesg.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since

[Desktop-packages] [Bug 1345573] XorgLog.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: XorgLog.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404607/+files/XorgLog.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] UnitySupportTest.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: UnitySupportTest.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404606/+files/UnitySupportTest.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] ProcInterrupts.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404602/+files/ProcInterrupts.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] GconfCompiz.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: GconfCompiz.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404595/+files/GconfCompiz.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] UdevLog.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404605/+files/UdevLog.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1345573] xdpyinfo.txt

2015-05-26 Thread Jani Uusitalo

apport information

** Attachment added: xdpyinfo.txt
   
https://bugs.launchpad.net/bugs/1345573/+attachment/4404610/+files/xdpyinfo.txt

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

Title:
  Horizontal lines flashing on screen briefly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading HWE from -lts-saucy to -lts-trusty, I have had
  recurring graphical glitches on screen, with short black horizontal
  lines appearing briefly on screen (on top of normal contents),
  particularly when switching between applications. The lines appear
  only for a few 100 ms before going away (just enough to register in
  your eye that there's something there), so I've been trying to make a
  screen recording to capture it, but of course the phenomenon goes away
  when I do (perhaps RecordMyDesktop does something with the screen that
  makes it less likely to appear).

  I have another 12.04 system with desktop Radeon graphics, and there
  -lts-trusty has not produced this issue so far (the one with the issue
  and the one I'm attaching the logs here from has Intel).

  I don't recall seeing this with -lts-saucy or other previous Xorg
  packages. It was so obvious right after upgrading that either it never
  occurred before or was so rare or quick to flash away that it didn't
  register.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Jul 20 15:21:12 2014
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: xorg-lts-trusty
  UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() 
(showErrors=True)
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19
  Tags:  precise running-unity ubuntu compiz-0.9
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo 
vboxusers
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:

1 2 >

1 - 100 of 186 matches

Mail list logo