date:20180323

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Pomalý systém

Status in xorg package in Ubuntu:
  Expired

Bug description:
  SK.LANG.PRACUJE pomaly,pomaly nabieha systém.Nie som dlho užívateľ
  Ubuntu,zatiaľ sa iba učím.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Dec 30 09:50:44 2017
  DistUpgraded: 2017-10-23 19:02:47,148 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:13c7]
  InstallationDate: Installed on 2017-05-30 (214 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170411)
  MachineType: ASUSTeK Computer Inc. K54C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=6ba22068-04c3-4d1a-8a5e-dac9dd5aec79 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2017-10-23 (67 days ago)
  dmi.bios.date: 01/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K54C.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K54C
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK54C.204:bd01/20/2012:svnASUSTeKComputerInc.:pnK54C:pvr1.0:rvnASUSTeKComputerInc.:rnK54C:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K54C
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 23 16:35:06 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.3
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1740579/+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 1744517] Re: Ubuntu Software

[Expired for gnome-software (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-software (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Ubuntu Software

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  Initially when I was using the internet, a warning symbol near wi-fi
  symbol (at top right corner) appeared indicating that the system is
  not updated and may be in risk. To solve the problem I clicked the
  symbol and a new message is shown that the system is updated. After
  that the Ubuntu software package icon (left side) is found to be non-
  responsive. Please advise.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jan 21 06:42:26 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:118c]
  InstallationDate: Installed on 2018-01-06 (14 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Acer Swift SF314-52
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic.efi.signed 
root=UUID=bf576d98-9349-4939-a505-eb772d5a8d9a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Suntory_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd06/27/2017:svnAcer:pnSwiftSF314-52:pvrV1.05:rvnKBL:rnSuntory_KL:rvrV1.05:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-52
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Jan 21 06:40:56 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1744517/+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 1757299] Re: [Dell OptiPlex 755] xorg hangs

** Description changed:

- The problem is that my GUI stops responding after launching a few
- applications, and is correlated to high CPU utilization of xorg.
+ The problem is that after launching a few applications, the GUI may
+ become unresponsive, although this is not consistently reproducible.
+ When the GUI is unresponsive, it is correlated to high CPU utilization
+ of xorg.
  
- An example reproduction scenario:
- launched startx,
- launched an xterm via twm,
- launched another xterm via the first,
- launched tmux,
- launched firefox-esr, bluetooth-manager, and pavucontrol,
- maximized the xterm running tmux
+ An example reproduction scenario is launch the following in order, and 
quickly:
+ startx
+ xterm via twm
+ another xterm via the first xterm
+ tmux
+ firefox-esr
+ bluetooth-manager
+ pavucontrol
  
- xorg stopped responding, ctl-alt-Fn don't respond either
+ While the above are launching, maximize the xterm running tmux, and the
+ GUI immediately becomes unresponsive. For example, Ctrl+Alt+Fn don't
+ respond.
  
- logged in via ssh, attached to tmux, launched htop, copied htop output,
- in which you can see xorg consuming lots of cpu.
+ After this, I logged in via ssh, attached to tmux, launched htop, copied
+ htop output, which shows xorg at 94.6 CPU%.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog:
   Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
    * Starting AppArmor profiles   [160G
  [154G[ OK ]
    * Restoring resolver state...   [160G
  [154G[ OK ]
  CompositorRunning: None
  Date: Tue Mar 20 17:15:16 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Dell OptiPlex 755 [1028:0211]
     Subsystem: Dell OptiPlex 755 [1028:0211]
  JournalErrors:
   -- Logs begin at Fri 2018-02-23 08:59:47 CST, end at Tue 2018-03-20 17:14:39 
CDT. --
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="pci-_00_1b.0" card_name="alsa_card.pci-_00_1b.0" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
   Mar 20 17:01:37 hostname pulseaudio[1109]: [pulseaudio] pid.c: Daemon 
already running.
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 panic=30
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Summary changed:

- [Dell OptiPlex 755] xorg hangs
+ [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after 
launching applications

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

Title:
  [Dell OptiPlex 755] Intermittently GUI hangs with high xorg CPU% after
  launching applications

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The problem is that after launching a few applications, the GUI may
  become unresponsive, although this is not consistently reproducible.
  When the GUI is unresponsive, it is corre

[Desktop-packages] [Bug 1757299] Re: [Dell OptiPlex 755] xorg hangs

gregrwm:

>"i am not asking for help."

If you are not expecting this bug to be fixed (i.e. not asking for a
developer to help), then feel free to mark this report Status Invalid.
Otherwise, please refrain from "smart alec" remarks, as it doesn't
motivate developers to want to fix bugs you report.

Despite this, allow me to clarify a previously asked question:
After reproducing the problem, if you SSH in and only kill processes that are 
not xorg, which processes do you have to kill until your GUI begins to be 
responsive again?

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

Title:
  [Dell OptiPlex 755] xorg hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The problem is that my GUI stops responding after launching a few
  applications, and is correlated to high CPU utilization of xorg.

  An example reproduction scenario:
  launched startx,
  launched an xterm via twm,
  launched another xterm via the first,
  launched tmux,
  launched firefox-esr, bluetooth-manager, and pavucontrol,
  maximized the xterm running tmux

  xorg stopped responding, ctl-alt-Fn don't respond either

  logged in via ssh, attached to tmux, launched htop, copied htop
  output, in which you can see xorg consuming lots of cpu.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog:
   Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
    * Starting AppArmor profiles   [160G
  [154G[ OK ]
    * Restoring resolver state...   [160G
  [154G[ OK ]
  CompositorRunning: None
  Date: Tue Mar 20 17:15:16 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Dell OptiPlex 755 [1028:0211]
     Subsystem: Dell OptiPlex 755 [1028:0211]
  JournalErrors:
   -- Logs begin at Fri 2018-02-23 08:59:47 CST, end at Tue 2018-03-20 17:14:39 
CDT. --
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="pci-_00_1b.0" card_name="alsa_card.pci-_00_1b.0" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
   Mar 20 17:01:37 hostname pulseaudio[1109]: [pulseaudio] pid.c: Daemon 
already running.
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 panic=30
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1757299/+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 1757299] Re: [Dell OptiPlex 755] xorg hangs

i am not asking for help.  this is a bug report.  i am reporting a bug.
if there is useful information i can gather i am happy to do so.

4) the steps in the description of this bug were performed in fairly
rapid succession, so several apps were busy starting up.  The lockup
occurred instantly after maximizing the xterm.  6) killing Xorg freed
the terminal.  3) it is not consistently reproducible.  Under xenial it
happens watching videos (Bug #1744429).  Since installing bionic, videos
haven't tripped it so far.  This bug report describes an occurrence that
didn't involve a video.

5) here is what htop looks like right after logging in, launching
startx, 2 xterms, and htop:

0  [ 0.0%] Tasks: 37; 1 running 
 [0/0]
1  [ 0.0%] Load average: 0.12 0.30 0.15 
 
Mem[   122M/1.90G] Time: 15:54:56   
 
Swp[ 0K/1.86G]  
 
  PID START USER   VIRT   RES  NI CPU%   TIME+  S Command   
 
1 15:51 root   155M  8996   1  0.0  0:01.92 S /sbin/init
 
  253 15:51 root  86576 18424   0  0.0  0:01.16 S 
/lib/systemd/systemd-journald  
  543 15:51 syslog 252M  4576   0  0.0  0:00.99 S /usr/sbin/rsyslogd -n 
 
  828 15:52 g  242M 23468   0  0.0  0:00.53 S /usr/lib/xorg/Xorg 
-nolisten tcp :0 vt1
  278 15:51 root  47348  5788   0  0.0  0:00.51 S 
/lib/systemd/systemd-udevd 
  549 15:51 root   280M  6952   0  0.0  0:00.12 S 
/usr/lib/accountsservice/accounts-daemon
  769 15:53 g 29276  7588   0  0.0  0:00.09 S -bash 
 
  980 15:54 root  61440  4228   0  0.0  0:00.09 S sudo -H -uG -s
 
  953 15:54 g 29308  7452   0  0.0  0:00.08 S -bash 
 
  893 15:52 g 28304  6432   0  0.0  0:00.06 S bash  
 
 1005 15:54 root  28136  6464   0  0.0  0:00.06 S /bin/bash 
 
  550 15:51 root   417M  9020   0  0.0  0:00.05 S /usr/sbin/ModemManager
 
  551 15:51 messagebu 50088  4664   0  0.0  0:00.05 S /usr/bin/dbus-daemon 
--system --address=
  871 15:52 g 86456 10504   0  0.0  0:00.05 S xterm 
 
  890 15:52 g 86456 10464   0  0.0  0:00.05 S xterm -bg black -fg white 
-rightbar -xrm
  834 15:52 g 46120  5524   0  0.0  0:00.04 S x-window-manager  
 
F1Help  F2Setup F3SearchF4FilterF5Tree  F6SortByF7Nice -F8Nice +F9Kill  F10Quit

here is what htop looks like while quiescent after several hours of use:

0  [|||  5.3%] Tasks: 55; 1 running 
  [0/0]
1  [|||  4.6%] Load average: 0.00 0.04 0.07 
  
Mem[||1.11G/1.90G] Time: 15:22:36   
  
Swp[ 0K/1.86G]  
  
  PID START USER   VIRT   RES  NI CPU%   TIME+  S Command   
  
 1231 07:07 g 2605M  707M   0  0.7 30:52.86 S 
/usr/lib/firefox-esr/plugin-container -gr
 1119 07:06 g 2385M  431M   0  7.3 12:13.72 S 
/usr/lib/firefox-esr/firefox-esr
  883 07:05 g  348M 54372   0  0.0  1:39.51 S /usr/lib/xorg/Xorg 
-nolisten tcp :0 vt1 -
 1051 07:06 g 1049M 10372 -11  0.0  1:31.19 S /usr/bin/pulseaudio 
--start --log-target=
 1027 07:06 g  535M 41720   0  0.0  1:10.72 S pavucontrol   
  
 1023 07:06 g  832M 58800   0  0.0  0:10.06 S /usr/bin/python3 
/usr/bin/blueman-manager
 1058 07:06 g 70784  6520   0  0.0  0:03.05 S xclock -geometry --1+-4 
-fg green -bg bla
1 06:51 root   155M  9016   0  0.0  0:02.93 S /sbin/init
  
  925 07:05 g 86456 10456   0  0.0  0:02.80 S xterm 
  
 2600 15:18 root  28044  5228   0  0.7  0:01.45 R htop  
  
  889 07:05 g 46120  5704   0  0.0  0:01.38 S x-window-manager  
  
  253 06:52 root  86568 16580   0  0.0  0:01.13 S 
/lib/systemd/systemd-journald   
  544 06:52 syslog 252M  4508   0  0.0  0:01.06 S /usr/sbin/rsyslogd -n 
  
  280 06:52 root  47580  5940   0  0.0  0:00.55 S 
/lib/systemd/systemd-udevd  
 1070 07:06 g  648M 51880   0  0.0  0:00.43 S /usr/bin/python3 
/usr/bin/blueman-applet
  518 06:52 root   280M  7192   0  0.0  0:00.41 S 
/usr/lib/accountsservice/accounts-daemon
F1Help  F2Setup F3SearchF4FilterF5Tree  F6SortByF7Nice -F8Nice +F9Kill  F10Quit

-- 
You received this bug notification because you are a m

[Desktop-packages] [Bug 1645485] Re: very old display driver bug?

gregrwm, the bug scoped to xorg hanging is handled in LP#1757299.

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

Title:
  very old display driver bug?

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  the most bothersome, most notable, and most curious symptom of this
  bug is the absolute degree to which the display locks up.  xclock's
  seconds are no longer changing, the mouse cursor won't move, and even
  ctl-alt-F1 does nothing.

  meanwhile mplayer, playing in a hidden tmux window, is still playing
  merrily along.

  i logged in via sshd and copied this from htop:
  0  [|100.0%] Tasks: 68; 3 running
  1  [|| 1.3%] Load average: 1.00 0.91 
0.53
  Mem[|973M/1.91G] Time: 14:26:17
  Swp[   0K/1.86G]
PID START USER   VIRT   RES  NI CPU%   TIME+  S Command
   1714 12:50 g 1713M  789M   0  0.0  6:37.92 S /usr/lib/firefox/firefox
   2368 14:07 g  661M 57252   0  0.0  0:03.33 S /usr/bin/python3 
/usr/bin/blueman-manager
794 12:49 root   269M 54988   0 99.3 10:12.88 R /usr/lib/xorg/Xorg 
-core :0 -seat seat0 -auth /var/
   2385 14:07 g  583M 53524   0  0.0  0:00.39 S /usr/bin/python3 
/usr/bin/blueman-applet
   2397 14:07 g  555M 42968   0  0.0  0:10.68 S pavucontrol
   1926 12:57 g  282M 37752   0  0.7  0:02.46 S 
/usr/lib/firefox/plugin-container /opt/google/talkp
   1933 12:57 g  512M 36404   0  0.0  0:02.96 S 
/opt/google/talkplugin/GoogleTalkPlugin
   2403 14:07 g  823M 30352   0  0.0  0:03.52 S mplayer -ao pulse -af 
channels=2 -framedrop -msgcol
  F1Help  F2Setup F3SearchF4FilterF5Tree  F6SortByF7Nice -F8Nice +F9Kill  
F10Quit

  ps also attached, taken before killing xorg.

  i've filed this under xorg merely because xorg is the one stuck eating
  all the CPU.  i really suspect the display driver, and don't know how
  to find or identify that.

  i much more commonly saw these very same symptoms when i used to run
  xscreensaver.  i stopped running xscreensaver just to stop beating my
  head against that wall.  but many years and many releases later, it
  looks like this display driver bug is still lurking around.

  there was hardly anything running when this froze.  i already
  mentioned mplayer (sound only) and tmux, twm's the window manager,
  firefox was running but iconized and idle tho running gmail and the
  googletalk plugin, not that i suspect any of them in any way.  xterm
  was occupying most of the screen, showing tmux, and idle.  the ones
  i'd more suspect would be xclock & pavucontrol.  pavucontrol was
  hidden but busily showing it's audio level bar, xclock was visible and
  displaying the time of day including seconds, so the most likely one
  to have tripped a display driver bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Nov 28 14:36:38 2016
  InstallationDate: Installed on 2016-10-15 (43 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645485/+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 1645485] Re: very old display driver bug?

when Xorg hangs but does not crash, as in this bug description, will a
manual kill of Xorg, perhaps with a certain signal, produce the crash
report you describe?

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

Title:
  very old display driver bug?

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  the most bothersome, most notable, and most curious symptom of this
  bug is the absolute degree to which the display locks up.  xclock's
  seconds are no longer changing, the mouse cursor won't move, and even
  ctl-alt-F1 does nothing.

  meanwhile mplayer, playing in a hidden tmux window, is still playing
  merrily along.

  i logged in via sshd and copied this from htop:
  0  [|100.0%] Tasks: 68; 3 running
  1  [|| 1.3%] Load average: 1.00 0.91 
0.53
  Mem[|973M/1.91G] Time: 14:26:17
  Swp[   0K/1.86G]
PID START USER   VIRT   RES  NI CPU%   TIME+  S Command
   1714 12:50 g 1713M  789M   0  0.0  6:37.92 S /usr/lib/firefox/firefox
   2368 14:07 g  661M 57252   0  0.0  0:03.33 S /usr/bin/python3 
/usr/bin/blueman-manager
794 12:49 root   269M 54988   0 99.3 10:12.88 R /usr/lib/xorg/Xorg 
-core :0 -seat seat0 -auth /var/
   2385 14:07 g  583M 53524   0  0.0  0:00.39 S /usr/bin/python3 
/usr/bin/blueman-applet
   2397 14:07 g  555M 42968   0  0.0  0:10.68 S pavucontrol
   1926 12:57 g  282M 37752   0  0.7  0:02.46 S 
/usr/lib/firefox/plugin-container /opt/google/talkp
   1933 12:57 g  512M 36404   0  0.0  0:02.96 S 
/opt/google/talkplugin/GoogleTalkPlugin
   2403 14:07 g  823M 30352   0  0.0  0:03.52 S mplayer -ao pulse -af 
channels=2 -framedrop -msgcol
  F1Help  F2Setup F3SearchF4FilterF5Tree  F6SortByF7Nice -F8Nice +F9Kill  
F10Quit

  ps also attached, taken before killing xorg.

  i've filed this under xorg merely because xorg is the one stuck eating
  all the CPU.  i really suspect the display driver, and don't know how
  to find or identify that.

  i much more commonly saw these very same symptoms when i used to run
  xscreensaver.  i stopped running xscreensaver just to stop beating my
  head against that wall.  but many years and many releases later, it
  looks like this display driver bug is still lurking around.

  there was hardly anything running when this froze.  i already
  mentioned mplayer (sound only) and tmux, twm's the window manager,
  firefox was running but iconized and idle tho running gmail and the
  googletalk plugin, not that i suspect any of them in any way.  xterm
  was occupying most of the screen, showing tmux, and idle.  the ones
  i'd more suspect would be xclock & pavucontrol.  pavucontrol was
  hidden but busily showing it's audio level bar, xclock was visible and
  displaying the time of day including seconds, so the most likely one
  to have tripped a display driver bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Nov 28 14:36:38 2016
  InstallationDate: Installed on 2016-10-15 (43 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645485/+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 1758163] Re: Please remove xchat-gnome from Ubuntu (again)

2018-03-23 Thread Dimitri John Ledkov

@mdeslaur there is polari, which is gtk3 and wayland compatible.

Note that we are not using wayland by default in 18.04.

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

Title:
  Please remove xchat-gnome from Ubuntu (again)

Status in xchat-gnome package in Ubuntu:
  Fix Released

Bug description:
  xchat-gnome is unmaintained.

  It was removed from Debian and Ubuntu 17.04. It was reintroduced to
  Ubuntu but without any real commitment to maintain the package.

  Its last upstream release was 9 years ago
  https://download.gnome.org/sources/xchat-gnome/0.26/

  The Ubuntu version is a bizarre mix up of a git snapshot and 37
  patches.

  Users would be better off switching to hexchat which is actually
  maintained.

  See also https://launchpad.net/bugs/1753169 for xchat, a somewhat
  different app with the same general problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/1758163/+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 1758472] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

** Tags removed: need-duplicate-check

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Turned on my laptop and this came up.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Mar 23 19:42:01 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-OOqAU8/13-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-03-18 (5 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1758472/+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 1758472] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

2018-03-23 Thread Literal Line

Public bug reported:

Turned on my laptop and this came up.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Mar 23 19:42:01 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-OOqAU8/13-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2018-03-18 (5 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Turned on my laptop and this came up.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Mar 23 19:42:01 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-OOqAU8/13-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-03-18 (5 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1758472/+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 1758467] [NEW] Update yelp* to 3.28.0

2018-03-23 Thread Jeremy Bicha

Public bug reported:

The Ubuntu Docs team requested that the new versions of yelp* stuff not
be updated to the 3.28 versions for Ubuntu 18.04 LTS. The new versions
have changes that will require rewriting of the rules used to generate
the html documentation for https://help.ubuntu.com/stable/ubuntu-help/

The desktop app yelp should have no compatibility problems.

Even if it takes some time to update those html rules, Ubuntu 18.04 LTS
can be used for a while to update the web site. It just would be
annoying to be stuck on 16.04 LTS for a while instead!

Therefore, I'm filing this tracking bug and setting the block-proposed
tag in case someone accidentally syncs the packages even though we're in
Freeze status for Ubuntu 18.04 LTS.

** Affects: yelp (Ubuntu)
 Importance: Wishlist
 Status: Triaged

** Affects: yelp-tools (Ubuntu)
 Importance: Wishlist
 Status: Triaged

** Affects: yelp-xsl (Ubuntu)
 Importance: Wishlist
 Status: Triaged


** Tags: block-proposed upgrade-software-version

** Also affects: yelp-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: yelp-tools (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: yelp-tools (Ubuntu)
   Status: New => Triaged

** Also affects: yelp (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: yelp (Ubuntu)
   Status: New => Triaged

** Changed in: yelp (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Update yelp* to 3.28.0

Status in yelp package in Ubuntu:
  Triaged
Status in yelp-tools package in Ubuntu:
  Triaged
Status in yelp-xsl package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Docs team requested that the new versions of yelp* stuff
  not be updated to the 3.28 versions for Ubuntu 18.04 LTS. The new
  versions have changes that will require rewriting of the rules used to
  generate the html documentation for https://help.ubuntu.com/stable
  /ubuntu-help/

  The desktop app yelp should have no compatibility problems.

  Even if it takes some time to update those html rules, Ubuntu 18.04
  LTS can be used for a while to update the web site. It just would be
  annoying to be stuck on 16.04 LTS for a while instead!

  Therefore, I'm filing this tracking bug and setting the block-proposed
  tag in case someone accidentally syncs the packages even though we're
  in Freeze status for Ubuntu 18.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1758467/+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 1758459] Re: Getting 2.93 in Bionic

2018-03-23 Thread eris23

A private tracker I belong to now requires 2.93 or above.

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

Title:
  Getting 2.93 in Bionic

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  As referenced on #1752940 some trackers have started blacklisting
  Transmission versions below 2.93 on the basis that they have no way of
  telling if an older version has been patched for CVE-2018-5702 or not.

  Can we try to get 2.93 in Bionic before the final freeze, especially
  since this is an LTS and 2.92 is starting to get old (Apr 9, 2016).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1758459/+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 1752153] Re: package bamfdaemon 0.5.3+17.10.20180208-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

2018-03-23 Thread Brian Murray

** Tags added: bot-stop-nagging

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

Title:
  package bamfdaemon 0.5.3+17.10.20180208-0ubuntu1 failed to
  install/upgrade: triggers looping, abandoned

Status in bamf package in Ubuntu:
  New

Bug description:
  after system login it crushes

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bamfdaemon 0.5.3+17.10.20180208-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Feb 20 04:05:13 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-08-14 (197 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: bamf
  Title: package bamfdaemon 0.5.3+17.10.20180208-0ubuntu1 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to artful on 2018-02-20 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1752153/+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 1758459] Re: Getting 2.93 in Bionic

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: transmission (Ubuntu)
   Status: New => Confirmed

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

Title:
  Getting 2.93 in Bionic

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  As referenced on #1752940 some trackers have started blacklisting
  Transmission versions below 2.93 on the basis that they have no way of
  telling if an older version has been patched for CVE-2018-5702 or not.

  Can we try to get 2.93 in Bionic before the final freeze, especially
  since this is an LTS and 2.92 is starting to get old (Apr 9, 2016).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1758459/+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 1747802] Re: Snapped applications launched from command line aren't properly matched

2018-03-23 Thread Treviño

** Tags removed: verification-failed-artful

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

Title:
  Snapped applications launched from command line aren't properly
  matched

Status in BAMF:
  Fix Committed
Status in bamf package in Ubuntu:
  Fix Released
Status in bamf source package in Xenial:
  Fix Released
Status in bamf source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Snapped applications non launched from their desktop file aren't
  properly matched by BAMF.

  [Test case]

  From terminal:
   1. snap install qml-hello-world
   2. qml-hello-world

  The application should start and the icon in the unity launcher should
  contain a Qt logo.

  [Regression Potential]

  Application with security profile might get a wrong desktop file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1747802/+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 1758458] [NEW] Bookmarks Toolbar Toggler Missing from View>Toolbars Menu

2018-03-23 Thread Lonnie Lee Best

Public bug reported:

In Ubuntu 18.04, running the unity desktop, Firefox 59's "View >
Taskbars" menu is missing "Bookmarks Tool bar".

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 59.0.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lonnie 5782 F pulseaudio
BuildID: 20180316161208
Channel: Unavailable
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri Mar 23 17:47:00 2018
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2018-02-09 (42 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
IpRoute:
 default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
 169.254.0.0/16 dev enp0s3 scope link metric 1000
IwConfig:
 enp0s3no wireless extensions.
 
 lono wireless extensions.
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=59.0.1/20180316161208 (In use)
RfKill:
 
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-bug bionic

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

Title:
  Bookmarks Toolbar Toggler Missing from View>Toolbars Menu

Status in firefox package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.04, running the unity desktop, Firefox 59's "View >
  Taskbars" menu is missing "Bookmarks Tool bar".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 59.0.1+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lonnie 5782 F pulseaudio
  BuildID: 20180316161208
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Mar 23 17:47:00 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-02-09 (42 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=59.0.1/20180316161208 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 1758459] [NEW] Getting 2.93 in Bionic

2018-03-23 Thread Schwert

Public bug reported:

As referenced on #1752940 some trackers have started blacklisting
Transmission versions below 2.93 on the basis that they have no way of
telling if an older version has been patched for CVE-2018-5702 or not.

Can we try to get 2.93 in Bionic before the final freeze, especially
since this is an LTS and 2.92 is starting to get old (Apr 9, 2016).

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

** Description changed:

  As referenced on #1752940 some trackers have started blacklisting
- Transmission version below 2.93 on the basis that they have no way of
+ Transmission versions below 2.93 on the basis that they have no way of
  telling if an older version has been patched for CVE-2018-5702 or not.
  
  Can we try to get 2.93 in Bionic before the final freeze, especially
  since this is an LTS and 2.92 is starting to get old (Apr 9, 2016).

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

Title:
  Getting 2.93 in Bionic

Status in transmission package in Ubuntu:
  New

Bug description:
  As referenced on #1752940 some trackers have started blacklisting
  Transmission versions below 2.93 on the basis that they have no way of
  telling if an older version has been patched for CVE-2018-5702 or not.

  Can we try to get 2.93 in Bionic before the final freeze, especially
  since this is an LTS and 2.92 is starting to get old (Apr 9, 2016).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1758459/+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 1758451] Re: gnome-shell crashed with signal 5

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1758451/+attachment/5088662/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1758451/+attachment/5088664/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1758451/+attachment/5088666/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1758451/+attachment/5088667/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1758451/+attachment/5088668/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758451/+attachment/5088669/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758451/+attachment/5088670/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Just rebooted the system, as a cold start

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar 23 14:52:21 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  JournalErrors:
   -- Logs begin at Thu 2018-03-22 16:10:06 PDT, end at Fri 2018-03-23 14:54:46 
PDT. --
   Mar 23 14:53:13 hostname kernel: [Firmware Bug]: AMD-Vi: IOAPIC[130] not in 
IVRS table
   Mar 23 14:53:13 hostname kernel: AMD-Vi: Disabling interrupt remapping
   Mar 23 14:53:17 hostname spice-vdagent[1464]: Cannot access vdagent virtio 
channel /dev/virtio-ports/com.redhat.spice.0
   Mar 23 14:53:41 hostname pulseaudio[1345]: [pulseaudio] bluez5-util.c: 
GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive 
a reply. Possible causes include: the remote application did not send a reply, 
the message bus security policy blocked the reply, the reply timeout expired, 
or the network connection was broken.
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758451/+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 1758450] [NEW] Should not hash apt.Cache

2018-03-23 Thread Julian Andres Klode

Public bug reported:

UbuntuDrivers should not hash the apt.Cache. It was accidentally broken
to be not-hashable as a side-effect, but it really should not be
hashable, so please fix it for the next cycle at least.

-   File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 145, in 
packages_for_modalias
- apt_cache_hash = hash(apt_cache)
- TypeError: unhashable type: 'Cache'


(hash is identical to id for the cache right now I guess)

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Should not hash apt.Cache

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  UbuntuDrivers should not hash the apt.Cache. It was accidentally
  broken to be not-hashable as a side-effect, but it really should not
  be hashable, so please fix it for the next cycle at least.

  -   File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 145, 
in packages_for_modalias
  - apt_cache_hash = hash(apt_cache)
  - TypeError: unhashable type: 'Cache'


  (hash is identical to id for the cache right now I guess)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1758450/+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 1747802] [bamf/artful] possible regression found

2018-03-23 Thread Ubuntu Foundations Team Bug Bot

As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of bamf from artful-proposed was
performed and bug 1752153 was found.  Please investigate this bug report
to ensure that a regression will not be created by this SRU. In the
event that this is not a regression remove the "verification-failed-
artful" tag from this bug report and add the tag "bot-stop-nagging" to
bug 1752153 (not this bug). Thanks!

** Tags added: verification-failed-artful

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

Title:
  Snapped applications launched from command line aren't properly
  matched

Status in BAMF:
  Fix Committed
Status in bamf package in Ubuntu:
  Fix Released
Status in bamf source package in Xenial:
  Fix Released
Status in bamf source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Snapped applications non launched from their desktop file aren't
  properly matched by BAMF.

  [Test case]

  From terminal:
   1. snap install qml-hello-world
   2. qml-hello-world

  The application should start and the icon in the unity launcher should
  contain a Qt logo.

  [Regression Potential]

  Application with security profile might get a wrong desktop file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1747802/+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 1758430] Re: gnome-control-center crashed with SIGABRT in g_slice_free1()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1738239, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1758430/+attachment/5088561/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1758430/+attachment/5088563/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1758430/+attachment/5088566/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1758430/+attachment/5088567/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1758430/+attachment/5088568/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758430/+attachment/5088569/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758430/+attachment/5088570/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1738239

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGABRT in g_slice_free1()

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Crashed during printer installation process

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 21:34:55 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGABRT in g_slice_free1()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758430/+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 1755514] Re: Clicking the "Additional Printer Settings…" button launches system-config-printer multiple times

2018-03-23 Thread Jeremy Bicha

** Tags added: rls-bb-incoming

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

Title:
  Clicking the "Additional Printer Settings…" button launches system-
  config-printer multiple times

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  Clicking the "Additional Printer Settings…" button in GNOME Control
  Center launches multiple instances of system-config-printer instead of
  one instance in Ubuntu 18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1755514/+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 1755514] Re: Clicking the "Additional Printer Settings…" button launches system-config-printer multiple times

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: system-config-printer (Ubuntu)
   Status: New => Confirmed

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

Title:
  Clicking the "Additional Printer Settings…" button launches system-
  config-printer multiple times

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  Clicking the "Additional Printer Settings…" button in GNOME Control
  Center launches multiple instances of system-config-printer instead of
  one instance in Ubuntu 18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1755514/+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 1755514] Re: Clicking the "Additional Printer Settings…" button launches system-config-printer multiple times

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  Clicking the "Additional Printer Settings…" button launches system-
  config-printer multiple times

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  Clicking the "Additional Printer Settings…" button in GNOME Control
  Center launches multiple instances of system-config-printer instead of
  one instance in Ubuntu 18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1755514/+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 1758415] [NEW] Ubuntu 16.06 x64

