from:"Valentin"

Hello,
Sorry for the time I take, I have a lot of work these days...

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

Title:
  Alt+Tab works with a wrong behaviour

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On GNOME Shell 3.32.0, there is a very confusing behaviour with the "alt-tab" 
shortcut.

  Example, I have this list of app (windows):

  [w1][w2][w3][w4][w5][w6]

  On alt+tab, now I get this:

  [w2][w1][w3][w4][w5][w6]

  No problem for the moment.
  But if I use Super + H to hide the first Window (here, w2).

  The list doesn't take the expected behaviour:
  [w1][w2][w3][w4][w5][w6] (like on Unity, Windows 10, OSX, or others...)

  But something like this:

  [w1][w3].[w4].[w5].[w6].

  [w2] go somewhere on a "." between [w3] and [w6], or after [w6].

  This if very frustrating for example when you want to hide a half
  screen window who is in front of another, and then want to go-back to
  the half screen window.

  For example, Unity have a correct behaviour with this.

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-02 (27 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: third-party-packages disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

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

apport information

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

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

Title:
  Alt+Tab works with a wrong behaviour

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On GNOME Shell 3.32.0, there is a very confusing behaviour with the "alt-tab" 
shortcut.

  Example, I have this list of app (windows):

  [w1][w2][w3][w4][w5][w6]

  On alt+tab, now I get this:

  [w2][w1][w3][w4][w5][w6]

  No problem for the moment.
  But if I use Super + H to hide the first Window (here, w2).

  The list doesn't take the expected behaviour:
  [w1][w2][w3][w4][w5][w6] (like on Unity, Windows 10, OSX, or others...)

  But something like this:

  [w1][w3].[w4].[w5].[w6].

  [w2] go somewhere on a "." between [w3] and [w6], or after [w6].

  This if very frustrating for example when you want to hide a half
  screen window who is in front of another, and then want to go-back to
  the half screen window.

  For example, Unity have a correct behaviour with this.

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-02 (27 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: third-party-packages disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825953/+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 1825953] Re: Alt+Tab works with a wrong behaviour

apport information

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

** Description changed:

  Hello,
  On GNOME Shell 3.32.0, there is a very confusing behaviour with the "alt-tab" 
shortcut.
  
  Example, I have this list of app (windows):
  
  [w1][w2][w3][w4][w5][w6]
  
  On alt+tab, now I get this:
  
  [w2][w1][w3][w4][w5][w6]
  
  No problem for the moment.
  But if I use Super + H to hide the first Window (here, w2).
  
  The list doesn't take the expected behaviour:
  [w1][w2][w3][w4][w5][w6] (like on Unity, Windows 10, OSX, or others...)
  
  But something like this:
  
  [w1][w3].[w4].[w5].[w6].
  
  [w2] go somewhere on a "." between [w3] and [w6], or after [w6].
  
  This if very frustrating for example when you want to hide a half screen
  window who is in front of another, and then want to go-back to the half
  screen window.
  
  For example, Unity have a correct behaviour with this.
  
  Thank you
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 19.04
+ InstallationDate: Installed on 2019-04-02 (27 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
+ Package: gnome-shell 3.32.0+git20190410-1ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
+ Tags: third-party-packages disco
+ Uname: Linux 5.0.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo wireshark
+ _MarkForUpload: True

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

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

Title:
  Alt+Tab works with a wrong behaviour

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On GNOME Shell 3.32.0, there is a very confusing behaviour with the "alt-tab" 
shortcut.

  Example, I have this list of app (windows):

  [w1][w2][w3][w4][w5][w6]

  On alt+tab, now I get this:

  [w2][w1][w3][w4][w5][w6]

  No problem for the moment.
  But if I use Super + H to hide the first Window (here, w2).

  The list doesn't take the expected behaviour:
  [w1][w2][w3][w4][w5][w6] (like on Unity, Windows 10, OSX, or others...)

  But something like this:

  [w1][w3].[w4].[w5].[w6].

  [w2] go somewhere on a "." between [w3] and [w6], or after [w6].

  This if very frustrating for example when you want to hide a half
  screen window who is in front of another, and then want to go-back to
  the half screen window.

  For example, Unity have a correct behaviour with this.

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-02 (27 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: third-party-packages disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

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

apport information

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

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

Title:
  Alt+Tab works with a wrong behaviour

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On GNOME Shell 3.32.0, there is a very confusing behaviour with the "alt-tab" 
shortcut.

  Example, I have this list of app (windows):

  [w1][w2][w3][w4][w5][w6]

  On alt+tab, now I get this:

  [w2][w1][w3][w4][w5][w6]

  No problem for the moment.
  But if I use Super + H to hide the first Window (here, w2).

  The list doesn't take the expected behaviour:
  [w1][w2][w3][w4][w5][w6] (like on Unity, Windows 10, OSX, or others...)

  But something like this:

  [w1][w3].[w4].[w5].[w6].

  [w2] go somewhere on a "." between [w3] and [w6], or after [w6].

  This if very frustrating for example when you want to hide a half
  screen window who is in front of another, and then want to go-back to
  the half screen window.

  For example, Unity have a correct behaviour with this.

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-02 (27 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: third-party-packages disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825953/+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 1825953] Re: Alt+Tab works with a wrong behaviour

2019-05-02 Thread Valentin Crone

Hello,
I have reported this to the gitlab, but I feel that the developers are not very 
open minded to user's suggestions...

https://gitlab.gnome.org/GNOME/gnome-shell/issues/1233

"It's not a bug, you disagree with the behaviour" → Closed.

Very coolwhen will be the time where Linux UI will take the users
suggestions to make better UI in place to force users to change many
habits on each new version?

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

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

Title:
  Alt+Tab works with a wrong behaviour

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On GNOME Shell 3.32.0, there is a very confusing behaviour with the "alt-tab" 
shortcut.

  Example, I have this list of app (windows):

  [w1][w2][w3][w4][w5][w6]

  On alt+tab, now I get this:

  [w2][w1][w3][w4][w5][w6]

  No problem for the moment.
  But if I use Super + H to hide the first Window (here, w2).

  The list doesn't take the expected behaviour:
  [w1][w2][w3][w4][w5][w6] (like on Unity, Windows 10, OSX, or others...)

  But something like this:

  [w1][w3].[w4].[w5].[w6].

  [w2] go somewhere on a "." between [w3] and [w6], or after [w6].

  This if very frustrating for example when you want to hide a half
  screen window who is in front of another, and then want to go-back to
  the half screen window.

  For example, Unity have a correct behaviour with this.

  Thank you
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-02 (27 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags: third-party-packages disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

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

2022-03-14 Thread 6-valentin

I confirm this on the most recent distributions of Arch Linux and
Thunderbird.

The suggested fix works to solve the sluggishness.

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

Title:
  [upstream] Very high CPU and slow responsiveness in Thunderbird 91

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Very high CPU and slow responsiveness in Thunderbird 91.5.0. Just
  moving the mouse cursor over a message list results in 365% CPU for
  me.

  I had to set this in the config editor to fix it:

    gfx.webrender.force-disabled = TRUE

  Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1959747/+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 2047737] Re: Nautilus crashes when opening folders that contain files with js or json extensions

2024-01-23 Thread Valentin Bersier

I can confirm this happens to me too on a fresh install of Ubuntu 23.10.
I specifically re-installed Ubuntu (I was on 22.04 LTS) because of the
problem but it's still present.

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

Title:
  Nautilus crashes when opening folders that contain files with js or
  json extensions

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  After attempting to open a folder that contains js or json files the app 
crashes.
  when testing from terminal I get a segmentation fault and no other error info.
  even enabling G_MESSAGES_DEBUG=all did not provide additional info.
  removing nautilus extensions, resetting xdg-mime for js/json, and disabling 
nautilus features (search, file count, etc ...) did not fix the problem either.

  additional info
  $ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:42.6-0ubuntu1
Candidate: 1:42.6-0ubuntu1
Version table:
   *** 1:42.6-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:42.2-0ubuntu2.1 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:42.0-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.6-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 30 14:50:09 2023
  InstallationDate: Installed on 2023-02-14 (319 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.3-0ubuntu3.1
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2047737/+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 2056642] [NEW] drop down menu appears on another workspace

2024-03-09 Thread Valentin Stoykov

Public bug reported:

I am using Selenium webdriver to open a drop down menu in Firefox.

When I manually open the drop down menu the bug does not appear. Because
the drop down menu is being closed when I switch between workspaces.

But when I switch to another workspace when the drop down menu is opened
by Selenium webdriver it is appearing on the other workspace and I can
interact with it.


Screenshot is attached.

$ dpkg --list | grep firefox
ii  firefox1:1snap1-0ubuntu2
   amd64Transitional package - firefox -> firefox snap

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-25-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  9 17:35:02 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/6.1.50, 6.5.0-21-generic, x86_64: installed
 virtualbox/6.1.50, 6.5.0-25-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [1849:0102]
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-25-generic 
root=UUID=929bcce7-36fe-499e-8f75-ae48a4583b03 ro rootflags=subvol=@ quiet
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/07/2011
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: H61M-GS
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd03/07/2011:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-GS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/bugs/2056642/+attachment/5754315/+files/PmqOQjl.png

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

Title:
  drop down menu appears on another workspace

Status in xorg package in Ubuntu:
  New

Bug description:
  I am using Selenium webdriver to open a drop down menu in Firefox.

  When I manually open the drop down menu the bug does not appear.
  Because the drop down menu is being closed when I switch between
  workspaces.

  But when I switch to another workspace when the drop down menu is
  opened by Selenium webdriver it is appearing on the other workspace
  and I can interact with it.

  
  Screenshot is attached.

  $ dpkg --list | grep firefox
  ii  firefox1:1snap1-0ubuntu2  
 amd64Transitional package - firefox -> firefox snap

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  9 17:35:02 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.50, 6.5.0-21-generic, x86_64: installed
   virtualbox/6.1.50, 6.5.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controll

[Desktop-packages] [Bug 927952] Re: When I press the Print Screen button, it will not appear in "Save Screenshot" window.

2018-08-15 Thread Valentin Crone

+1 Kris

GNOME in all is a downgrade for Unity users, I don't understand why
Ubuntu choose GNOME now, even if X.org is back...

When a Ubuntu Unity remix?

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

Title:
  When I press the Print Screen button, it will not appear in "Save
  Screenshot" window.

Status in Ayatana Design:
  Fix Released
Status in Gnome Screenshot:
  Expired
Status in gnome-screenshot package in Ubuntu:
  Fix Released
Status in gnome-screenshot source package in Precise:
  Fix Released
Status in gnome-screenshot package in Debian:
  Confirmed

Bug description:
  When taking a screenshot with Print Screen or Alt+Print Screen a
  dialog box asking you what and where to save the file no longer
  appears.  So while you hear a camera sound you have no other
  confirmation that a screenshot was really taken.  Additionally, there
  is no way of knowing where the screenshot went.  I'd imagine this will
  be particularly problematic for new users of Ubuntu.

  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: gnome-screenshot 3.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
  Uname: Linux 3.2.0-14-generic x86_64
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Mon Feb  6 23:54:17 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029.1)SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to precise on 2012-01-27 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/927952/+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 1792085] Re: MTP not working/very slow on Bionic

2019-09-07 Thread Valentin Crone

It's not the first bug who is not fixed in one or more years, the
problem is, when you invite new users to discover ubuntu, at a time,
they will need to connect their phone on their computer, and they will
say: This doesn't work, and the fix (via mtpfs-go) is complicated for
basic users.

Today from the boot to the basic usage, you have a lot of problems never
fixed or ignored when reported that make ubuntu or linux in general not
user friendly, and even if people with some knowledge in IT always find
after some hours a way to use their favorite OS on their computer, the
lambda user, who will be really happy to use ubuntu, is in fact not able
to install it, or use it on some specific points like this, even if they
follow a tutorial. (Boot, uefi, wifi, graphics, mtp, bugs in gui,
missing basic feature or removed, sound, video, etc)


For information, with go-mtpfs, you can set an higher timeout value, then the 
mtp is usable, the bug is just a timeout issuenot fixed in 1 year

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

Title:
  MTP not working/very slow on Bionic

Status in libmtp:
  New
Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  Hi, unfortunately (for me) MTP android devices no more work on Ubuntu
  18.04.

  I have used MTP on 16.04 without problems, but on 18.04 it does not
  work. When I connect my Android devices (Samsung A5 and Samsung J3)
  and I try to list directories with many files (e.g. /DCIM/Camera) the
  window hangs until I disconnect the device. Same issue if I try to
  post the command "ls /var/run/1000/gvfs/".

  I have installed Ubuntu 18.04 on two different machines - an older HP
  laptop and a recent DELL laptop - and the issue is present on the all
  of them.

  I suspect a defect on the "libmtp". I tried many alternative solutions
  suggested by the net (e.g. jmtpfs and so on) but anyone worked.

  That's all!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-fuse 1.36.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 06:20:07 2018
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libmtp/+bug/1792085/+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 1797734] Re: slow calculator startup