2018-03-23 Thread Nurettin BAYRAKTAR

Public bug reported:

Ubuntu 16.06 x64

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Mar 23 22:25:49 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.4.0-116-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-62-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1626] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Broadwell-U Integrated Graphics [106b:011b]
InstallationDate: Installed on 2018-03-13 (10 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
LightdmDisplayLog:
 The XKEYBOARD keymap compiler (xkbcomp) reports:
 > Warning:  Type "ONE_LEVEL" has 1 levels, but  has 2 symbols
 >   Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
MachineType: Apple Inc. MacBookAir7,2
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=928e15c4-d7b7-4916-b151-52dbad72476a ro
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/05/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA71.88Z.0166.B06.1506051511
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-937CB26E2E02BB01
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir7,2
dmi.chassis.asset.tag: Chassis Board Asset Tag#
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-937CB26E2E02BB01
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA71.88Z.0166.B06.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookAir7,2:pvr1.0:rvnAppleInc.:rnMac-937CB26E2E02BB01:rvrMacBookAir7,2:cvnAppleInc.:ct9:cvrMac-937CB26E2E02BB01:
dmi.product.name: MacBookAir7,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Mar 23 22:13:44 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   40176 
 vendor APP
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu 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/1758415

Title:
  Ubuntu 16.06 x64

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 16.06 x64

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar 23 22:25:49 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-116-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-62-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1626] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Broadwell-U Integrated Graphics [106b:011b]
  InstallationDate: Installed on 2018-03-13 (10 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  LightdmDisplayLog:
   The XKEYBOARD keymap compiler (xkb

[Desktop-packages] [Bug 1755514] Re: Clicking the "Additional Printer Settings…" button launches system-config-printer multiple times

2018-03-23 Thread AsciiWolf

It looks like it's 7 instances every time.

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

Title:
  Clicking the "Additional Printer Settings…" button launches system-
  config-printer multiple times

Status in gnome-control-center package in Ubuntu:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  Clicking the "Additional Printer Settings…" button in GNOME Control
  Center launches multiple instances of system-config-printer instead of
  one instance in Ubuntu 18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1755514/+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 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

2018-03-23 Thread herrtimson

Ubuntu builds firefox for trusty with g++-4.9 , I checked this on amd64
some time ago and the build logs tell me that the armhf toolchain is as
well g++-4.9

 0:08.79 checking for the target C++ compiler... 
/<>/firefox-59.0.1+build1/debian/gcc-mozilla/g++
 0:08.90 checking whether the target C++ compiler can be used... yes
 0:08.90 checking the target C++ compiler version... 4.9.4
 0:08.98 checking the target C++ compiler works... yes
 0:08.98 checking for the host C compiler... 
/<>/firefox-59.0.1+build1/debian/gcc-mozilla/gcc
 0:09.04 checking whether the host C compiler can be used... yes
 0:09.04 checking the host C compiler version... 4.9.4
 0:09.11 checking the host C compiler works... yes
 0:09.11 checking for the host C++ compiler... 
/<>/firefox-59.0.1+build1/debian/gcc-mozilla/g++
 0:09.18 checking whether the host C++ compiler can be used... yes
 0:09.18 checking the host C++ compiler version... 4.9.4
 0:09.25 checking the host C++ compiler works... yes

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.10.1 dev eth0 
   default via 192.168.10.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108  
metric 600
  Locales: extensions.sqlite corrupt or missing
  PciMultimedia:
   
  PciNetwork:
   
  Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1711337/+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 1754356] Re: xdg-user-dirs-update does not take care of $HOME

This bug was fixed in the package xdg-user-dirs - 0.17-1ubuntu1

---
xdg-user-dirs (0.17-1ubuntu1) bionic; urgency=low

  * Merge with Debian. Remaining change:
- Add launchpad_translation_export.patch:
  + update translations from Launchpad
  * Fixes xdg-user-dirs-update not respecting $HOME (LP: #1754356), thanks
Trevinho.

xdg-user-dirs (0.17-1) unstable; urgency=medium

  * New upstream release (LP: #1754356)
  * Update Vcs fields for migration to https://salsa.debian.org/

xdg-user-dirs (0.16-1) unstable; urgency=medium

  * New upstream release
  * Drop 01_add-autostart-file.patch: Applied in new release
  * Update Vcs fields for conversion to git
  * Add debian/gbp.conf
  * Bump Standards-Version to 4.1.2
  * Bump debhelper compat to 11

 -- Iain Lane   Fri, 23 Mar 2018 15:58:57 +

** Changed in: xdg-user-dirs (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  xdg-user-dirs-update does not take care of $HOME

Status in xdg-user-dirs package in Ubuntu:
  Fix Released
Status in xdg-user-dirs source package in Xenial:
  In Progress

Bug description:
  [ Impact ]

  When setting an user dir to a folder that is subfolder of $HOME (and
  when $HOME does not match the /etc/passwd defined home for the user),
  the ~/.config/user-dirs.dirs is wrongly generated.

  [ Test case ]

   1) env HOME=/tmp/temp-home xdg-user-dirs-update
   2) find /tmp/temp-home/
   3) should list generated XDG user directories
   4) /tmp/temp-home/.config/user-dirs.dirs should mention them

  Launching something like:
   - env HOME=/tmp/temp-home ./xdg-user-dirs-update --set DOWNLOADS 