2019-06-11 Thread Valentin Crone

Hello,
Try to remove the snap package:

snap remove gnome-calculator

And install the deb package:

apt-get install gnome-calculator


I have experimented this on Ubuntu 18.04 and 19.04 and it seem to be really 
faster.
I have experienced many speed problems with snap apps. And some was really 
laggy.

For example, with discord on snap, on one of my laptop: crashes, and mic 
problems.
For the other laptop: Really laggy, 5 to 10s between the time I type something, 
and the time it appear on the screen, on a laptop with 2 SSD.
I have the time to start firefox 3 times on the same period, and discord in 
firefox doesn't present any of theses problems.

After this, I remove the snap version, and install the official deb
version (from the discord website), and no problems. Fluid and not full
of bugs.

Same problem for Atom (atom.io), buggy and laggy with snap.
I don't understand why snap is slow like this for certain apps, and I don't 
understand exactly how snap works, but I suspect him to be the cause of many 
slow apps on recent versions of Ubuntu.

On my laptop, for gnome-calculator, the time to open:
- Snap: 2 to 10s
- Deb: 0.1 to 1s

I can't say it's definitely snap, but I suppose you can look at this.

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

Title:
  slow calculator startup

Status in gnome-calculator package in Ubuntu:
  Confirmed

Bug description:
  The calculator starts very slowly. It's a tiny program, but it runs
  like a very big one. In previous versions of Ubuntu, the launch was
  normal, very fast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calculator (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:40:06 2018
  InstallationDate: Installed on 2018-05-06 (160 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+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 927952] Re: When I press the Print Screen button, it will not appear in "Save Screenshot" window.

2019-06-13 Thread Valentin Crone

Hi
I have a similar problem, but I use an extension to do my screenshots, but I 
seem each time you close an app, you clipboard is empty

It's a strange behaviour

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

Title:
  When I press the Print Screen button, it will not appear in "Save
  Screenshot" window.

Status in Ayatana Design:
  Fix Released
Status in Gnome Screenshot:
  Expired
Status in gnome-screenshot package in Ubuntu:
  Fix Released
Status in gnome-screenshot source package in Precise:
  Fix Released
Status in gnome-screenshot package in Debian:
  Confirmed

Bug description:
  When taking a screenshot with Print Screen or Alt+Print Screen a
  dialog box asking you what and where to save the file no longer
  appears.  So while you hear a camera sound you have no other
  confirmation that a screenshot was really taken.  Additionally, there
  is no way of knowing where the screenshot went.  I'd imagine this will
  be particularly problematic for new users of Ubuntu.

  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: gnome-screenshot 3.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
  Uname: Linux 3.2.0-14-generic x86_64
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Mon Feb  6 23:54:17 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029.1)SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to precise on 2012-01-27 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/927952/+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 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

2019-06-18 Thread Valentin Wittich

Still having that issue with Ubuntu 18.04.2 LTS on a ThinkPad T480 and
the stock pulseaudio 11.1.

Is there going to be a fix/upgrade for the LTS?

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

Title:
  pulseaudio assert failure: pulseaudio: mixer.c:929:
  snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250

  ---

  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.

  Got an other crash, and that time 'sound' is fully lost (pulseaudio
  not reloaded). Wonder if lp:1662860 can be concerned.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem4084 F pulseaudio
   /dev/snd/controlC0:  oem4084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 10 09:55:45 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1663528/+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 1834366] [NEW] xdg-desktop-portal-gtk package makes the computer crawl to the knees

2019-06-26 Thread Valentin Quequet

Public bug reported:

Hi the Team!

I run Ubuntu 18.04.2 LTS (Bionic Beaver) 64-bit on Intel-based platform.

I have noticed for ages that sometimes a dozen of programs where
consuming much too CPU cycles. Amongst them were xdg-desktop-portal-gtk.
And if I "kill -STOP" the PID of xdg-desktop-portal-gtk then all calm
down and become responsive again.

If fact the most affected applications were gedit, geany, firefox,
google-chrome, and, last but not leas, the Xorg server itself!,
hindering the usability of the whole system.