"/tmp/temp-home/sub/folder/of/it/Downloads"

  Should modify /tmp/temp-home/.config/user-dirs.dirs so that it contains:
XDG_DOWNLOADS_DIR="$HOME/sub/folder/of/it/Downloads"

  [ Regression potential ]

  Xdg folders could be generated in wrong locations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1754356/+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 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed

2018-03-23 Thread yusuf okçulu

** Information type changed from Public to Public Security

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

** Information type changed from Public Security to Private

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

Title:
  cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be
  installed

Status in cups package in Ubuntu:
  Fix Released

Bug description:
  This is related to this bug
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790

  After `sudo apt-get -f install`, it removed cups and marked a bunch of
  cups packages as unnecessary

  `sudo apt-get autoremove` removed them.

  Now when I try to re-install cups, I get this error:

  ```
  ☀  sudo apt-get install cups cups-daemon cups-core-drivers
  Mod master
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed
  Depends: libcupscgi1 (>= 1.4.2) but it is not going to be installed
  Depends: libcupsmime1 (>= 1.4.0) but it is not going to be installed
  Recommends: printer-driver-gutenprint but it is not going to be 
installed
   cups-core-drivers : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to 
be installed
   cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be 
installed
 Depends: libcupsmime1 (>= 1.5.0) but it is not going to be 
installed
 Recommends: cups-browsed but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676621/+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 1757030] Re: Lite-On DS8A1H Slimline fails to record dual layer DVD+R

2018-03-23 Thread Thomas Schmitt

Hi,

> Is there a way to place a DVD burner into simulation mode as with CD
> recording so as to test the commands without wasting the disc?

Not with DVD+R and DVD+R DL, i fear.
Only DVD-R and unformatted DVD-RW can simulate.


> nodao.log

Now that's a short one.
It can hardly be that growisofs issues a wrong command here. At most
there can be something missing.

It tries to learn some info about the medium, is convinced that it is
a blank DVD+R DL, and begins to write.
The first WRITE(10) command needs 72 seconds to fail.

  WRITE(10)
  2a 00 00 00 00 00 00 00 10 00 
  ...
  +++ key=5  asc=21h  ascq=04h   ( 72020 ms)
  :-[ WRITE@LBA=0h failed with SK=5h/ASC=21h/ACQ=04h]: Invalid argument

Neither SPC-3 nor MMC-5 specifies this code. Its neighbors are
  5 21 00 LOGICAL BLOCK ADDRESS OUT OF RANGE
  5 21 01 INVALID ELEMENT ADDRESS
  5 21 02 INVALID ADDRESS FOR WRITE
  5 21 03 INVALID WRITE CROSSING LAYER JUMP

I.e. the drive does not like the write target address. But this might
be just a consequence of the drive or bus reset.


> dao.log

This seems to have succeeded.

But the image was much smaller than in your original run.

  /dev/dvdrw: splitting layers at 1167120 blocks

  (NOT IN COMMAND LIST)
  bf 00 00 00 00 00 00 20 00 0c 00 00 
  To drive: 12b
  00 0a 00 00 00 00 00 00 00 11 cf 10 
   91120 ms

Command code 0xBF is "SEND DISC STRUCTURE". I should add it to the list
in the patch.
Does this really last 92 seconds ?

  WRITE(10)
  2a 00 00 23 9e 00 00 00 10 00 
   8 ms
  /dev/dvdrw: flushing cache

  SYNCHRONIZE CACHE
  35 02 00 00 00 00 00 00 00 00 
   0 ms

The last WRITE(10) command wrote up to block 0x239e00 + 15 = 2334223.
So the total size is 2334224, which divided by 2 is 1167112.
So growisofs rounded up the layer break position by 8 blocks.

In the original run, the block count was 8231090176 / 2048 = 4019087.
Divided by 2: 2009543.5 . "splitting layers at 2009552 blocks" means
that growisofs rounded up by 8.5 blocks.

-

This still gives me no idea what growisofs might do wrong.
The nodao.log is quite what i would expect from xorrecord -tao, too.

If you find reason to burn a DVD+R DL with xorrecord, then you could use
option -V and post the log here.
You may then omit the legthy sequences of WRITE(10) and READ BUFFER CAPACITY.
It suffices to show the first few WRITE(10) and the last few WRITE(10)
together with the other commands before and after the WRITE(10) flood.


Have a nice day :)

Thomas

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

Title:
  Lite-On DS8A1H Slimline fails to record dual layer DVD+R

Status in dvd+rw-tools package in Ubuntu:
  New

Bug description:
  I tried Verbatim 8x and 2.4x DVD+R DL.  The failure is always exactly
  the same.

  $ growisofs -dvd-compat -Z /dev/dvdrw=2017.iso
  Executing 'builtin_dd if=2017.iso of=/dev/dvdrw obs=32k seek=0'
  /dev/dvdrw: splitting layers at 2009552 blocks
  /dev/dvdrw: "Current Write Speed" is 1.6x1352KBps.
  9175040/8231090176 ( 0.1%) @2.0x, remaining 74:40 RBU 100.0% UBU   7.4%
 21135360/8231090176 ( 0.3%) @2.6x, remaining 58:16 RBU 100.0% UBU  98.8%
 33095680/8231090176 ( 0.4%) @2.6x, remaining 49:32 RBU 100.0% UBU  98.6%
 45056000/8231090176 ( 0.5%) @2.6x, remaining 45:25 RBU 100.0% UBU  98.8%
 57016320/8231090176 ( 0.7%) @2.6x, remaining 45:23 RBU 100.0% UBU  98.8%
 69009408/8231090176 ( 0.8%) @2.6x, remaining 43:22 RBU 100.0% UBU  98.8%
 80969728/8231090176 ( 1.0%) @2.6x, remaining 41:56 RBU 100.0% UBU  98.6%
 92930048/8231090176 ( 1.1%) @2.6x, remaining 42:19 RBU 100.0% UBU  98.6%
  [..]
   4077289472/8231090176 (49.5%) @4.1x, remaining 15:15 RBU  90.0% UBU  88.4%
   4096065536/8231090176 (49.8%) @4.1x, remaining 15:11 RBU  43.0% UBU  97.9%
   4114808832/8231090176 (50.0%) @4.1x, remaining 15:06 RBU  28.0% UBU  97.9%
   4115562496/8231090176 (50.0%) @0.2x, remaining 15:08 RBU  69.4% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:12 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:15 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:18 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:22 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:25 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:28 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:32 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:35 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:38 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:42 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:45 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:48 R

[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time

2018-03-23 Thread Alex

I think my report is related:
https://bugzilla.gnome.org/show_bug.cgi?id=787983

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

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

Title:
  gnome-shell uses lots of memory, and grows over time

Status in GNOME Shell:
  Confirmed
Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
  almost 2 GiB.

  user  3039  1.8 16.1 4302340 1968476 tty2  Sl+  Mar09 120:17
  /usr/bin/gnome-shell

  strace output is voluminous; here is a representative sample:

  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\231\n\10\0\n\0 
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0 
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  open("/proc/self/stat", O_RDONLY)   = 36
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  fcntl(36, F_GETFL)  = 0x8000 (flags O_RDONLY|O_LARGEFILE)
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
  read(36, "", 3072)  = 0
  close(36)   = 0
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) = 
1 ([{fd=4, revents=POLLIN}])
  read(4, "\1\0\0\0\0\0\0\0", 16) = 8
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, {msg_name(0)=NULL, 
msg_iov(1)=[{"[\2\327&h\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}

[Desktop-packages] [Bug 1757299] Re: [Dell OptiPlex 755] xorg hangs

gregrwm, in order to help you, please review all of the following, and
answer all questions:

1) Regarding all the reports you mentioned, they are useless as they
don't contain useful information to root cause and solve. Hence, it is
most helpful if you keep focus on this one report, versus making new
reports, or constantly referencing others.

2) Please don't apport-collect or attach more apport-collect files.

3) Regarding the Bug Description, is this consistently reproducible
using your steps?

4) Regarding the Bug Description, how long does it take from "maximized
the xterm running tmux" to your GUI stops responding, seconds, minutes,
etc.?

5) Immediately after logging in, without doing anything else what is the
idle CPU utilization (htop results)?

6) After reproducing the problem, if you SSH in and kill processes,
which processes do you have to kill until your GUI begins to be
responsive again?

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

** Description changed:

+ The problem is that my GUI stops responding after launching a few
+ applications, and is correlated to high CPU utilization of xorg.
+ 
+ An example reproduction scenario:
  launched startx,
  launched an xterm via twm,
  launched another xterm via the first,
  launched tmux,
  launched firefox-esr, bluetooth-manager, and pavucontrol,
  maximized the xterm running tmux
  
  xorg stopped responding, ctl-alt-Fn don't respond either
  
- logged in via ssh, attached to tmux, launched htop, copied htop output, in 
which you can see xorg consuming lots of cpu.
- noticed twm no longer running
- launched ubuntu-bug xserver-xorg
- answered its question re display manager log files
- i left it printing endless periods for over an hour
- 
- killed xorg
- launched startx again
- started a second ubuntu-bug xserver-xorg
- answered its questions re display manager log files and additional debugging 
work
- 
- noticed the first ubuntu-bug xserver-xorg is no longer printing periods
- answered its questions re additional debugging work and Send problem report
- 
- attached copy of htop output
+ logged in via ssh, attached to tmux, launched htop, copied htop output,
+ in which you can see xorg consuming lots of cpu.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog:
-  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
-   * Starting AppArmor profiles   [160G 
+  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
+   * Starting AppArmor profiles   [160G
  [154G[ OK ]
-   * Restoring resolver state...   [160G 
+   * Restoring resolver state...   [160G
  [154G[ OK ]
  CompositorRunning: None
  Date: Tue Mar 20 17:15:16 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
-Subsystem: Dell OptiPlex 755 [1028:0211]
-Subsystem: Dell OptiPlex 755 [1028:0211]
+  Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
+    Subsystem: Dell OptiPlex 755 [1028:0211]
+    Subsystem: Dell OptiPlex 755 [1028:0211]
  JournalErrors:
-  -- Logs begin at Fri 2018-02-23 08:59:47 CST, end at Tue 2018-03-20 17:14:39 
CDT. --
-  Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
-  Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="pci-_00_1b.0" card_name="alsa_card.pci-_00_1b.0" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
-  Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
-  Mar 20 17:01:37 hostname pulseaudio[1109]: [pulseaudio] pid.c: Daemon 
already running.
+  -- Logs begin at Fri 2018-02-23 08:59:47 CST, end at Tue 2018-03-20 17:14:39 
CDT. --
+  Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
+  Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="pci-_00_1b.0" card_name="alsa_card.pci-_00_1b.0" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization f

[Desktop-packages] [Bug 1758408] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1754924, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1758408/+attachment/5088477/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1758408/+attachment/5088479/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1758408/+attachment/5088483/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1758408/+attachment/5088484/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1758408/+attachment/5088485/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758408/+attachment/5088486/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758408/+attachment/5088487/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1754924
   gnome-control-center crashed with SIGSEGV in actualize_printers_list()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 19:01:52 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-08 (15 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x55e818eea3d1:mov0x90(%rbp),%rsi
   PC (0x55e818eea3d1) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758408/+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 1758107] Re: View > Toolbars is Missing "Bookmarks Toolbar"

2018-03-23 Thread Lonnie Lee Best

Also see: https://askubuntu.com/questions/1015697/firefox-bookmarks-
toolbar-option-is-missing

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

Title:
  View > Toolbars is Missing "Bookmarks Toolbar"

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  The "Bookmarks Toolbar" toggler is missing from the View > Toolbars
  menu in Firefox 59 on Ubuntu 16.04.4.

  Video:
  https://youtu.be/Josm0VqtUDQ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 59.0.1+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lonnie 1902 F pulseaudio
   /dev/snd/pcmC0D0p:   lonnie 1902 F...m pulseaudio
   /dev/snd/controlC0:  lonnie 1902 F pulseaudio
  BuildID: 20180316021607
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Thu Mar 22 11:42:51 2018
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-02-09 (41 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.77.1 dev enp3s0  proto static  metric 100 
   169.254.0.0/16 dev enp3s0  scope link  metric 1000 
   192.168.77.0/24 dev enp3s0  proto kernel  scope link  src 192.168.77.252  
metric 100
  NoProfiles: True
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv8 Notebook PC
  dmi.product.version: 04992224121000104
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1758107/+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 1744429] Re: [Dell OptiPlex 755] PC freezes while playing vlc or youtube

gregrwm, this report is being closed given you updated to Bionic, and
you have not advised to further occurrences with either VLC or Firefox.

However, please focus your efforts on one bug/report (LP#1757299) so
that it may be root caused and solved, versus commenting across multiple
reports, or making new reports about potentially the same issue. Doing
this causes confusion, and delays your issue being resolved.

Thank you for your understanding.

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [Dell OptiPlex 755] PC freezes while playing vlc or youtube

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  When watching youtube or vlc, xorg CPU utilization increases, until
  overall CPU utilization pegs at 100%. The sound plays on a bit further
  and then stops. The mouse can move the cursor but cannot interact with
  anything.

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Dell OptiPlex 755 [1028:0211]
     Subsystem: Dell OptiPlex 755 [1028:0211]
  InstallationDate: Installed on 2016-10-15 (478 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: Dell Inc. OptiPlex 755
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=31a5bed5-4d43-4da3-a094-17c3f23ae8b1 panic=30
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1744429/+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 1757299] Re: [Dell OptiPlex 755] xorg hangs

** Summary changed:

- xorg hangs
+ [Dell OptiPlex 755] xorg hangs

** Tags added: bios-outdated-a22

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

Title:
  [Dell OptiPlex 755] xorg hangs

Status in xorg package in Ubuntu:
  New

Bug description:
  launched startx,
  launched an xterm via twm,
  launched another xterm via the first,
  launched tmux,
  launched firefox-esr, bluetooth-manager, and pavucontrol,
  maximized the xterm running tmux

  xorg stopped responding, ctl-alt-Fn don't respond either

  logged in via ssh, attached to tmux, launched htop, copied htop output, in 
which you can see xorg consuming lots of cpu.
  noticed twm no longer running
  launched ubuntu-bug xserver-xorg
  answered its question re display manager log files
  i left it printing endless periods for over an hour

  killed xorg
  launched startx again
  started a second ubuntu-bug xserver-xorg
  answered its questions re display manager log files and additional debugging 
work

  noticed the first ubuntu-bug xserver-xorg is no longer printing periods
  answered its questions re additional debugging work and Send problem report

  attached copy of htop output

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog:
   Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
* Starting AppArmor profiles   [160G 
[154G[ OK ]
* Restoring resolver state...   [160G 
[154G[ OK ]
  CompositorRunning: None
  Date: Tue Mar 20 17:15:16 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell OptiPlex 755 [1028:0211]
 Subsystem: Dell OptiPlex 755 [1028:0211]
  JournalErrors:
   -- Logs begin at Fri 2018-02-23 08:59:47 CST, end at Tue 2018-03-20 17:14:39 
CDT. --
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="pci-_00_1b.0" card_name="alsa_card.pci-_00_1b.0" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
   Mar 20 17:01:37 hostname pulseaudio[1109]: [pulseaudio] pid.c: Daemon 
already running.
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 panic=30
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1757299/+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 1290797] Re: longstanding display driver bug elicited by xscreensaver or lightdm or chvt

gregrwm, reviewing your attachment, it is noticed that your crash report
is manually attached.

Please follow these instructions to have apport report a new bug against your
crash file that can be dealt with by the automatic retracer. First, execute at
a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y
dist-upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in
/etc/default/apport and restart. Now reproduce the crash, then open a terminal,
navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By
default, this sends the crash to the Ubuntu Error Tracker
infrastructure, which is different than Launchpad. For more on this,
please see https://wiki.ubuntu.com/ErrorTracker .

However, this report is being closed since the process outlined above
will deal with this issue more efficiently.

Also, please do not attach your crash report manually to this report and
reopen it.

Thank you for your help.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Changed in: xorg (Ubuntu)
Importance: Low => Undecided

** Changed in: xorg (Ubuntu)
Status: Expired => Invalid

** Attachment removed: "zip.zip"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1290797/+attachment/4018029/+files/zip.zip

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

Title:
longstanding display driver bug elicited by xscreensaver or lightdm or
chvt

Status in xorg package in Ubuntu:
Invalid

Bug description:
i've been hitting this bug since natty or earlier. today, as per
usual, the evidence of the bug is that chvt no longer functions
normally. in today's case, two instances of xorg had been running,
both crashed, xorg would not relaunch (immediately crashed again)(tho
no trouble launching Xvnc), after the xorg crashes ctl-alt-F7 shows:
"The system is running in low-graphics mode", ctl-alt-F8 shows all
black, and the clear clue, ctl-alt-F1 shows the text you would expect
to see there, but at the same time the mouse cursor is still being
displayed and responding to mouse movement as if we were still looking
at ctl-alt-F[78]! same for ctl-alt-F[2-6]. when i hit this same bug
on other days, the behaviour of ctl-alt-Fn will be peculiar in unique
bizarre ways.

i tried to submit this bug via ubuntu-bug (in 2 or 3 "screen" windows,
then killed them all, then tried one more time), then zipped up the
apport log, the Xorg logs, the single /var/crash/*Xorg* i found, and a
process list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1290797/+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 1758399] Re: gnome-software crashed with SIGSEGV in g_io_channel_shutdown()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1757932, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1758399/+attachment/5088420/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1758399/+attachment/5088422/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1758399/+attachment/5088425/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1758399/+attachment/5088426/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1758399/+attachment/5088427/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758399/+attachment/5088428/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758399/+attachment/5088429/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1757932

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-software crashed with SIGSEGV in g_io_channel_shutdown()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Not sure whether or not it is a duplicate to #1722185, crashed while
  installing programms

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 18:18:20 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f5bfa83f76f :cmpq   
$0x0,0x8(%rdi)
   PC (0x7f5bfa83f76f) ok
   source "$0x0" ok
   destination "0x8(%rdi)" (0xf70627f40008) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   g_io_channel_shutdown () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-software crashed with SIGSEGV in g_io_channel_shutdown()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1758399/+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 1645485] Re: very old display driver bug?

gregrwm, reviewing your attachments, your crash report is missing, and
no useful information is provided to root cause this problem.

Please follow these instructions to have apport report a new bug against your 
crash file that can be dealt with by the automatic retracer. First, execute at 
a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y 
dist-upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in 
/etc/default/apport and restart. Now reproduce the crash, then open a terminal, 
navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By
default, this sends the crash to the Ubuntu Error Tracker
infrastructure, which is different than Launchpad. For more on this,
please see https://wiki.ubuntu.com/ErrorTracker .

However, this report is being closed since the process outlined above
will deal with this issue more efficiently.

Also, please do not attach your crash report manually to this report and
reopen it.

Thank you for your help.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

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

Title:
  very old display driver bug?

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  the most bothersome, most notable, and most curious symptom of this
  bug is the absolute degree to which the display locks up.  xclock's
  seconds are no longer changing, the mouse cursor won't move, and even
  ctl-alt-F1 does nothing.

  meanwhile mplayer, playing in a hidden tmux window, is still playing
  merrily along.

  i logged in via sshd and copied this from htop:
  0  [|100.0%] Tasks: 68; 3 running
  1  [|| 1.3%] Load average: 1.00 0.91 
0.53
  Mem[|973M/1.91G] Time: 14:26:17
  Swp[   0K/1.86G]
PID START USER   VIRT   RES  NI CPU%   TIME+  S Command
   1714 12:50 g 1713M  789M   0  0.0  6:37.92 S /usr/lib/firefox/firefox
   2368 14:07 g  661M 57252   0  0.0  0:03.33 S /usr/bin/python3 
/usr/bin/blueman-manager
794 12:49 root   269M 54988   0 99.3 10:12.88 R /usr/lib/xorg/Xorg 
-core :0 -seat seat0 -auth /var/
   2385 14:07 g  583M 53524   0  0.0  0:00.39 S /usr/bin/python3 
/usr/bin/blueman-applet
   2397 14:07 g  555M 42968   0  0.0  0:10.68 S pavucontrol
   1926 12:57 g  282M 37752   0  0.7  0:02.46 S 
/usr/lib/firefox/plugin-container /opt/google/talkp
   1933 12:57 g  512M 36404   0  0.0  0:02.96 S 
/opt/google/talkplugin/GoogleTalkPlugin
   2403 14:07 g  823M 30352   0  0.0  0:03.52 S mplayer -ao pulse -af 
channels=2 -framedrop -msgcol
  F1Help  F2Setup F3SearchF4FilterF5Tree  F6SortByF7Nice -F8Nice +F9Kill  
F10Quit

  ps also attached, taken before killing xorg.

  i've filed this under xorg merely because xorg is the one stuck eating
  all the CPU.  i really suspect the display driver, and don't know how
  to find or identify that.

  i much more commonly saw these very same symptoms when i used to run
  xscreensaver.  i stopped running xscreensaver just to stop beating my
  head against that wall.  but many years and many releases later, it
  looks like this display driver bug is still lurking around.

  there was hardly anything running when this froze.  i already
  mentioned mplayer (sound only) and tmux, twm's the window manager,
  firefox was running but iconized and idle tho running gmail and the
  googletalk plugin, not that i suspect any of them in any way.  xterm
  was occupying most of the screen, showing tmux, and idle.  the ones
  i'd more suspect would be xclock & pavucontrol.  pavucontrol was
  hidden but busily showing it's audio level bar, xclock was visible and
  displaying the time of day including seconds, so the most likely one
  to have tripped a display driver bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Nov 28 14:36:38 2016
  InstallationDate: Installed on 2016-10-15 (43 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1758401] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in __strrchr_avx2()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1755017, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1758401/+attachment/5088441/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1758401/+attachment/5088443/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1758401/+attachment/5088446/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1758401/+attachment/5088447/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1758401/+attachment/5088448/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758401/+attachment/5088449/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758401/+attachment/5088450/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1755017

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  usb_modeswitch_dispatcher crashed with SIGSEGV in __strrchr_avx2()

Status in usb-modeswitch package in Ubuntu:
  New

Bug description:
  Fails just after boot

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: usb-modeswitch 2.5.2+repack0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Mar 23 18:23:59 2018
  ExecutablePath: /usr/sbin/usb_modeswitch_dispatcher
  InstallationDate: Installed on 2017-10-24 (150 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/sbin/usb_modeswitch_dispatcher --switch-mode 1-6
  ProcEnviron:
   LANG=da_DK.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f0b5a8103d7 <__strrchr_avx2+23>:vmovdqu 
(%rdi),%ymm1
   PC (0x7f0b5a8103d7) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ymm1" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: usb-modeswitch
  StacktraceTop:
   __strrchr_avx2 () at ../sysdeps/x86_64/multiarch/strrchr-avx2.S:54
   ?? ()
   __libc_start_main (main=0x55fdac1dcb70, argc=3, argv=0x7ffd358ee5d8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd358ee5c8) at ../csu/libc-start.c:310
   ?? ()
  Title: usb_modeswitch_dispatcher crashed with SIGSEGV in __strrchr_avx2()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1758401/+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 1511244] Re: Mouse pointer flickers at using DisplayLink

** Description changed:

- Using the new official DisplayLink driver for Ubuntu from
- http://www.displaylink.com/downloads/ubuntu.php for my USB-DisplayLink-
- Adapter causes on the two main monitors (DisplayPort and internal
- monitor) a flickering mouse. The pointer doesn't flicker on third
- monitor (DisplayLink monitor).
+ I have a three screen setup, the built-in laptop screen, a monitor
+ connected directly into the laptop via DisplayPort, and a monitor
+ connected via a USB DisplayLink Adapter.
  
- This also seems to be related to this bug:
- https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1485682
+ What happens is that when a monitor is connected via the USB DisplayLink
+ Adapter, the mouse icon flickers only on the laptop screen and monitor
+ connected via DisplayPort (not on the monitor connected via USB
+ DisplayLink Adapter).
+ 
+ However, this is also reproducible if I either deactivate the built-in
+ laptop screen, or disconnect the DisplayPort connected monitor.
+ 
+ WORKAROUND: Disconnect the USB DisplayLink Adapter for the computer.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Oct 29 08:29:50 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
-Subsystem: Lenovo Device [17aa:503c]
+  Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
+    Subsystem: Lenovo Device [17aa:503c]
  InstallationDate: Installed on 2015-09-25 (33 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: LENOVO 20DT0003GE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic 
root=UUID=500f2ef6-7426-42ec-9fe2-88e9bcea ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET50WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET50WW(1.12):bd03/25/2015:svnLENOVO:pn20DT0003GE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT0003GE
  dmi.product.version: ThinkPad L450
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Oct 29 07:45:59 2015
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id9782 
-  vendor ENC
+  product id9782
+  vendor ENC
  xserver.version: 2:1.15.1-0ubuntu2.7

** Changed in: xorg (Ubuntu)
   Importance: Medium => Low

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

Title:
  Mouse pointer flickers at using DisplayLink

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have a three screen setup, the built-in laptop screen, a monitor
  connected directly into the laptop via DisplayPort, and a monitor
  connected v

[Desktop-packages] [Bug 1758391] Re: remmina crashed with SIGSEGV in InterlockedIncrement()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1751324, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1758391/+attachment/5088400/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1758391/+attachment/5088402/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1758391/+attachment/5088406/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1758391/+attachment/5088407/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1758391/+attachment/5088408/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758391/+attachment/5088409/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758391/+attachment/5088410/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1751324

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  remmina crashed with SIGSEGV in InterlockedIncrement()

Status in remmina package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: remmina 1.2.0-rcgit.27+dfsg-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 22:10:51 2018
  ExecutablePath: /usr/bin/remmina
  InstallationDate: Installed on 2016-01-08 (805 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/remmina
  SegvAnalysis:
   Segfault happened at: 0x7f0fe987eda5 :   lock 
xadd %eax,(%rdi)
   PC (0x7f0fe987eda5) ok
   source "%eax" ok
   destination "(%rdi)" (0x0020) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: remmina
  StacktraceTop:
   InterlockedIncrement () at /usr/lib/x86_64-linux-gnu/libwinpr2.so.2
   EnterCriticalSection () at /usr/lib/x86_64-linux-gnu/libwinpr2.so.2
   MessageQueue_Dispatch () at /usr/lib/x86_64-linux-gnu/libwinpr2.so.2
   MessageQueue_Post () at /usr/lib/x86_64-linux-gnu/libwinpr2.so.2
   () at /usr/lib/x86_64-linux-gnu/libfreerdp-client2.so.2
  Title: remmina crashed with SIGSEGV in InterlockedIncrement()
  UpgradeStatus: Upgraded to bionic on 2018-01-24 (57 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1758391/+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 1758373] Re: bison -Wconversion warning

2018-03-23 Thread Amr Ibrahim

In the future, please use `ubuntu-bug package-name` to report bugs. Thanks.
https://help.ubuntu.com/dev/ubuntu-help/report-ubuntu-bug.html.en

** Package changed: gnome-settings-daemon (Ubuntu) => bison (Ubuntu)

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

Title:
  bison -Wconversion warning

Status in bison package in Ubuntu:
  New

Bug description:
  I wish to use the -Wconversion at gcc (the warnings are instructive
  for me, and they already taught me a lot), but then:

  $ bash bison_conversion_bug.sh 
  y.tab.c: In function ‘yyparse’:
  y.tab.c:1023:12: warning: conversion to ‘yytype_int16 {aka short int}’ from 
‘int’ may alter its value [-Wconversion]
 *yyssp = yystate;
  ^~~
  y.tab.c:1028:25: warning: conversion to ‘long unsigned int’ from ‘long int’ 
may change the sign of the result [-Wsign-conversion]
 YYSIZE_T yysize = yyssp - yyss + 1;
   ^
  $

  I get this problem even in an almost empty grammar and minimal C
  source frame for it, see the attachment: an example for minimal
  grammar and minimal C frame ALREADY providing the error.

  This is the error in case of my Ubuntu 18.04 ( bison --version =
  3.0.4, gcc --version = (Ubuntu 7.3.0-12ubuntu1) 7.3.0).

  I could try Debian jessie, where I get exactly the same error at
  exactly the same line position ( bison --version = 3.0.2, gcc
  --version = (Debian 4.9.2-10+deb8u1) 4.9.2).

  MY SUGGESTION: IF the bison developers are sure, that "yystate" and
  "yyssp - yyss + 1" will always fit into "short int" or "long unsigned
  int", THEN an explicit casting could be a solution.  HOWEVER in case
  of "yystate" it would be much more relaxing to make a decision whether
  it should be an "int" or "short int".

  The compilation commands are:

  CCOPTS=''
  CCOPTS+=' -std=c11'
  CCOPTS+=' -Og -g'
  CCOPTS+=' -Wabi'
  CCOPTS+=' -Wfatal-errors'
  CCOPTS+=' -Wall'
  CCOPTS+=' -Wextra'
  CCOPTS+=' -Wreturn-type'
  CCOPTS+=' -Wconversion'  ### bison has 2 conversion errors
  CCOPTS+=' -fexceptions'
  CCOPTS+=' -pedantic-errors'
  CCOPTS+=' -fmax-errors=1'

  rm -f y.output y.tab.h y.tab.c y.tab.o
  bison --yacc --verbose -d "EXAMPLE_GIVEN_IN_THE_ATTACHMENT.y"
  gcc -c ${CCOPTS} y.tab.c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bison/+bug/1758373/+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 1758398] [NEW] nautilus doesn't show network shares on 18.04

2018-03-23 Thread Anderson Luiz Alves

Public bug reported:

After upgrade libglib2.0-0 from version 2.54.1-1ubuntu1 to 2.56.0-2ubuntu1
nautilus doesn't show on sidebar neither on desktop any mounted network share.

I think it happens because changes in gio/gunixmounts.c
at g_unix_is_system_fs_type() that added cifs and smbfs to ignore_fs.

Network shares was mounted by pam_mount on /media/user/something.
gsettings org.gnome.nautilus.desktop volumes-visible is set true.

On Ubuntu Bionic 18.04 (devel branch)
nautilus 1:3.26.2-0ubuntu3.1

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


** Tags: bionic

** Tags added: bionic

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

Title:
  nautilus doesn't show network shares on 18.04

Status in nautilus package in Ubuntu:
  New

Bug description:
  After upgrade libglib2.0-0 from version 2.54.1-1ubuntu1 to 2.56.0-2ubuntu1
  nautilus doesn't show on sidebar neither on desktop any mounted network share.

  I think it happens because changes in gio/gunixmounts.c
  at g_unix_is_system_fs_type() that added cifs and smbfs to ignore_fs.

  Network shares was mounted by pam_mount on /media/user/something.
  gsettings org.gnome.nautilus.desktop volumes-visible is set true.

  On Ubuntu Bionic 18.04 (devel branch)
  nautilus 1:3.26.2-0ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1758398/+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 1511244] Re: Mouse pointer flickers at using DisplayLink

Hannes Bochmann:

1) Could you please advise to the full manufacturer and model of your
DisplayLink adapter (ex. StarTech USB3SDOCKDD)?

2) Regarding switching from Unity, did you test a different desktop
environment and confirm the issue is not reproducible?

3) Is this still reproducible with the latest DisplayLink driver (now
4.2)?

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

Title:
  Mouse pointer flickers at using DisplayLink

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have a three screen setup, the built-in laptop screen, a monitor
  connected directly into the laptop via DisplayPort, and a monitor
  connected via a USB DisplayLink Adapter.

  What happens is that when a monitor is connected via the USB
  DisplayLink Adapter, the mouse icon flickers only on the laptop screen
  and monitor connected via DisplayPort (not on the monitor connected
  via USB DisplayLink Adapter).

  However, this is also reproducible if I either deactivate the built-in
  laptop screen, or disconnect the DisplayPort connected monitor.

  WORKAROUND: Disconnect the USB DisplayLink Adapter for the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Oct 29 08:29:50 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:503c]
  InstallationDate: Installed on 2015-09-25 (33 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: LENOVO 20DT0003GE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic 
root=UUID=500f2ef6-7426-42ec-9fe2-88e9bcea ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET50WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET50WW(1.12):bd03/25/2015:svnLENOVO:pn20DT0003GE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT0003GE
  dmi.product.version: ThinkPad L450
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Oct 29 07:45:59 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9782
   vendor ENC
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1511244/+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 1757030] Re: Lite-On DS8A1H Slimline fails to record dual layer DVD+R

2018-03-23 Thread Ryan C. Underwood

dao option

** Attachment added: "dao.log"
   
https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1757030/+attachment/5088414/+files/dao.log

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

Title:
  Lite-On DS8A1H Slimline fails to record dual layer DVD+R

Status in dvd+rw-tools package in Ubuntu:
  New

Bug description:
  I tried Verbatim 8x and 2.4x DVD+R DL.  The failure is always exactly
  the same.

  $ growisofs -dvd-compat -Z /dev/dvdrw=2017.iso
  Executing 'builtin_dd if=2017.iso of=/dev/dvdrw obs=32k seek=0'
  /dev/dvdrw: splitting layers at 2009552 blocks
  /dev/dvdrw: "Current Write Speed" is 1.6x1352KBps.
  9175040/8231090176 ( 0.1%) @2.0x, remaining 74:40 RBU 100.0% UBU   7.4%
 21135360/8231090176 ( 0.3%) @2.6x, remaining 58:16 RBU 100.0% UBU  98.8%
 33095680/8231090176 ( 0.4%) @2.6x, remaining 49:32 RBU 100.0% UBU  98.6%
 45056000/8231090176 ( 0.5%) @2.6x, remaining 45:25 RBU 100.0% UBU  98.8%
 57016320/8231090176 ( 0.7%) @2.6x, remaining 45:23 RBU 100.0% UBU  98.8%
 69009408/8231090176 ( 0.8%) @2.6x, remaining 43:22 RBU 100.0% UBU  98.8%
 80969728/8231090176 ( 1.0%) @2.6x, remaining 41:56 RBU 100.0% UBU  98.6%
 92930048/8231090176 ( 1.1%) @2.6x, remaining 42:19 RBU 100.0% UBU  98.6%
  [..]
   4077289472/8231090176 (49.5%) @4.1x, remaining 15:15 RBU  90.0% UBU  88.4%
   4096065536/8231090176 (49.8%) @4.1x, remaining 15:11 RBU  43.0% UBU  97.9%
   4114808832/8231090176 (50.0%) @4.1x, remaining 15:06 RBU  28.0% UBU  97.9%
   4115562496/8231090176 (50.0%) @0.2x, remaining 15:08 RBU  69.4% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:12 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:15 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:18 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:22 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:25 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:28 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:32 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:35 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:38 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:42 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:45 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:48 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:52 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:55 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:58 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:02 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:05 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:08 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:12 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:15 RBU 100.0% UBU 100.0%
  :-[ WRITE@LBA=1ea9d0h failed with SK=5h/ASC=21h/ACQ=04h]: Invalid argument
  :-( write failed: Invalid argument
  $ dmesg
  [..]
  [5033003.021339] capability: warning: `growisofs' uses 32-bit capabilities 