Also, this bug maybe also affects default Ubuntu session/desktop/window
manager or compositor, and non default ones, possibly.

In hope this helps,
Sincerely, Valentin.

** Affects: xdg-desktop-portal-gtk (Ubuntu)
Importance: Undecided
Status: New

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

Title:
xdg-desktop-portal-gtk package makes the computer crawl to the knees

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

Bug description:
Hi the Team!

I run Ubuntu 18.04.2 LTS (Bionic Beaver) 64-bit on Intel-based
platform.

I have noticed for ages that sometimes a dozen of programs where
consuming much too CPU cycles. Amongst them were xdg-desktop-portal-
gtk. And if I "kill -STOP" the PID of xdg-desktop-portal-gtk then all
calm down and become responsive again.

If fact the most affected applications were gedit, geany, firefox,
google-chrome, and, last but not leas, the Xorg server itself!,
hindering the usability of the whole system.

Also, this bug maybe also affects default Ubuntu
session/desktop/window manager or compositor, and non default ones,
possibly.

In hope this helps,
Sincerely, Valentin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1834366/+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 1749150] [NEW] Spontaneous single window freezing

Public bug reported:

Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
No way found to revive in-time refreshing except full window closing (or blind 
login, in case of KDE lock screen). Keyboard or mouse activity in a such window 
doesn't help.
A one-shot refresh can be easily caused by switching to another virtual desktop 
and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
No relation to host uptime or X session uptime is visible.