(legacy support in use)
  [5033841.644130] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 
frozen
  [5033841.644149] ata1.00: cmd a0/01:00:00:00:80/00:00:00:00:00/a0 tag 0 dma 
32768 out
Write(10) 2a 00 00 1e d8 40 00 00 10 00res 
40/00:02:00:0c:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
  [5033841.644155] ata1.00: status: { DRDY }
  [5033846.688236] ata1: link is slow to respond, please be patient (ready=0)
  [5033851.684070] ata1: device not ready (errno=-16), forcing hardreset
  [5033851.684086] ata1: soft resetting link
  [5033851.888486] ata1.00: configured for MWDMA2
  [5033851.889482] ata1: EH complete

  xorriso is fine:
  $ xorrecord dev='/dev/sr0' -v -dao -pad 2017.iso
  xorriso 1.4.6 : RockRidge filesystem manipulator, libburnia project.

  Drive current: -outdev '/dev/sr0'
  Media current: DVD+R/DL
  Media status : is blank
  Media summary: 0 sessions, 0 data blocks, 0 data, 8152m free
  Beginning to write data track.
  [..]
  Writing to '/dev/sr0' completed successfully.

  xorriso : NOTE : Re-assessing -outdev '/dev/sr0'
  xorriso : NOTE : Disc status unsuitable for writing
  Drive current: -outdev '/dev/sr0'
  Media current: DVD+R/DL
  Media status : is written , is closed
  Media summary: 1 session, 4019104 data blocks, 7850m data, 0 free

  Disc status afterwards:
  $ dvd+rw-mediainfo /dev/dvdrw
  INQUIRY:[Slimtype][DVD A  DS8A1H   ][WH66]
  GET [CURRENT] CONFIGURATION:
   Mounted Media: 2Bh, DVD+R Double Layer
   Media ID