Observed on two different hosts, both carrying Kubuntu 16.04 and running
XWindow+KDE as desktop environment. KDE is standard Kubuntu one.
Multiple virtual desktops are used on both hosts.

The issue started to appear approximately 4-5 months ago but I can't
specify exact package change that could have caused it. Both hosts are
regularly updated (no more than 1 week delay).

The first host has:
video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
Kernel driver in use: radeon
Kernel modules: radeon
CPU: AMD FX-8150
RAM: 16GB
Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
current kernel: linux-image-4.4.0-112-generic
video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

Issue rate on this host is rather tiny (~1 per week).

The second one has:
video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
(really this is GeForce GT 740)
CPU:Intel i3-4170
RAM: 16GB
Installed originally as Kubuntu 16.04
current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

Issue rate on this host is 1-2 per day and was much higher with VESA
driver in use.

No respective messages are found in Xorg.*.log or ~/.xsession-errors,
but the latter has got stream of messages like:

at host with AMD and Radeon:
kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) 
( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" ) 
( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

at host with Intel and Nvidia:
kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" 
) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" )
kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: "DVI-D-0" 
) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( "DVI-D-0" )

such messages started appearing approximately at the same time, plus-
minus 1-2 months.

Additional info can be provided on demand.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Feb 13 11:47:32 2018
InstallationDate: Installed on 2014-12-16 (1154 days ago)
InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can

[Desktop-packages] [Bug 1749150] DpkgLog.txt

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054880/+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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.

[Desktop-packages] [Bug 1749150] DkmsStatus.txt

apport information

** Attachment added: "DkmsStatus.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054879/+files/DkmsStatus.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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not suppo

[Desktop-packages] [Bug 1749150] Re: Spontaneous single window freezing

apport information

** Tags added: apport-collected kubuntu

** Description changed:

  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.
  
  Observed on two different hosts, both carrying Kubuntu 16.04 and running
  XWindow+KDE as desktop environment. KDE is standard Kubuntu one.
  Multiple virtual desktops are used on both hosts.
  
  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).
  
  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon
  
  Issue rate on this host is rather tiny (~1 per week).
  
  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.
  
  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.
  
  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:
  
  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  
  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  
  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.
  
  Additional info can be provided on demand.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