[Desktop-packages] [Bug 1757030] Re: Lite-On DS8A1H Slimline fails to record dual layer DVD+R

2018-03-23 Thread Ryan C. Underwood

Attaching logs for
./growisofs -Z /dev/dvdrw=dvd.iso (nodao.log)
./growisofs -use-the-force-luke=dao -Z /dev/dvdrw=dvd.iso (dao.log)

The difference in the actual commands sent seems to be stark.

Is there a way to place a DVD burner into simulation mode as with CD
recording so as to test the commands without wasting the disc?

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

Title:
  Lite-On DS8A1H Slimline fails to record dual layer DVD+R

Status in dvd+rw-tools package in Ubuntu:
  New

Bug description:
  I tried Verbatim 8x and 2.4x DVD+R DL.  The failure is always exactly
  the same.

  $ growisofs -dvd-compat -Z /dev/dvdrw=2017.iso
  Executing 'builtin_dd if=2017.iso of=/dev/dvdrw obs=32k seek=0'
  /dev/dvdrw: splitting layers at 2009552 blocks
  /dev/dvdrw: "Current Write Speed" is 1.6x1352KBps.
  9175040/8231090176 ( 0.1%) @2.0x, remaining 74:40 RBU 100.0% UBU   7.4%
 21135360/8231090176 ( 0.3%) @2.6x, remaining 58:16 RBU 100.0% UBU  98.8%
 33095680/8231090176 ( 0.4%) @2.6x, remaining 49:32 RBU 100.0% UBU  98.6%
 45056000/8231090176 ( 0.5%) @2.6x, remaining 45:25 RBU 100.0% UBU  98.8%
 57016320/8231090176 ( 0.7%) @2.6x, remaining 45:23 RBU 100.0% UBU  98.8%
 69009408/8231090176 ( 0.8%) @2.6x, remaining 43:22 RBU 100.0% UBU  98.8%
 80969728/8231090176 ( 1.0%) @2.6x, remaining 41:56 RBU 100.0% UBU  98.6%
 92930048/8231090176 ( 1.1%) @2.6x, remaining 42:19 RBU 100.0% UBU  98.6%
  [..]
   4077289472/8231090176 (49.5%) @4.1x, remaining 15:15 RBU  90.0% UBU  88.4%
   4096065536/8231090176 (49.8%) @4.1x, remaining 15:11 RBU  43.0% UBU  97.9%
   4114808832/8231090176 (50.0%) @4.1x, remaining 15:06 RBU  28.0% UBU  97.9%
   4115562496/8231090176 (50.0%) @0.2x, remaining 15:08 RBU  69.4% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:12 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:15 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:18 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:22 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:25 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:28 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:32 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:35 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:38 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:42 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:45 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:48 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:52 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:55 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:58 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:02 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:05 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:08 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:12 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:15 RBU 100.0% UBU 100.0%
  :-[ WRITE@LBA=1ea9d0h failed with SK=5h/ASC=21h/ACQ=04h]: Invalid argument
  :-( write failed: Invalid argument
  $ dmesg
  [..]
  [5033003.021339] capability: warning: `growisofs' uses 32-bit capabilities 
(legacy support in use)
  [5033841.644130] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 
frozen
  [5033841.644149] ata1.00: cmd a0/01:00:00:00:80/00:00:00:00:00/a0 tag 0 dma 
32768 out
Write(10) 2a 00 00 1e d8 40 00 00 10 00res 
40/00:02:00:0c:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
  [5033841.644155] ata1.00: status: { DRDY }
  [5033846.688236] ata1: link is slow to respond, please be patient (ready=0)
  [5033851.684070] ata1: device not ready (errno=-16), forcing hardreset
  [5033851.684086] ata1: soft resetting link
  [5033851.888486] ata1.00: configured for MWDMA2
  [5033851.889482] ata1: EH complete

  xorriso is fine:
  $ xorrecord dev='/dev/sr0' -v -dao -pad 2017.iso
  xorriso 1.4.6 : RockRidge filesystem manipulator, libburnia project.

  Drive current: -outdev '/dev/sr0'
  Media current: DVD+R/DL
  Media status : is blank
  Media summary: 0 sessions, 0 data blocks, 0 data, 8152m free
  Beginning to write data track.
  [..]
  Writing to '/dev/sr0' completed successfully.

  xorriso : NOTE : Re-assessing -outdev '/dev/sr0'
  xorriso : NOTE : Disc status unsuitable for writing
  Drive current: -outdev '/dev/sr0'
  Media current: DVD+R/DL
  Media status : is written , is closed
  Media summary: 1 session, 4019104 data blocks, 7850m data, 0 free

  Disc status afterwards:
  $ dv

[Desktop-packages] [Bug 1757030] Re: Lite-On DS8A1H Slimline fails to record dual layer DVD+R

2018-03-23 Thread Ryan C. Underwood

no DAO option

** Attachment added: "nodao.log"
   
https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1757030/+attachment/5088413/+files/nodao.log

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

Title:
  Lite-On DS8A1H Slimline fails to record dual layer DVD+R

Status in dvd+rw-tools package in Ubuntu:
  New

Bug description:
  I tried Verbatim 8x and 2.4x DVD+R DL.  The failure is always exactly
  the same.

  $ growisofs -dvd-compat -Z /dev/dvdrw=2017.iso
  Executing 'builtin_dd if=2017.iso of=/dev/dvdrw obs=32k seek=0'
  /dev/dvdrw: splitting layers at 2009552 blocks
  /dev/dvdrw: "Current Write Speed" is 1.6x1352KBps.
  9175040/8231090176 ( 0.1%) @2.0x, remaining 74:40 RBU 100.0% UBU   7.4%
 21135360/8231090176 ( 0.3%) @2.6x, remaining 58:16 RBU 100.0% UBU  98.8%
 33095680/8231090176 ( 0.4%) @2.6x, remaining 49:32 RBU 100.0% UBU  98.6%
 45056000/8231090176 ( 0.5%) @2.6x, remaining 45:25 RBU 100.0% UBU  98.8%
 57016320/8231090176 ( 0.7%) @2.6x, remaining 45:23 RBU 100.0% UBU  98.8%
 69009408/8231090176 ( 0.8%) @2.6x, remaining 43:22 RBU 100.0% UBU  98.8%
 80969728/8231090176 ( 1.0%) @2.6x, remaining 41:56 RBU 100.0% UBU  98.6%
 92930048/8231090176 ( 1.1%) @2.6x, remaining 42:19 RBU 100.0% UBU  98.6%
  [..]
   4077289472/8231090176 (49.5%) @4.1x, remaining 15:15 RBU  90.0% UBU  88.4%
   4096065536/8231090176 (49.8%) @4.1x, remaining 15:11 RBU  43.0% UBU  97.9%
   4114808832/8231090176 (50.0%) @4.1x, remaining 15:06 RBU  28.0% UBU  97.9%
   4115562496/8231090176 (50.0%) @0.2x, remaining 15:08 RBU  69.4% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:12 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:15 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:18 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:22 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:25 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:28 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:32 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:35 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:38 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:42 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:45 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:48 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:52 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:55 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 15:58 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:02 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:05 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:08 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:12 RBU 100.0% UBU 100.0%
   4115562496/8231090176 (50.0%) @0.0x, remaining 16:15 RBU 100.0% UBU 100.0%
  :-[ WRITE@LBA=1ea9d0h failed with SK=5h/ASC=21h/ACQ=04h]: Invalid argument
  :-( write failed: Invalid argument
  $ dmesg
  [..]
  [5033003.021339] capability: warning: `growisofs' uses 32-bit capabilities 
(legacy support in use)
  [5033841.644130] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 
frozen
  [5033841.644149] ata1.00: cmd a0/01:00:00:00:80/00:00:00:00:00/a0 tag 0 dma 
32768 out
Write(10) 2a 00 00 1e d8 40 00 00 10 00res 
40/00:02:00:0c:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
  [5033841.644155] ata1.00: status: { DRDY }
  [5033846.688236] ata1: link is slow to respond, please be patient (ready=0)
  [5033851.684070] ata1: device not ready (errno=-16), forcing hardreset
  [5033851.684086] ata1: soft resetting link
  [5033851.888486] ata1.00: configured for MWDMA2
  [5033851.889482] ata1: EH complete

  xorriso is fine:
  $ xorrecord dev='/dev/sr0' -v -dao -pad 2017.iso
  xorriso 1.4.6 : RockRidge filesystem manipulator, libburnia project.

  Drive current: -outdev '/dev/sr0'
  Media current: DVD+R/DL
  Media status : is blank
  Media summary: 0 sessions, 0 data blocks, 0 data, 8152m free
  Beginning to write data track.
  [..]
  Writing to '/dev/sr0' completed successfully.

  xorriso : NOTE : Re-assessing -outdev '/dev/sr0'
  xorriso : NOTE : Disc status unsuitable for writing
  Drive current: -outdev '/dev/sr0'
  Media current: DVD+R/DL
  Media status : is written , is closed
  Media summary: 1 session, 4019104 data blocks, 7850m data, 0 free

  Disc status afterwards:
  $ dvd+rw-mediainfo /dev/dvdrw
  INQUIRY:[Slimtype][DVD A  DS8A1H   ][WH66]
  GET [CURRENT] CONFIGURATION:
   Mounted Media: 2Bh, DVD+R Double Layer
   M

[Desktop-packages] [Bug 1751075] Re: Xorg freeze when use mpv or cheese.

Ven, given you updated to 18.04, stopping using unsupported
PPAs/software, and the screen freezing after using mpv/cheese doesn't
occur anymore, this issue appears resolved. Hence, I'll close this
report.

However, if you seek a resolution to the computer not booting unless using 
non-default kernel parameters, feel free to file a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  When using mpv to play a video fullscreen, when I try to resume the
  window from fullscreen, the screen freezes. Same thing happens when I
  use cheese. Nothing I can do except a hard poweroff.

  I've manually upgraded my kernel with M-bab's build from
  'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:

  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] 
[1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:380c]
  InstallationDate: Installed on 2018-03-07 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 81BR
  Package: xorg 1:7.7+19ubuntu5
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro pci=noaer 
ivrs_ioapic[4]=00:14.00 ivrs_ioapic[5]=00:00.01 quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnL

[Desktop-packages] [Bug 1754356] Re: xdg-user-dirs-update does not take care of $HOME

2018-03-23 Thread Iain Lane

xenial is uploaded, for bionic I asked for a review from seb128 which is
pending and I'll upload shortly

** Changed in: xdg-user-dirs (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: xdg-user-dirs (Ubuntu Xenial)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  xdg-user-dirs-update does not take care of $HOME

Status in xdg-user-dirs package in Ubuntu:
  In Progress
Status in xdg-user-dirs source package in Xenial:
  In Progress

Bug description:
  [ Impact ]

  When setting an user dir to a folder that is subfolder of $HOME (and
  when $HOME does not match the /etc/passwd defined home for the user),
  the ~/.config/user-dirs.dirs is wrongly generated.

  [ Test case ]

   1) env HOME=/tmp/temp-home xdg-user-dirs-update
   2) find /tmp/temp-home/
   3) should list generated XDG user directories
   4) /tmp/temp-home/.config/user-dirs.dirs should mention them

  Launching something like:
   - env HOME=/tmp/temp-home ./xdg-user-dirs-update --set DOWNLOADS 
"/tmp/temp-home/sub/folder/of/it/Downloads"

  Should modify /tmp/temp-home/.config/user-dirs.dirs so that it contains:
XDG_DOWNLOADS_DIR="$HOME/sub/folder/of/it/Downloads"

  [ Regression potential ]

  Xdg folders could be generated in wrong locations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1754356/+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 1758335] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'aut

2018-03-23 Thread dino99

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

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files  '/lib/udev/hwdb.d/20-sane.hwdb'

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: tentative de remplacement de «
  /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances
  du paquet libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  no details

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Mar 23 14:26:32 2018
  ErrorMessage: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », 
qui est différent d'autres instances du paquet libsane1:i386
  InstallationDate: Installed on 2018-03-14 (8 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb 
», qui est différent d'autres instances du paquet libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1758335/+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 1758373] Re: bison -Wconversion warning

2018-03-23 Thread Péter Prőhle

HELP!  I adjusted at the beginning of the bug report, that this is NOT a
gnome-settings-daemon bug, BUT a bison bug, ... there was a possibility
TO CHANGE THE PACKAGE WHAT IS AFFECTED, I do not know why it changed
back to gnome-settings-daemon?

Please, somebody who has enough right for this, change it to bison.
Thanks.

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

Title:
  bison -Wconversion warning

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

Bug description:
  I wish to use the -Wconversion at gcc (the warnings are instructive
  for me, and they already taught me a lot), but then:

  $ bash bison_conversion_bug.sh 
  y.tab.c: In function ‘yyparse’:
  y.tab.c:1023:12: warning: conversion to ‘yytype_int16 {aka short int}’ from 
‘int’ may alter its value [-Wconversion]
 *yyssp = yystate;
  ^~~
  y.tab.c:1028:25: warning: conversion to ‘long unsigned int’ from ‘long int’ 
may change the sign of the result [-Wsign-conversion]
 YYSIZE_T yysize = yyssp - yyss + 1;
   ^
  $

  I get this problem even in an almost empty grammar and minimal C
  source frame for it, see the attachment: an example for minimal
  grammar and minimal C frame ALREADY providing the error.

  This is the error in case of my Ubuntu 18.04 ( bison --version =
  3.0.4, gcc --version = (Ubuntu 7.3.0-12ubuntu1) 7.3.0).

  I could try Debian jessie, where I get exactly the same error at
  exactly the same line position ( bison --version = 3.0.2, gcc
  --version = (Debian 4.9.2-10+deb8u1) 4.9.2).

  MY SUGGESTION: IF the bison developers are sure, that "yystate" and
  "yyssp - yyss + 1" will always fit into "short int" or "long unsigned
  int", THEN an explicit casting could be a solution.  HOWEVER in case
  of "yystate" it would be much more relaxing to make a decision whether
  it should be an "int" or "short int".

  The compilation commands are:

  CCOPTS=''
  CCOPTS+=' -std=c11'
  CCOPTS+=' -Og -g'
  CCOPTS+=' -Wabi'
  CCOPTS+=' -Wfatal-errors'
  CCOPTS+=' -Wall'
  CCOPTS+=' -Wextra'
  CCOPTS+=' -Wreturn-type'
  CCOPTS+=' -Wconversion'  ### bison has 2 conversion errors
  CCOPTS+=' -fexceptions'
  CCOPTS+=' -pedantic-errors'
  CCOPTS+=' -fmax-errors=1'

  rm -f y.output y.tab.h y.tab.c y.tab.o
  bison --yacc --verbose -d "EXAMPLE_GIVEN_IN_THE_ATTACHMENT.y"
  gcc -c ${CCOPTS} y.tab.c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1758373/+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 1758373] [NEW] bison -Wconversion warning

2018-03-23 Thread Péter Prőhle

Public bug reported:

I wish to use the -Wconversion at gcc (the warnings are instructive for
me, and they already taught me a lot), but then:

$ bash bison_conversion_bug.sh 
y.tab.c: In function ‘yyparse’:
y.tab.c:1023:12: warning: conversion to ‘yytype_int16 {aka short int}’ from 
‘int’ may alter its value [-Wconversion]
   *yyssp = yystate;
^~~
y.tab.c:1028:25: warning: conversion to ‘long unsigned int’ from ‘long int’ may 
change the sign of the result [-Wsign-conversion]
   YYSIZE_T yysize = yyssp - yyss + 1;
 ^
$

I get this problem even in an almost empty grammar and minimal C source
frame for it, see the attachment: an example for minimal grammar and
minimal C frame ALREADY providing the error.

This is the error in case of my Ubuntu 18.04 ( bison --version = 3.0.4,
gcc --version = (Ubuntu 7.3.0-12ubuntu1) 7.3.0).

I could try Debian jessie, where I get exactly the same error at exactly
the same line position ( bison --version = 3.0.2, gcc --version =
(Debian 4.9.2-10+deb8u1) 4.9.2).

MY SUGGESTION: IF the bison developers are sure, that "yystate" and
"yyssp - yyss + 1" will always fit into "short int" or "long unsigned
int", THEN an explicit casting could be a solution.  HOWEVER in case of
"yystate" it would be much more relaxing to make a decision whether it
should be an "int" or "short int".

The compilation commands are:

CCOPTS=''
CCOPTS+=' -std=c11'
CCOPTS+=' -Og -g'
CCOPTS+=' -Wabi'
CCOPTS+=' -Wfatal-errors'
CCOPTS+=' -Wall'
CCOPTS+=' -Wextra'
CCOPTS+=' -Wreturn-type'
CCOPTS+=' -Wconversion'  ### bison has 2 conversion errors
CCOPTS+=' -fexceptions'
CCOPTS+=' -pedantic-errors'
CCOPTS+=' -fmax-errors=1'

rm -f y.output y.tab.h y.tab.c y.tab.o
bison --yacc --verbose -d "EXAMPLE_GIVEN_IN_THE_ATTACHMENT.y"
gcc -c ${CCOPTS} y.tab.c

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

** Attachment added: "minimal grammar with minimal C frame"
   
https://bugs.launchpad.net/bugs/1758373/+attachment/5088332/+files/bison_conversion_bug.y

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

Title:
  bison -Wconversion warning

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

Bug description:
  I wish to use the -Wconversion at gcc (the warnings are instructive
  for me, and they already taught me a lot), but then:

  $ bash bison_conversion_bug.sh 
  y.tab.c: In function ‘yyparse’:
  y.tab.c:1023:12: warning: conversion to ‘yytype_int16 {aka short int}’ from 
‘int’ may alter its value [-Wconversion]
 *yyssp = yystate;
  ^~~
  y.tab.c:1028:25: warning: conversion to ‘long unsigned int’ from ‘long int’ 
may change the sign of the result [-Wsign-conversion]
 YYSIZE_T yysize = yyssp - yyss + 1;
   ^
  $

  I get this problem even in an almost empty grammar and minimal C
  source frame for it, see the attachment: an example for minimal
  grammar and minimal C frame ALREADY providing the error.

  This is the error in case of my Ubuntu 18.04 ( bison --version =
  3.0.4, gcc --version = (Ubuntu 7.3.0-12ubuntu1) 7.3.0).

  I could try Debian jessie, where I get exactly the same error at
  exactly the same line position ( bison --version = 3.0.2, gcc
  --version = (Debian 4.9.2-10+deb8u1) 4.9.2).

  MY SUGGESTION: IF the bison developers are sure, that "yystate" and
  "yyssp - yyss + 1" will always fit into "short int" or "long unsigned
  int", THEN an explicit casting could be a solution.  HOWEVER in case
  of "yystate" it would be much more relaxing to make a decision whether
  it should be an "int" or "short int".

  The compilation commands are:

  CCOPTS=''
  CCOPTS+=' -std=c11'
  CCOPTS+=' -Og -g'
  CCOPTS+=' -Wabi'
  CCOPTS+=' -Wfatal-errors'
  CCOPTS+=' -Wall'
  CCOPTS+=' -Wextra'
  CCOPTS+=' -Wreturn-type'
  CCOPTS+=' -Wconversion'  ### bison has 2 conversion errors
  CCOPTS+=' -fexceptions'
  CCOPTS+=' -pedantic-errors'
  CCOPTS+=' -fmax-errors=1'

  rm -f y.output y.tab.h y.tab.c y.tab.o
  bison --yacc --verbose -d "EXAMPLE_GIVEN_IN_THE_ATTACHMENT.y"
  gcc -c ${CCOPTS} y.tab.c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1758373/+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 1672297] Re: gnome-shell uses lots of memory, and grows over time

2018-03-23 Thread cement_head

Disabling Gnome3 Shell Extensions is not the answer.  Solving the
underlying bug is the answer.  Disabling the G3X will severe cramp
usability of G3.

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

Title:
  gnome-shell uses lots of memory, and grows over time