+ --- 
+ .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
+ .proc.driver.nvidia.registry: Binary: ""
+ .proc.driver.nvidia.version:
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
+  GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
+ .proc.driver.nvidia.warnings.fbdev:
+  Your system is not currently configured to drive a VGA console
+  on the primary VGA device. The NVIDIA Linux graphics driver
+  requires the use of a text-mode VGA console. Use of other console
+  drivers including, but not limited to, vesafb, may result in
+  corruption and stability problems, and is not supported.
+ ApportVersion: 2.20.1-0ubuntu2.15
+ Architecture: amd64
+ CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
+ CompositorRunning: None
+ CurrentDesktop: KDE
+ DistUpgraded: Fresh install
+ DistroCodename: xenial
+ DistroRelease: Ubuntu 16.04
+ DistroVariant: kubun

[Desktop-packages] [Bug 1749150] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054877/+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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not s

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054887/+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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not sup

[Desktop-packages] [Bug 1749150] Re: Spontaneous single window freezing

Just have sent info from the second host (Intel+NVidia; more prone to
the issue). Will do it for the first host in a few hours.

Please notice that apport-collect is somewhat broken -
1) it didn't request dependence on python-qt5 but needs it for run time;
2) it just created a dialog window "Text. Yes? No?", i.e. without real 
question. I had to blindly answer "yes".

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA de

[Desktop-packages] [Bug 1749150] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054889/+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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not sup

[Desktop-packages] [Bug 1749150] XorgLog.txt

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054891/+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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.

[Desktop-packages] [Bug 1749150] NvidiaBugReportLog.txt

apport information

** Attachment added: "NvidiaBugReportLog.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054884/+files/NvidiaBugReportLog.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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems,

[Desktop-packages] [Bug 1749150] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054878/+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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not s

[Desktop-packages] [Bug 1749150] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1749150/+attachment/5054883/+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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  App

[Desktop-packages] [Bug 1749150] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054885/+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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not sup

[Desktop-packages] [Bug 1749150] Xrandr.txt

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1749150/+attachment/5054893/+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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  A

[Desktop-packages] [Bug 1749150] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054881/+files/JournalErrors.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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not

[Desktop-packages] [Bug 1749150] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1749150/+attachment/5054882/+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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  App

[Desktop-packages] [Bug 1749150] XorgLogOld.txt

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054892/+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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not suppo

[Desktop-packages] [Bug 1749150] BootLog.txt

apport information

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054876/+files/BootLog.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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.

[Desktop-packages] [Bug 1749150] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1749150/+attachment/5054890/+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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  A

[Desktop-packages] [Bug 1749150] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054886/+files/ProcCpuinfoMinimal.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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems,

[Desktop-packages] [Bug 1749150] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054888/+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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is n

[Desktop-packages] [Bug 1749150] nvidia-settings.txt

apport information

** Attachment added: "nvidia-settings.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054894/+files/nvidia-settings.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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is

[Desktop-packages] [Bug 1749150] xdpyinfo.txt

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054895/+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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported

[Desktop-packages] [Bug 1749150] Re: Spontaneous single window freezing

On the first host, apport-collect crashed with:

Traceback (most recent call last):
  File "/usr/share/apport/apport-kde", line 530, in 
sys.exit(UserInterface.run_argv())
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 658, in run_argv
return self.run_update_report()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 574, in 
run_update_report
response = self.ui_present_report_details(allowed_to_report)
  File "/usr/share/apport/apport-kde", line 367, in ui_present_report_details
desktop_info)
  File "/usr/share/apport/apport-kde", line 184, in __init__
self.ui.ui_update_view(self)
  File "/usr/share/apport/apport-kde", line 358, in ui_update_view
QTreeWidgetItem(keyitem, [str(line)])
UnicodeEncodeError: 'ascii' codec can't encode characters in position 17-18: 
ordinal not in range(128)
Segmentation fault