Status in GNOME Shell:
  Confirmed
Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
  almost 2 GiB.

  user  3039  1.8 16.1 4302340 1968476 tty2  Sl+  Mar09 120:17
  /usr/bin/gnome-shell

  strace output is voluminous; here is a representative sample:

  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\231\n\10\0\n\0 
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0 
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  open("/proc/self/stat", O_RDONLY)   = 36
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  fcntl(36, F_GETFL)  = 0x8000 (flags O_RDONLY|O_LARGEFILE)
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
  read(36, "", 3072)  = 0
  close(36)   = 0
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) = 
1 ([{fd=4, revents=POLLIN}])
  read(4, "\1\0\0\0\0\0\0\0", 16) = 8
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, {msg_name(0)=NULL, 
msg_iov(1)=[{"[\2\327&h\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd

[Desktop-packages] [Bug 1742443] Re: Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot

2018-03-23 Thread Jani Uusitalo

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

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

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

Status in gnome-screenshot package in Ubuntu:
  Confirmed

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

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

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

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

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

[Desktop-packages] [Bug 1758363] Re: push and pop warning can generate "Operation not permitted" error

2018-03-23 Thread Philippe Cloutier

** Description changed:

  The push and pop quilt subcommands call touch for each patched file. The
  way it is called, touch can generate an error due to insufficient
  permissions, and that error is sent straight to the terminal.
  
  The touch call intends to set file modification times. As explained in
  https://stackoverflow.com/questions/953098/change-file-time-touch Linux
  does not allow changing mtime for a user which is neither root nor the
  user owning the file. This means that it is impossible for several
  people each owning some files to manage the same patched software, even
  if they are part of the same group and that group has full permissions
  on all files, unless they have access to a common account.
  
  Either quilt should manage times in a way that does not depend on a
  single user managing the software, or the failure can be considered
  unimportant, and quilt should just report failures differently. The
  latter approach could involve replacing touch's output with a clear
  error/warning message, limiting the number of errors displayed to 1, or
  adding an option to quiet such issues.
- 
  
  cloph2@SWIKID02:/var/www/html/foncierpedia$ quilt pop
  Removing patch tracker_prevent_edit_conflict.diff
  Restoring lang/fr/language.php
  Restoring lang/fr/language.js
  Restoring templates/tiki-view_tracker_item.tpl
  Restoring tiki-view_tracker_item.php
  Restoring lib/core/Services/Tracker/Controller.php
  touch: setting times of './lang/fr/language.php': Operation not permitted
  cloph2@SWIKID02:/var/www/html/foncierpedia$ quilt push
  touch: setting times of 
'.pc/tracker_prevent_edit_conflict.diff/lang/fr/language

   .php': Operation not permitted
  Applying patch tracker_prevent_edit_conflict.diff
  patching file lang/fr/language.js
  patching file lang/fr/language.php
  patching file lib/core/Services/Tracker/Controller.php
  patching file templates/tiki-view_tracker_item.tpl
  patching file tiki-view_tracker_item.php
  
  Now at patch tracker_prevent_edit_conflict.diff
  cloph2@SWIKID02:/var/www/html/foncierpedia$
  
+ 
  Ubuntu 14.04.5, using quilt 0.61-1
+ I could not find any hint that this is fixed in quilt 0.65.

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

Title:
  push and pop warning can generate "Operation not permitted" error

Status in quilt package in Ubuntu:
  New

Bug description:
  The push and pop quilt subcommands call touch for each patched file.
  The way it is called, touch can generate an error due to insufficient
  permissions, and that error is sent straight to the terminal.

  The touch call intends to set file modification times. As explained in
  https://stackoverflow.com/questions/953098/change-file-time-touch
  Linux does not allow changing mtime for a user which is neither root
  nor the user owning the file. This means that it is impossible for
  several people each owning some files to manage the same patched
  software, even if they are part of the same group and that group has
  full permissions on all files, unless they have access to a common
  account.

  Either quilt should manage times in a way that does not depend on a
  single user managing the software, or the failure can be considered
  unimportant, and quilt should just report failures differently. The
  latter approach could involve replacing touch's output with a clear
  error/warning message, limiting the number of errors displayed to 1,
  or adding an option to quiet such issues.

  cloph2@SWIKID02:/var/www/html/foncierpedia$ quilt pop
  Removing patch tracker_prevent_edit_conflict.diff
  Restoring lang/fr/language.php
  Restoring lang/fr/language.js
  Restoring templates/tiki-view_tracker_item.tpl
  Restoring tiki-view_tracker_item.php
  Restoring lib/core/Services/Tracker/Controller.php
  touch: setting times of './lang/fr/language.php': Operation not permitted
  cloph2@SWIKID02:/var/www/html/foncierpedia$ quilt push
  touch: setting times of 
'.pc/tracker_prevent_edit_conflict.diff/lang/fr/language

   .php': Operation not permitted
  Applying patch tracker_prevent_edit_conflict.diff
  patching file lang/fr/language.js
  patching file lang/fr/language.php
  patching file lib/core/Services/Tracker/Controller.php
  patching file templates/tiki-view_tracker_item.tpl
  patching file tiki-view_tracker_item.php

  Now at patch tracker_prevent_edit_conflict.diff
  cloph2@SWIKID02:/var/www/html/foncierpedia$

  
  Ubuntu 14.04.5, using quilt 0.61-1
  I could not find any hint that this is fixed in quilt 0.65.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/quilt/+bug/1758363/+subscrip

[Desktop-packages] [Bug 1758141] Re: language selecter crashing when trying to change language region german-german to german-switzerland

2018-03-23 Thread Gunnar Hjalmarsson

Meaningful, highly visible error messages are nice.

But if config files in $HOME, which programs need to write to, are owned
by root, you can't expect your system to work. Programs typically crash
then; root owned files in $HOME may even prevent you from being able to
log in.

If you can show me a reproducible use case where ~/.pam_environment gets
owned by root through normal use of the system, it's indeed a bug which
should be fixed. But probably it happened via some mistake you did
yourself, and error handling can't reasonably anticipate every possible
user error. ;)

With that said, in this case the program did provide useful debugging
info; it did "not just crash":

running '/usr/share/language-tools/save-to-pam-env' failed: no output

That's why I easily could point you to what the problem was.

** Changed in: language-selector (Ubuntu)
   Status: Incomplete => Opinion

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

Title:
  language selecter crashing when trying to change language region
  german-german to german-switzerland

Status in language-selector package in Ubuntu:
  Opinion

Bug description:
  language selecter crashing when trying to change language region
  german-german to german-switzerland

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: language-selector-gnome 0.165.4
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 22 20:27:05 2018
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2017-12-05 (107 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=de_DE.UTF-8
   LANGUAGE=de_DE
   XDG_RUNTIME_DIR=
  SourcePackage: language-selector
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1758141/+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 1758366] Re: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.13.0-38.43

2018-03-23 Thread Stefan Bader

test_wpa2_ip4 (__main__.ColdplugWifi)
WPA2, 802.11g, IPv4 ... ok
test_wpa2_ip6 (__main__.ColdplugWifi)
WPA2, 802.11g, IPv6 with only RA ... ok
test_auto_detect_ap (__main__.Hotplug)
new AP is being detected automatically within 30s ... expected failure
test_auto_detect_eth (__main__.Hotplug)
new eth router is being detected automatically within 30s ... Cannot find 
device "eth0"
/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/nm:23: PyGIWarning: 
NetworkManager was imported without specifying a version first. Use 
gi.require_version('NetworkManager', '1.0') before import to ensure that the 
right version gets loaded.
  from gi.repository import NetworkManager, NMClient, GLib
/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/nm:23: PyGIWarning: NMClient 
was imported without specifying a version first. Use 
gi.require_version('NMClient', '1.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import NetworkManager, NMClient, GLib
expected failure

==
FAIL: test_wpa1_ip4 (__main__.ColdplugWifi)
WPA1, 802.11g, IPv4
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/nm", line 466, in 
test_wpa1_ip4
''' % SSID, None, 54000, '12345678')
  File 
"/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/network_test_base.py", line 
359, in wrapped
args[0].wrap_process(fn, *args, **kwargs)
  File 
"/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/network_test_base.py", line 
263, in wrap_process
self.fail(f.read())
AssertionError: Traceback (most recent call last):
  File 
"/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/network_test_base.py", line 
252, in wrap_process
fn(*args, **kwargs)
  File "/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/nm", line 540, in 
do_test
ap = self.wait_ap(timeout=100)
  File "/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/nm", line 229, in 
wait_ap
timeout=timeout)
  File "/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/nm", line 184, in 
assertEventually
self.fail(message or 'timed out waiting for ' + str(condition))
  File "/usr/lib/python3.6/unittest/case.py", line 670, in fail
raise self.failureException(msg)
AssertionError: timed out waiting for AP to be detected

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

Title:
  network-manager 1.8.4-1ubuntu3 ADT test failure with linux
  4.13.0-38.43

Status in network-manager package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/n/network-manager/20180323_105026_adff0@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1758366/+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 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: New => Confirmed

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  A HDMI audio device usually has several output ports, each port
  represents a profile in pulseaudio, without this patch, the puseaudio
  always choose the first profile no matter it is active or not.

  [Test Case]

  connect each port of HDMI device, and check if the profile of that
  port is active or not.

  [Regression Potential]

  The patch will check all ports under each profile, if a profile only
  contains unavailable ports, this profile will be set to unavailable as
  well. Without this patch, all profiles are always available, then if a
  profile includes a unusable hdmi-output, and pulseaudio select this
  profile to be active (since its priority is the highest), the kernel
  audio driver will crash.

  I think this patch will not introduce regression:
  1) It is a correct logic to set a profile to be unavailable if it only 
contains unavailable ports.
  2) pulseaudio-artful and pulseaudio-bionic already include this patch, they 
work very well
  3) I tested this patch on 1 lenovo laptop, 1 lenovo desktop, 1 dell laptop 
and 1 dell desktop, all worked well as before
  4) tested this patch on two dell machines (LOAD5-DVT2-A2 and Dawson-JC-C 
without analogue audio) which have unusable hdmi-output profile on them, the 
kernel driver did not crash anymore and audio function worked very well.

  [Other Info]

  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+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 1758366] [NEW] network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.13.0-38.43

2018-03-23 Thread Stefan Bader

Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/n/network-manager/20180323_105026_adff0@/log.gz

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  network-manager 1.8.4-1ubuntu3 ADT test failure with linux
  4.13.0-38.43

Status in network-manager package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/n/network-manager/20180323_105026_adff0@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1758366/+subscriptions

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

[Desktop-packages] [Bug 1742443] Re: Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot

2018-03-23 Thread Jani Uusitalo

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

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

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


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

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

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

Status in gnome-screenshot package in Ubuntu:
  Confirmed

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

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

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

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

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

[Desktop-packages] [Bug 1758035] Re: gnome-shell crashed with SIGTRAP in g_realloc_n() from g_log_structured()

2018-03-23 Thread Brian Murray

There is a bit of a backlog which the errors.ubuntu.com retracers are
working through so it could be a while.

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

Title:
  gnome-shell crashed with SIGTRAP in g_realloc_n() from
  g_log_structured()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Freshly installed bionic.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Mar 22 12:22:58 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_realloc_n () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
  Title: gnome-shell crashed with signal 5 in g_realloc_n()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758035/+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 1758089] Re: 18.04 default wallpapers

2018-03-23 Thread Iain Lane

It's there. Still waiting for FCS wallpapers.

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: New => Fix Committed

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

Title:
  18.04 default wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Committed

Bug description:
  Attached is our Bionic Beaver.

  I've attached the PNG and JPG of the colour version.  The PNG is 18
  MB, and a pngcrush --brute failed to make it any smaller.  We could
  resize to 4k if needed, or use the JPEG.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1758089/+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 1758363] [NEW] push and pop warning can generate "Operation not permitted" error

2018-03-23 Thread Philippe Cloutier

Public bug reported:

The push and pop quilt subcommands call touch for each patched file. The
way it is called, touch can generate an error due to insufficient
permissions, and that error is sent straight to the terminal.

The touch call intends to set file modification times. As explained in
https://stackoverflow.com/questions/953098/change-file-time-touch Linux
does not allow changing mtime for a user which is neither root nor the
user owning the file. This means that it is impossible for several
people each owning some files to manage the same patched software, even
if they are part of the same group and that group has full permissions
on all files, unless they have access to a common account.

Either quilt should manage times in a way that does not depend on a
single user managing the software, or the failure can be considered
unimportant, and quilt should just report failures differently. The
latter approach could involve replacing touch's output with a clear
error/warning message, limiting the number of errors displayed to 1, or
adding an option to quiet such issues.


cloph2@SWIKID02:/var/www/html/foncierpedia$ quilt pop
Removing patch tracker_prevent_edit_conflict.diff
Restoring lang/fr/language.php
Restoring lang/fr/language.js
Restoring templates/tiki-view_tracker_item.tpl
Restoring tiki-view_tracker_item.php
Restoring lib/core/Services/Tracker/Controller.php
touch: setting times of './lang/fr/language.php': Operation not permitted
cloph2@SWIKID02:/var/www/html/foncierpedia$ quilt push
touch: setting times of 
'.pc/tracker_prevent_edit_conflict.diff/lang/fr/language

   .php': Operation not permitted
Applying patch tracker_prevent_edit_conflict.diff
patching file lang/fr/language.js
patching file lang/fr/language.php
patching file lib/core/Services/Tracker/Controller.php
patching file templates/tiki-view_tracker_item.tpl
patching file tiki-view_tracker_item.php

Now at patch tracker_prevent_edit_conflict.diff
cloph2@SWIKID02:/var/www/html/foncierpedia$

Ubuntu 14.04.5, using quilt 0.61-1

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

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

Title:
  push and pop warning can generate "Operation not permitted" error

Status in quilt package in Ubuntu:
  New

Bug description:
  The push and pop quilt subcommands call touch for each patched file.
  The way it is called, touch can generate an error due to insufficient
  permissions, and that error is sent straight to the terminal.

  The touch call intends to set file modification times. As explained in
  https://stackoverflow.com/questions/953098/change-file-time-touch
  Linux does not allow changing mtime for a user which is neither root
  nor the user owning the file. This means that it is impossible for
  several people each owning some files to manage the same patched
  software, even if they are part of the same group and that group has
  full permissions on all files, unless they have access to a common
  account.

  Either quilt should manage times in a way that does not depend on a
  single user managing the software, or the failure can be considered
  unimportant, and quilt should just report failures differently. The
  latter approach could involve replacing touch's output with a clear
  error/warning message, limiting the number of errors displayed to 1,
  or adding an option to quiet such issues.

  
  cloph2@SWIKID02:/var/www/html/foncierpedia$ quilt pop
  Removing patch tracker_prevent_edit_conflict.diff
  Restoring lang/fr/language.php
  Restoring lang/fr/language.js
  Restoring templates/tiki-view_tracker_item.tpl
  Restoring tiki-view_tracker_item.php
  Restoring lib/core/Services/Tracker/Controller.php
  touch: setting times of './lang/fr/language.php': Operation not permitted
  cloph2@SWIKID02:/var/www/html/foncierpedia$ quilt push
  touch: setting times of 
'.pc/tracker_prevent_edit_conflict.diff/lang/fr/language

   .php': Operation not permitted
  Applying patch tracker_prevent_edit_conflict.diff
  patching file lang/fr/language.js
  patching file lang/fr/language.php
  patching file lib/core/Services/Tracker/Controller.php
  patching file templates/tiki-view_tracker_item.tpl
  patching file tiki-view_tracker_item.php

  Now at patch tracker_prevent_edit_conflict.diff
  cloph2@SWIKID02:/var/www/html/foncierpedia$

  Ubuntu 14.04.5, using quilt 0.61-1

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

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

[Desktop-packages] [Bug 1754156] Re: Screen unlocking without password

2018-03-23 Thread pumpkinbeer

I've found the answer to this and created a new question.
https://askubuntu.com/questions/1018580/

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

Title:
  Screen unlocking without password

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  My screen is unlocking without a password after being locked for an
  unknown time period, like a lunch break or overnight.  It is not
  hibernating or suspending, just locked.  If I lock it and immediately
  unlock it forces me to use password as it should, otherwise about 40%
  of the time it just unlocks to my full session as I left it before
  locking.  I lock by physically clicking the lock icon in the top right
  of the screen.  I've not tested by just walking away and waiting.

  I originally posted here
  https://askubuntu.com/questions/1012420/ubuntu-17-10-major-security-
  issue-at-login?noredirect=1#comment1641885_1012420 if that helps.

  Let me know other info you need to help find a fix.  This is a major
  security issue for me at my location.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-screensaver 3.6.1-7ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  7 15:16:15 2018
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2018-03-01 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1754156/+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 1336184] Re: USB flash drive (NTFS) keeps writing for quite a while even after "Eject" completes

2018-03-23 Thread Seb Bonnard

I have the same pb. on Ubuntu 17.10 with Xfce + thunar file manager, so
I believe this bug is maybe not linked to nautilus but to fuseblk

** Package changed: nautilus (Ubuntu) => fuse (Ubuntu)

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

Title:
  USB flash drive (NTFS) keeps writing for quite a while even after
  "Eject" completes

Status in fuse package in Ubuntu:
  Confirmed

Bug description:
  Release: Ubuntu 14.04

  Nautilus version: 1:3.10.1-0ubuntu9.1

  Expected: After pressing "Eject" on a flash drive (formatted with NTFS
  -- haven't tried with FAT yet) I expected it to return only after
  flushing and unmounting the drive so the drive is completely safe to
  remove at that point

  What happened: "Eject" returned after a short while. The drive still
  kept writing for a long time. Mount shows the drive still mounted for
  the period while the flash drive keeps blinking though "df" does not
  show the drive anymore. Removing the drive at this point results in
  partial file write and NTFS filesystem damage (fixable with ntfsfix
  but dangerous).

  Steps to reproduce:

  1) Insert a flash drive (tried with NTFS mounted drive though I
  believe FAT will show similar behaviour though latter uses "flush"
  mount option so may not be that prominent)

  2) Try copying a large file. For testing use a size that will also mostly fit 
into filesystem cache so that real wait for writing is during unmount: dd 
if=/dev/zero of=/media///test.out bs=1M count=1000
   is the user name and  the name where drive was mounted by 
nautilus as per the label.

  3) "Eject" the drive from nautilus context menu after dd command above
  returns.

  4) Eject returns shortly. However drive is still writing as seen by
  the blinking, or disk throughput in gkrellm, iostat. Also note that
  "mount" still shows the drive as mounted though "df" and other tools
  don't.

  I have confirmed the same issue exists on all similar file managers
  namely nemo and caja. Haven't filed bugs against those yet.

  For comparison, the gnome-disks system utility correctly unmounts,
  ejects and stops the drive (last one even powers down the drive so the
  LED on drive is switched off which one would expect nautilus "Eject"
  to also do) so it doesn't seem to be a bug in udisks2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1336184/+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 1336184] Re: USB flash drive (NTFS) keeps writing for quite a while even after "Eject" completes

2018-03-23 Thread Seb Bonnard

Hi,

I have the same pb. in Ubuntu 17.10.

Where is the rule (udev ?) that automatically mounts my USB pendrive so
that I can add "flush" or "sync" to it ?

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

Title:
  USB flash drive (NTFS) keeps writing for quite a while even after
  "Eject" completes

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Release: Ubuntu 14.04

  Nautilus version: 1:3.10.1-0ubuntu9.1

  Expected: After pressing "Eject" on a flash drive (formatted with NTFS
  -- haven't tried with FAT yet) I expected it to return only after
  flushing and unmounting the drive so the drive is completely safe to
  remove at that point

  What happened: "Eject" returned after a short while. The drive still
  kept writing for a long time. Mount shows the drive still mounted for
  the period while the flash drive keeps blinking though "df" does not
  show the drive anymore. Removing the drive at this point results in
  partial file write and NTFS filesystem damage (fixable with ntfsfix
  but dangerous).

  Steps to reproduce:

  1) Insert a flash drive (tried with NTFS mounted drive though I
  believe FAT will show similar behaviour though latter uses "flush"
  mount option so may not be that prominent)

  2) Try copying a large file. For testing use a size that will also mostly fit 
into filesystem cache so that real wait for writing is during unmount: dd 
if=/dev/zero of=/media///test.out bs=1M count=1000
   is the user name and  the name where drive was mounted by 
nautilus as per the label.

  3) "Eject" the drive from nautilus context menu after dd command above
  returns.

  4) Eject returns shortly. However drive is still writing as seen by
  the blinking, or disk throughput in gkrellm, iostat. Also note that
  "mount" still shows the drive as mounted though "df" and other tools
  don't.

  I have confirmed the same issue exists on all similar file managers
  namely nemo and caja. Haven't filed bugs against those yet.

  For comparison, the gnome-disks system utility correctly unmounts,
  ejects and stops the drive (last one even powers down the drive so the
  LED on drive is switched off which one would expect nautilus "Eject"
  to also do) so it doesn't seem to be a bug in udisks2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1336184/+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 1708375] Re: Add support for purple-telegram (telepathy-haze)

2018-03-23 Thread Khurshid Alam

I have updated the patch. Is there anything else needed for this?

** Tags removed: artful
** Tags added: bionic

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

Title:
  Add support for purple-telegram (telepathy-haze)

Status in telepathy-mission-control-5 package in Ubuntu:
  Confirmed

Bug description:
  When using purple telegram through telepathy-haze, it requires
  following permissions:

  # for purple telegram
  /etc/telegram-purple/server.tglpub r,
  /usr/lib/purple-2*/   r,
  /usr/lib/purple-2/*.somr,
  /usr/share/locale/*/LC_MESSAGES/*.mo r,
  /usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
  @{HOME}/.purple/telegram-purple/** rw,
  @{HOME}/.telegram-purple/**   rw,

  under /usr/lib/telepathy/telepathy-* section. See issue
  https://github.com/majn/telegram-purple/issues/346 for more details.

  I have attached the necessary patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+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 1757299] Re: xorg hangs

in all of the following bugs, xorg either crashes or hangs, and ctl-alt-
Fn either doesn't respond (ie loss of ability to change virtual terminal
from the keyboard) or in Bug #1290797 the text gets switched but not the
mouse cursor function.

Bug #1757299 xorg hangs
Bug #1744429 xorg sometimes freezes up while playing either vlc or youtube
Bug #1645485 very old display driver bug?
Bug #1290797 longstanding display driver bug elicited by xscreensaver or 
lightdm or chvt

i have xdiagnose installed in bionic, ready for the next occurrence.

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

Title:
  xorg hangs

Status in xorg package in Ubuntu:
  New

Bug description:
  launched startx,
  launched an xterm via twm,
  launched another xterm via the first,
  launched tmux,
  launched firefox-esr, bluetooth-manager, and pavucontrol,
  maximized the xterm running tmux

  xorg stopped responding, ctl-alt-Fn don't respond either

  logged in via ssh, attached to tmux, launched htop, copied htop output, in 
which you can see xorg consuming lots of cpu.
  noticed twm no longer running
  launched ubuntu-bug xserver-xorg
  answered its question re display manager log files
  i left it printing endless periods for over an hour

  killed xorg
  launched startx again
  started a second ubuntu-bug xserver-xorg
  answered its questions re display manager log files and additional debugging 
work

  noticed the first ubuntu-bug xserver-xorg is no longer printing periods
  answered its questions re additional debugging work and Send problem report

  attached copy of htop output

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog:
   Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
* Starting AppArmor profiles   [160G 
[154G[ OK ]
* Restoring resolver state...   [160G 
[154G[ OK ]
  CompositorRunning: None
  Date: Tue Mar 20 17:15:16 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell OptiPlex 755 [1028:0211]
 Subsystem: Dell OptiPlex 755 [1028:0211]
  JournalErrors:
   -- Logs begin at Fri 2018-02-23 08:59:47 CST, end at Tue 2018-03-20 17:14:39 
CDT. --
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module-alsa-card.c: 
Failed to find a working profile.
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] module.c: Failed to 
load module "module-alsa-card" (argument: "device_id="0" 
name="pci-_00_1b.0" card_name="alsa_card.pci-_00_1b.0" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
   Mar 20 17:01:37 hostname pulseaudio[1099]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
   Mar 20 17:01:37 hostname pulseaudio[1109]: [pulseaudio] pid.c: Daemon 
already running.
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 panic=30
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1750846] Re: several g-s-d services are timing out when booting a live session

2018-03-23 Thread Iain Lane

I can reproduce this, trying to figure it out now.

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

Title:
  several g-s-d services are timing out when booting a live session

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

Bug description:
  The following g-s-d services are timing out when booting a live
  session:

  gsd-media-keys
  gsd-color
  gsd-wacom
  gsd-power

  One impact at least is that the shortcut to launch a terminal doesn't
  work

  From the journal:
  [   82.368253] ubuntu gsd-media-keys[1865]: Failed to grab accelerators: 
Timeout was reached (24)
  [  108.828263] ubuntu gsd-color[1863]: failed to get screens: Timeout was 
reached
  [  108.836334] ubuntu gsd-wacom[1836]: Failed to construct RR screen: Timeout 
was reached
  [  108.837764] ubuntu gsd-power[1823]: Could not create GnomeRRScreen: 
Timeout was reached

  [  245.337228] ubuntu gsd-media-keys[1865]: Could not find accelerator for 
accel id 175
  ^_ this last line is displayed when Ctrl+Alt+T is pressed to open a terminal

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 21 15:20:00 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846/+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 1758331] Re: IPv6 Route to OpenVPN Server is not created

2018-03-23 Thread Andreas Hasenack

ppa:ahasenack/nm-ipv6-openvpn-1758331
(https://launchpad.net/~ahasenack/+archive/ubuntu/nm-
ipv6-openvpn-1758331/) has test packages with the upstream commit

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

Title:
  IPv6 Route to OpenVPN Server is not created

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  When the OpenVPN server pushes routes that overlaps with the openvpn server 
IP, it should add a route to the OpenVPN server.
  This seems to get done, but it fails:

  NetworkManager[1031]:  [1521794922.6687] platform: signal: route   6   
added: 2a00:x:x::3/128 via fe80::230:48ff:fedc:5067 dev 2 metric 100 mss 0 
rt-src rt-ra src ::/128 pref-src 2a02:x:x:x:x:x:x:5fc6
  NetworkManager[1031]:  [1521794922.6687] device[0x55566c34c4e0] 
(enxa44cc890f4c8): queued IP6 config change
  NetworkManager[1031]:   [1521794922.6688] platform: route: get IPv6 
route for: 2a00:x:x::3 failed with unspecified

  
  2a00:x:x::3 => VPN Server IPv6

  Now this seems to be fixed in commit:
  
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=2d1fad641b950520bec1a87c450d0e3b1439e262

  Can we get this cherry-picked in Bionic?

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1758331/+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 1758348] Re: gnome-shell crashed with signal 5

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1758348/+attachment/5088273/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1758348/+attachment/5088275/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1758348/+attachment/5088278/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1758348/+attachment/5088279/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1758348/+attachment/5088280/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758348/+attachment/5088281/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758348/+attachment/5088282/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crashes on resume from suspend about 20% of the time.  The shell does
  restart, of course.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar 23 09:59:11 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-12 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758348/+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 1645485] Re: very old display driver bug?

in all of the following bugs, xorg either crashes or hangs, and ctl-alt-
Fn either doesn't respond (ie loss of ability to change virtual terminal
from the keyboard) or in Bug #1290797 the text gets switched but not the
mouse cursor function.

Bug #1757299 xorg hangs
Bug #1744429 xorg sometimes freezes up while playing either vlc or youtube
Bug #1645485 very old display driver bug?
Bug #1290797 longstanding display driver bug elicited by xscreensaver or 
lightdm or chvt

i have xdiagnose installed in bionic, ready for the next occurrence.

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

Title:
  very old display driver bug?

Status in xorg package in Ubuntu:
  New

Bug description:
  the most bothersome, most notable, and most curious symptom of this
  bug is the absolute degree to which the display locks up.  xclock's
  seconds are no longer changing, the mouse cursor won't move, and even
  ctl-alt-F1 does nothing.

  meanwhile mplayer, playing in a hidden tmux window, is still playing
  merrily along.

  i logged in via sshd and copied this from htop:
  0  [|100.0%] Tasks: 68; 3 running
  1  [|| 1.3%] Load average: 1.00 0.91 
0.53
  Mem[|973M/1.91G] Time: 14:26:17
  Swp[   0K/1.86G]
PID START USER   VIRT   RES  NI CPU%   TIME+  S Command
   1714 12:50 g 1713M  789M   0  0.0  6:37.92 S /usr/lib/firefox/firefox
   2368 14:07 g  661M 57252   0  0.0  0:03.33 S /usr/bin/python3 
/usr/bin/blueman-manager
794 12:49 root   269M 54988   0 99.3 10:12.88 R /usr/lib/xorg/Xorg 
-core :0 -seat seat0 -auth /var/
   2385 14:07 g  583M 53524   0  0.0  0:00.39 S /usr/bin/python3 
/usr/bin/blueman-applet
   2397 14:07 g  555M 42968   0  0.0  0:10.68 S pavucontrol
   1926 12:57 g  282M 37752   0  0.7  0:02.46 S 
/usr/lib/firefox/plugin-container /opt/google/talkp
   1933 12:57 g  512M 36404   0  0.0  0:02.96 S 
/opt/google/talkplugin/GoogleTalkPlugin
   2403 14:07 g  823M 30352   0  0.0  0:03.52 S mplayer -ao pulse -af 
channels=2 -framedrop -msgcol
  F1Help  F2Setup F3SearchF4FilterF5Tree  F6SortByF7Nice -F8Nice +F9Kill  
F10Quit

  ps also attached, taken before killing xorg.

  i've filed this under xorg merely because xorg is the one stuck eating
  all the CPU.  i really suspect the display driver, and don't know how
  to find or identify that.

  i much more commonly saw these very same symptoms when i used to run
  xscreensaver.  i stopped running xscreensaver just to stop beating my
  head against that wall.  but many years and many releases later, it
  looks like this display driver bug is still lurking around.

  there was hardly anything running when this froze.  i already
  mentioned mplayer (sound only) and tmux, twm's the window manager,
  firefox was running but iconized and idle tho running gmail and the
  googletalk plugin, not that i suspect any of them in any way.  xterm
  was occupying most of the screen, showing tmux, and idle.  the ones
  i'd more suspect would be xclock & pavucontrol.  pavucontrol was
  hidden but busily showing it's audio level bar, xclock was visible and
  displaying the time of day including seconds, so the most likely one
  to have tripped a display driver bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Nov 28 14:36:38 2016
  InstallationDate: Installed on 2016-10-15 (43 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645485/+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 1290797] Re: longstanding display driver bug elicited by xscreensaver or lightdm or chvt

in all of the following bugs, xorg either crashes or hangs, and ctl-alt-
Fn either doesn't respond (ie loss of ability to change virtual terminal
from the keyboard) or in Bug #1290797 the text gets switched but not the
mouse cursor function.

Bug #1757299 xorg hangs
Bug #1744429 xorg sometimes freezes up while playing either vlc or youtube
Bug #1645485 very old display driver bug?
Bug #1290797 longstanding display driver bug elicited by xscreensaver or 
lightdm or chvt

i have xdiagnose installed in bionic, ready for the next occurrence.

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

Title:
  longstanding display driver bug elicited by xscreensaver or lightdm or
  chvt

Status in xorg package in Ubuntu:
  Expired

Bug description:
  i've been hitting this bug since natty or earlier.  today, as per
  usual, the evidence of the bug is that chvt no longer functions
  normally.  in today's case, two instances of xorg had been running,
  both crashed, xorg would not relaunch (immediately crashed again)(tho
  no trouble launching Xvnc), after the xorg crashes ctl-alt-F7 shows:
  "The system is running in low-graphics mode", ctl-alt-F8 shows all
  black, and the clear clue, ctl-alt-F1 shows the text you would expect
  to see there, but at the same time the mouse cursor is still being
  displayed and responding to mouse movement as if we were still looking
  at ctl-alt-F[78]!  same for ctl-alt-F[2-6].  when i hit this same bug
  on other days, the behaviour of ctl-alt-Fn will be peculiar in unique
  bizarre ways.

  i tried to submit this bug via ubuntu-bug (in 2 or 3 "screen" windows,
  then killed them all, then tried one more time), then zipped up the
  apport log, the Xorg logs, the single /var/crash/*Xorg* i found, and a
  process list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1290797/+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 1758346] Re: Xwayland crashed with signal 7 in __libc_start_main()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1750138, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1758346/+attachment/5088253/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1758346/+attachment/5088256/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1758346/+attachment/5088264/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1758346/+attachment/5088266/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1758346/+attachment/5088267/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758346/+attachment/5088268/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758346/+attachment/5088269/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1750138

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xwayland crashed with signal 7 in __libc_start_main()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Crashes on resume from suspend, about 50% of the time.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar 23 09:59:04 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: acpi-call, 1.1.0, 4.15.0-12-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-03-12 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114)
  MachineType: LENOVO 20ARA0S100
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core 
-listen 4 -listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=b6683bc1-7dd5-4afd-8e70-f69253403b71 ro quiet splash vt.handoff=1
  Signal: 7
  SourcePackage: xorg-server
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x55a1267fcaa0, argc=12, argv=0x7ffdf787dd08, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffdf787dcf8) at ../csu/libc-start.c:310
  Title: Xwayland crashed with signal 7 in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouv

[Desktop-packages] [Bug 1758350] [NEW] Everything is ok but The only is disappointing I cannot control display brightness through ubuntu provided brightness control option.And when I am playing any vi

2018-03-23 Thread Rohan Kundu

Public bug reported:

My system specs;-Intel pentium 2010g processor 
 4gb of ram

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 19:21:08 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [8086:2111]
InstallationDate: Installed on 2018-03-21 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed 
root=UUID=7157ae88-d872-4f4e-9fa7-c0bbf1f24103 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/19/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61
dmi.board.vendor: INTEL Corporation
dmi.board.version: To be filled by O.E.M.
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.:bvr4.6.5:bd07/19/2017:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu

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

Title:
  Everything is ok but The only is disappointing I cannot control
  display brightness through ubuntu provided brightness control
  option.And when I am playing any video it looks like my onboard
  graphics can't handel the video's graphics but, when i was on windows
  i didn't see any kind of problem like this.should I need to use any
  graphics card.

Status in xorg package in Ubuntu:
  New

Bug description:
  My system specs;-Intel pentium 2010g processor 
   4gb of ram

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 19:21:08 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [8086:2111]
  InstallationDate: Installed on 2018-03-21 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed 
root=UUID=7157ae88-d872-4f4e-9fa7-c0bbf1f24103 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: To be filled by O.E.M.
  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

[Desktop-packages] [Bug 1745799] Re: Xwayland crashed with SIGABRT in OsAbort()

** Tags added: artful

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

Title:
  Xwayland crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Crashes when plugging in Dell WD15

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  Uname: Linux 4.15.0-rc8+ x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 27 22:12:41 2018
  DistUpgraded: 2018-01-26 09:36:11,455 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:591e] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:077a]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5690 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9365
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-rc8+ 
root=UUID=fe08dba8-d746-4a04-82c9-cac962e9321c ro quiet splash 
wmi.debug_dump_wdg=1 vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (1 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.21
  dmi.board.name: 0DVT6M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.21:bd12/05/2017:svnDellInc.:pnXPS139365:pvr:rvnDellInc.:rn0DVT6M:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9365
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xorg-server (Ubuntu)
   Status: New => Confirmed

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

Title:
  Xwayland crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Crashes when plugging in Dell WD15

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  Uname: Linux 4.15.0-rc8+ x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 27 22:12:41 2018
  DistUpgraded: 2018-01-26 09:36:11,455 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:591e] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:077a]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5690 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9365
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-rc8+ 
root=UUID=fe08dba8-d746-4a04-82c9-cac962e9321c ro quiet splash 
wmi.debug_dump_wdg=1 vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (1 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.21
  dmi.board.name: 0DVT6M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.21:bd12/05/2017:svnDellInc.:pnXPS139365:pvr:rvnDellInc.:rn0DVT6M:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9365
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1745799, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1758340/+attachment/5088218/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1758340/+attachment/5088221/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1758340/+attachment/5088230/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1758340/+attachment/5088232/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1758340/+attachment/5088233/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758340/+attachment/5088234/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758340/+attachment/5088235/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1745799
   Xwayland crashed with SIGABRT in OsAbort()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xwayland crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Crash on first session login. Always have to login twice.

  Description:  Ubuntu 17.10
  Release:  17.10

  xorg:
Installed: 1:7.7+19ubuntu3
Candidate: 1:7.7+19ubuntu3
Version table:
   *** 1:7.7+19ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins:
   (gconftool-2:7523): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
   Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
   Failed to get value for 
`/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 22:33:43 2018
  DistUpgraded: 2018-03-17 22:04:35,067 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py ([Errno 2] No such file or directory: 
'./xorg_fix_proprietary.py')
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExecutableTimestamp: 1508068793
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 520 [1028:06de]
  InstallationDate: Installed on 2018-03-17 (5 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 002: ID 413c:81b6 Dell Computer Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E5470
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcCwd: /home/marc
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic 
root=UUID=ef2a1fe1-31a7-42da-9596-d08f28761031 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 5: Invalid MIT-MAGIC-COOKIE-1 keyError: unable to 
open display
  UpgradeStatus: Upgraded to artful on 2018-03-17 (5 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 04/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0VHKV0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: De

[Desktop-packages] [Bug 1758341] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1758341/+attachment/5088238/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1758341/+attachment/5088240/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1758341/+attachment/5088244/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1758341/+attachment/5088245/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1758341/+attachment/5088246/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758341/+attachment/5088247/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1758341/+attachment/5088248/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crash on first session login. Always have to login twice.

  May be related to #1758340.

  Description:  Ubuntu 17.10
  Release:  17.10

  gnome-shell:
Installed: 3.26.2-0ubuntu0.1
Candidate: 3.26.2-0ubuntu0.1
Version table:
   *** 3.26.2-0ubuntu0.1 500
  500 http://de.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Mar 20 22:26:39 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1510175942
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 
'libreoffice-impress.desktop', 'gnome-control-center.desktop', 
'vmware-workstation.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-17 (5 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /var/lib/gdm3
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: Upgraded to artful on 2018-03-17 (5 days ago)
  UserGroups:

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

apport information

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using mpv to play a video fullscreen, when I try to resume the
  window from fullscreen, the screen freezes. Same thing happens when I
  use cheese. Nothing I can do except a hard poweroff.

  I've manually upgraded my kernel with M-bab's build from
  'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:

  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] 
[1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:380c]
  InstallationDate: Installed on 2018-03-07 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 81BR
  Package: xorg 1:7.7+19ubuntu5
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro pci=noaer 
ivrs_ioapic[4]=00:14.00 ivrs_ioapic[5]=00:00.01 quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubun

[Desktop-packages] [Bug 1758331] [NEW] IPv6 Route to OpenVPN Server is not created

2018-03-23 Thread Jean-Louis Dupond

Public bug reported:

Hi,

When the OpenVPN server pushes routes that overlaps with the openvpn server IP, 
it should add a route to the OpenVPN server.
This seems to get done, but it fails:

NetworkManager[1031]:  [1521794922.6687] platform: signal: route   6   
added: 2a00:x:x::3/128 via fe80::230:48ff:fedc:5067 dev 2 metric 100 mss 0 
rt-src rt-ra src ::/128 pref-src 2a02:x:x:x:x:x:x:5fc6
NetworkManager[1031]:  [1521794922.6687] device[0x55566c34c4e0] 
(enxa44cc890f4c8): queued IP6 config change
NetworkManager[1031]:   [1521794922.6688] platform: route: get IPv6 route 
for: 2a00:x:x::3 failed with unspecified


2a00:x:x::3 => VPN Server IPv6

Now this seems to be fixed in commit:
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=2d1fad641b950520bec1a87c450d0e3b1439e262

Can we get this cherry-picked in Bionic?

Thanks!

** Affects: network-manager
 Importance: Unknown
 Status: Unknown

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=793962
   Importance: Unknown
   Status: Unknown

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

Title:
  IPv6 Route to OpenVPN Server is not created

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  When the OpenVPN server pushes routes that overlaps with the openvpn server 
IP, it should add a route to the OpenVPN server.
  This seems to get done, but it fails:

  NetworkManager[1031]:  [1521794922.6687] platform: signal: route   6   
added: 2a00:x:x::3/128 via fe80::230:48ff:fedc:5067 dev 2 metric 100 mss 0 
rt-src rt-ra src ::/128 pref-src 2a02:x:x:x:x:x:x:5fc6
  NetworkManager[1031]:  [1521794922.6687] device[0x55566c34c4e0] 
(enxa44cc890f4c8): queued IP6 config change
  NetworkManager[1031]:   [1521794922.6688] platform: route: get IPv6 
route for: 2a00:x:x::3 failed with unspecified

  
  2a00:x:x::3 => VPN Server IPv6

  Now this seems to be fixed in commit:
  
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=2d1fad641b950520bec1a87c450d0e3b1439e262

  Can we get this cherry-picked in Bionic?

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1758331/+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 1623665] Re: Image Magick appears twice in the list of installed applications

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

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-software (Ubuntu)
   Status: New => Confirmed

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

Title:
  Image Magick appears twice in the list of installed applications

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  After a fresh install of Ubuntu 16.04.1, in the installed apps list,
  Image Magick appears twice, with identical descriptions. Curiously,
  the two packages have different ratings.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 14 00:50:05 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-09-04 (10 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1623665/+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 1726224] Re: wacom invisible mouse pointer in wayland

2018-03-23 Thread WarrenSensei

I am not sure if I have the same bug with worse symptoms, or a whole different 
problem, but here goes:
My Intuos3 PTX-930 will not work in Ubuntu 17.10. 
Under Wayland, the cursor flies randomly across the screen whenever the stylus 
or mouse are near the tablet, often "collecting" in the top left corner. It 
also leaves a second cursor under the control of the normal mouse/touchpad on 
my laptop.
Under XOrg, location is stable. BUT with either Wayland or Xorg, all input 
seems to include a "touch" or left-click action! So literally everything the 
cursor passes over is clicked! Programs opening, windows being opened and 
closed, CHAOS! In XOrg, clicking stops when I remove the stylus/mouse from the 
tablet's field, but in Wayland once the stylus/mouse has been near, the chaos 
never ends until I reboot.

The internet has not been helpful with this, as most solutions are for
older versions and refer to repositories that don't exist anymore
(doctormo, for one).

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

Title:
  wacom invisible mouse pointer in wayland

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.10, I connected my Wacom Intuos tablet,
  which has touch and pen functionality.

  Controlling the mouse pointer through the touch functionality seems to
  work fine, but using the stylus produced very strange behaviour,
  depending the program.

  - With Firefox there there are two pointers - one that is moving in
  accordance with the stylus movements, and one stays put at the
  position, when the stylus movement was detected.

  - With Darktable the mouse pointer becomes invisible, once it's moved
  inside of the application window (it registers clicks though). Once
  the pointer is moved outside of the application window, it appears
  again.

  I'm running Ubuntu inside of a wayland session.

  libwacom2: 0.24-1

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

apport information

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using mpv to play a video fullscreen, when I try to resume the
  window from fullscreen, the screen freezes. Same thing happens when I
  use cheese. Nothing I can do except a hard poweroff.

  I've manually upgraded my kernel with M-bab's build from
  'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:

  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] 
[1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:380c]
  InstallationDate: Installed on 2018-03-07 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 81BR
  Package: xorg 1:7.7+19ubuntu5
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro pci=noaer 
ivrs_ioapic[4]=00:14.00 ivrs_ioapic[5]=00:00.01 quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3

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

apport information

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using mpv to play a video fullscreen, when I try to resume the
  window from fullscreen, the screen freezes. Same thing happens when I
  use cheese. Nothing I can do except a hard poweroff.

  I've manually upgraded my kernel with M-bab's build from
  'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:

  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] 
[1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:380c]
  InstallationDate: Installed on 2018-03-07 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 81BR
  Package: xorg 1:7.7+19ubuntu5
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro pci=noaer 
ivrs_ioapic[4]=00:14.00 ivrs_ioapic[5]=00:00.01 quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubun

[Desktop-packages] [Bug 1731417] Re: Installed network printer removed automatically when turned off

2018-03-23 Thread Alberto Donato

** Attachment added: "avahi.txt"
   
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1731417/+attachment/5088131/+files/avahi.txt

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

Title:
  Installed network printer removed automatically when turned off

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After installing artful, I configured my HP LaserJet M1212nf via network as 
usual via hp-setup.
  Installation worked and I could print/scan via network, but next time I 
needed to print, the printer was gone from the system.
  Basically, every time I need to print, I have to install the printer again.
  I'm not sure when the printer disappears, but I can reproduce consistently.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hplip-gui 3.17.7+repack0-3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: GNOME
  Date: Fri Nov 10 09:33:12 2017
  InstallationDate: Installed on 2017-07-30 (102 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170730)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed 
root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F15
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1751075] xdpyinfo.txt

apport information

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using mpv to play a video fullscreen, when I try to resume the
  window from fullscreen, the screen freezes. Same thing happens when I
  use cheese. Nothing I can do except a hard poweroff.

  I've manually upgraded my kernel with M-bab's build from
  'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:

  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] 
[1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:380c]
  InstallationDate: Installed on 2018-03-07 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 81BR
  Package: xorg 1:7.7+19ubuntu5
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro pci=noaer 
ivrs_ioapic[4]=00:14.00 ivrs_ioapic[5]=00:00.01 quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ub

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

apport information

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using mpv to play a video fullscreen, when I try to resume the
  window from fullscreen, the screen freezes. Same thing happens when I
  use cheese. Nothing I can do except a hard poweroff.

  I've manually upgraded my kernel with M-bab's build from
  'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:

  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] 
[1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:380c]
  InstallationDate: Installed on 2018-03-07 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 81BR
  Package: xorg 1:7.7+19ubuntu5
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro pci=noaer 
ivrs_ioapic[4]=00:14.00 ivrs_ioapic[5]=00:00.01 quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3

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

apport information

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using mpv to play a video fullscreen, when I try to resume the
  window from fullscreen, the screen freezes. Same thing happens when I
  use cheese. Nothing I can do except a hard poweroff.

  I've manually upgraded my kernel with M-bab's build from
  'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:

  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] 
[1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:380c]
  InstallationDate: Installed on 2018-03-07 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 81BR
  Package: xorg 1:7.7+19ubuntu5
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro pci=noaer 
ivrs_ioapic[4]=00:14.00 ivrs_ioapic[5]=00:00.01 quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18

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

apport information

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using mpv to play a video fullscreen, when I try to resume the
  window from fullscreen, the screen freezes. Same thing happens when I
  use cheese. Nothing I can do except a hard poweroff.

  I've manually upgraded my kernel with M-bab's build from
  'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:

  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] 
[1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:380c]
  InstallationDate: Installed on 2018-03-07 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 81BR
  Package: xorg 1:7.7+19ubuntu5
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro pci=noaer 
ivrs_ioapic[4]=00:14.00 ivrs_ioapic[5]=00:00.01 quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~r

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

apport information

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using mpv to play a video fullscreen, when I try to resume the
  window from fullscreen, the screen freezes. Same thing happens when I
  use cheese. Nothing I can do except a hard poweroff.

  I've manually upgraded my kernel with M-bab's build from
  'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:

  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] 
[1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:380c]
  InstallationDate: Installed on 2018-03-07 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 81BR
  Package: xorg 1:7.7+19ubuntu5
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro pci=noaer 
ivrs_ioapic[4]=00:14.00 ivrs_ioapic[5]=00:00.01 quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~r

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

apport information

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using mpv to play a video fullscreen, when I try to resume the
  window from fullscreen, the screen freezes. Same thing happens when I
  use cheese. Nothing I can do except a hard poweroff.

  I've manually upgraded my kernel with M-bab's build from
  'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:

  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] 
[1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:380c]
  InstallationDate: Installed on 2018-03-07 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 81BR
  Package: xorg 1:7.7+19ubuntu5
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro pci=noaer 
ivrs_ioapic[4]=00:14.00 ivrs_ioapic[5]=00:00.01 quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3

[Desktop-packages] [Bug 1751075] MonitorsUser.xml.txt

apport information

** Attachment added: "MonitorsUser.xml.txt"
   
https://bugs.launchpad.net/bugs/1751075/+attachment/5088120/+files/MonitorsUser.xml.txt

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using mpv to play a video fullscreen, when I try to resume the
  window from fullscreen, the screen freezes. Same thing happens when I
  use cheese. Nothing I can do except a hard poweroff.

  I've manually upgraded my kernel with M-bab's build from
  'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:

  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] 
[1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:380c]
  InstallationDate: Installed on 2018-03-07 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 81BR
  Package: xorg 1:7.7+19ubuntu5
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro pci=noaer 
ivrs_ioapic[4]=00:14.00 ivrs_ioapic[5]=00:00.01 quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dr

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

apport information

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using mpv to play a video fullscreen, when I try to resume the
  window from fullscreen, the screen freezes. Same thing happens when I
  use cheese. Nothing I can do except a hard poweroff.

  I've manually upgraded my kernel with M-bab's build from
  'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:

  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] 
[1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:380c]
  InstallationDate: Installed on 2018-03-07 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 81BR
  Package: xorg 1:7.7+19ubuntu5
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro pci=noaer 
ivrs_ioapic[4]=00:14.00 ivrs_ioapic[5]=00:00.01 quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mes

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

apport information

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using mpv to play a video fullscreen, when I try to resume the
  window from fullscreen, the screen freezes. Same thing happens when I
  use cheese. Nothing I can do except a hard poweroff.

  I've manually upgraded my kernel with M-bab's build from
  'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:

  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon Vega 8 Mobile] 
[1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Vega [Radeon Vega 8 Mobile] [17aa:380c]
  InstallationDate: Installed on 2018-03-07 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 81BR
  Package: xorg 1:7.7+19ubuntu5
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=a8a345d7-5b2e-495a-897a-351b10597e61 ro pci=noaer 
ivrs_ioapic[4]=00:14.00 ivrs_ioapic[5]=00:00.01 quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~r

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