I guess it needs more stabilization work :(

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus:

[Desktop-packages] [Bug 1801520] [NEW] On login screen, gdm3 behaves as if someone continually hit 'Enter'

2018-11-03 Thread Valentin Quequet

Public bug reported:

After logging in, using a session, zapping (locking) the session and
leaving the computer alone for some time, gdm3 sometimes behaves
erratically.

The strange behavior is the following :
  - Keys pressed don't show as dots in password text field ; they don't show at 
all
  - gdm3 tries validating empty password, in loop, without me even typing 
'Enter', continually

Please, look the folder at https://www.jinstallelinux.net/pub1/www/GDM3_Bugs/ .
The 3 pictures show what happen when someone type a wrong password (normal gdm3 
behavior).
The video shows the bad behavior of gdm3 under mysterious circumstances (yet to 
be defined).

Thanks for reading,
In hope this helps.

Val

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

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

Title:
  On login screen, gdm3 behaves as if someone continually hit 'Enter'

Status in gdm3 package in Ubuntu:
  New

Bug description:
  After logging in, using a session, zapping (locking) the session and
  leaving the computer alone for some time, gdm3 sometimes behaves
  erratically.

  The strange behavior is the following :
- Keys pressed don't show as dots in password text field ; they don't show 
at all
- gdm3 tries validating empty password, in loop, without me even typing 
'Enter', continually

  Please, look the folder at https://www.jinstallelinux.net/pub1/www/GDM3_Bugs/ 
.
  The 3 pictures show what happen when someone type a wrong password (normal 
gdm3 behavior).
  The video shows the bad behavior of gdm3 under mysterious circumstances (yet 
to be defined).

  Thanks for reading,
  In hope this helps.

  Val

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801520/+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 1741027] Re: Screen sharing panels abort using an non-existent vino gsettings key

2018-11-09 Thread Valentin Lab

Still an issue here on 18.04 ... Tried the PPA
ppa:unity7maintainers/unity7-desktop by curiosity... but this is loaded
with crippling bugs that render it unusable and does not have the
desktop sharing icon anymore.

The workaround from comment number 11, from Zakhar (alainb06) worked for
me:

Direct link: https://bugs.launchpad.net/ubuntu/+source/unity-control-
center/+bug/1741027/comments/11

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

Title:
  Screen sharing panels abort using an non-existent vino gsettings key

Status in unity-control-center package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed
Status in vino package in Ubuntu:
  Invalid

Bug description:
  [FFE]

  This happens because Gnome removed that particular gsettings key. The
  removal did not happen with the ui removal but rather much later than
  that. That is why it doesn't work with the latest version of vino.

  As of now If users try to open the new sharing panel, unity-control-
  center will crash. This sort behavior is not desired on LTS release
  (18.04).


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

  Specifically, the error report

   "Settings schema 'org.gnome.Vino' does not contain a key named
  'enabled' "

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027/+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 1749150] Re: Spontaneous single window freezing

2018-04-08 Thread Valentin Nechayev

Well, I was unable to spend much time in Gnome to reproduce the effect or 
refute it.
OTOH it wasn't reproduced since this ticket start on host 1 and became much 
less frequent on host 2, after I switched drivers on it nvidia->nouveau and 
back.
Also a new laptop showed it, but also rather rarely.

I would second the guess it is KDE specific due to absense of other
ideas.

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary V

[Desktop-packages] [Bug 1698351] Re: Search in Nautilus Files does not allow sorting of results

Any update on that? This should not be a bug in LTS!

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

Title:
  Search in Nautilus Files does not allow sorting of results

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  The version of nautilus/Files included with Ubuntu 17.04 no longer
  allows sorting of search results.

  Previously, sort was achieved by clicking on the column header titles.

  This no longer works.

  It represents a significant regression in the search feature.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1698351/+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 1698351] Re: Search in Nautilus Files does not allow sorting of results

I added an new issue on github
https://gitlab.gnome.org/GNOME/nautilus/issues/888 but it seams that
there is no intenstion so solve that behavior.

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

Title:
  Search in Nautilus Files does not allow sorting of results

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  The version of nautilus/Files included with Ubuntu 17.04 no longer
  allows sorting of search results.

  Previously, sort was achieved by clicking on the column header titles.

  This no longer works.

  It represents a significant regression in the search feature.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1698351/+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 1698351] Re: Search in Nautilus Files does not allow sorting of results

I added an new issue on github
https://gitlab.gnome.org/GNOME/nautilus/issues/888 but it seams that
there is no intenstion so solve that behaivier.

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

Title:
  Search in Nautilus Files does not allow sorting of results

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  The version of nautilus/Files included with Ubuntu 17.04 no longer
  allows sorting of search results.

  Previously, sort was achieved by clicking on the column header titles.

  This no longer works.

  It represents a significant regression in the search feature.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1698351/+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 1698351] Re: Search in Nautilus Files does not allow sorting of results