[Desktop-packages] [Bug 2062995] [NEW] With nvidia-dkms-470 need GSK_RENDERER=cairo WEBKIT_DISABLE_DMABUF_RENDERER=1

2024-04-20 Thread Boris Gjenero
Public bug reported:

I have an Nvidia GeForce GT 710, which requires the legacy 470 proprietary 
driver. Both foliate and epiphany-browser display improperly by default. Some 
user interface elements are missing, and e-book and web pages are totally 
blank. To fix this, I added the following lines to /etc/environment :
GSK_RENDERER=cairo
WEBKIT_DISABLE_DMABUF_RENDERER=1

In the past WEBKIT_DISABLE_DMABUF_RENDERER=1 was enough, but in Ubuntu
24.04 I also require GSK_RENDERER=cairo.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: libwebkitgtk-6.0-4 2.44.0-2
ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
Uname: Linux 6.8.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sat Apr 20 18:57:04 2024
SourcePackage: webkit2gtk
UpgradeStatus: Upgraded to noble on 2024-04-17 (3 days ago)

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


** Tags: amd64 apport-bug noble

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

Title:
  With nvidia-dkms-470 need GSK_RENDERER=cairo
  WEBKIT_DISABLE_DMABUF_RENDERER=1

Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  I have an Nvidia GeForce GT 710, which requires the legacy 470 proprietary 
driver. Both foliate and epiphany-browser display improperly by default. Some 
user interface elements are missing, and e-book and web pages are totally 
blank. To fix this, I added the following lines to /etc/environment :
  GSK_RENDERER=cairo
  WEBKIT_DISABLE_DMABUF_RENDERER=1

  In the past WEBKIT_DISABLE_DMABUF_RENDERER=1 was enough, but in Ubuntu
  24.04 I also require GSK_RENDERER=cairo.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libwebkitgtk-6.0-4 2.44.0-2
  ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
  Uname: Linux 6.8.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Apr 20 18:57:04 2024
  SourcePackage: webkit2gtk
  UpgradeStatus: Upgraded to noble on 2024-04-17 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2062995/+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 2018184] Re: printer prints mirrored pages

2023-10-28 Thread Boris Erdmann
For me it's "HP Color LaserJet CP4520 Series". So, it affects at least
multiple printer types.

Related, but not the same:
https://bugs.launchpad.net/ubuntu/+source/libppd/+bug/2018538

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

Title:
  printer prints mirrored pages

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  After update to Ubuntu 23.04 (Lunar), my HP Color Laserjet CP1515n prints all 
pages mirrored.
  the problem gets even stranger when I select the "print mirrored" option in 
the printing dialog: Then, the first, third, fifth … pages get printed 
correctly, but the second, fourth, sixth … pages are *still* mirrored.

  The problem appeared in Lunar (hplip 3.22.10+dfsg0-1) and was not
  present in Kinetic (hplip 3.22.6+dfsg0-1).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: hplip 3.22.10+dfsg0-1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 30 12:58:17 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-13 (2694 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat: device for Farblaser: socket://192.168.1.8
  MachineType: LENOVO 34382AG
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Farblaser.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Farblaser.ppd: Permission denied
  ProcEnviron:
   LANG=de_DE.utf8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vg-lv--root ro noprompt quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (6 days ago)
  dmi.bios.date: 06/19/2018
  dmi.bios.release: 2.71
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB1WW (2.71 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34382AG
  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.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB1WW(2.71):bd06/19/2018:br2.71:efr1.14:svnLENOVO:pn34382AG:pvrThinkPadX230Tablet:rvnLENOVO:rn34382AG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3438:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 34382AG
  dmi.product.sku: LENOVO_MT_3438
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2018184/+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 2018184] Re: printer prints mirrored pages

2023-10-28 Thread Boris Erdmann
Still present in mantic, exactly as described in the bug report with
every 2nd page being mirrored etc.

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

Title:
  printer prints mirrored pages

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  After update to Ubuntu 23.04 (Lunar), my HP Color Laserjet CP1515n prints all 
pages mirrored.
  the problem gets even stranger when I select the "print mirrored" option in 
the printing dialog: Then, the first, third, fifth … pages get printed 
correctly, but the second, fourth, sixth … pages are *still* mirrored.

  The problem appeared in Lunar (hplip 3.22.10+dfsg0-1) and was not
  present in Kinetic (hplip 3.22.6+dfsg0-1).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: hplip 3.22.10+dfsg0-1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 30 12:58:17 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-13 (2694 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat: device for Farblaser: socket://192.168.1.8
  MachineType: LENOVO 34382AG
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Farblaser.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Farblaser.ppd: Permission denied
  ProcEnviron:
   LANG=de_DE.utf8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vg-lv--root ro noprompt quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (6 days ago)
  dmi.bios.date: 06/19/2018
  dmi.bios.release: 2.71
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB1WW (2.71 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34382AG
  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.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB1WW(2.71):bd06/19/2018:br2.71:efr1.14:svnLENOVO:pn34382AG:pvrThinkPadX230Tablet:rvnLENOVO:rn34382AG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3438:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 34382AG
  dmi.product.sku: LENOVO_MT_3438
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO

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

2023-10-24 Thread Boris-chiou
This is critical before, but it seems there is no update in the previous
14 years, so mark S3 for now.

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

Title:
  Firefox prints one page only of long doc in a frame

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

Bug description:
  Binary package hint: mozilla-firefox

  Firefox 3.01 printing: I have two frames, one containing a document that 
should take many pages to print. Firefox only prints one page, losing the rest. 
Typical site: http://www.cict.bhtafe.edu.au/subjects/ict321/bug.html
  It also prints one page for multi-frame documents from web access to M/S 
Exchange such as 
http://www.cict.bhtafe.edu.au/subjects/bug/MicrosoftOutlookWebAccess.html
  Another problem site is 
http://septemberfestival.com.au/index.php?option=com_content=view=4=4
 which prints three pages but still loses a lot of content

  Package is Ubuntu 8.10 alpha5, but problem has occurred in many other
  distros and earlier versions of firefox.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/271216/+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 1903277] Re: language layout switch does not work

2023-07-15 Thread Boris Rybalkin
Actually I do not understand it myself either now :)
All I know it does not happen anymore, can we close this please?

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

Title:
  language layout switch does not work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When switching language to Russian I still can only type English.
  It happens sometimes and reboot helps to fix it for some time (hours days).
  This is always on machine with on/off screen.
  See the screenshot.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903277/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)

2022-09-01 Thread Boris Steiner
This issue is caused by lightdm running /usr/sbin/lightdm-session
instead of /etc/X11/Xsession.

The simplest workaround for me was:
- introduce has_option functon as 1st step in Xsession.d sourced scripts
- as root create file /etc/X11/Xsession.d/01custom-has-option with following 
content:

#check if has_option is already defined; if not, define

has_option 2>1 > /dev/null || has_option() {
  # Ensure that a later no-foo overrides an earlier foo
  if [ "$(echo "$OPTIONS" | grep -Eo "^(no-)?$1\>" | tail -n 1)" = "$1" ]; then
return 0
  else
return 1
  fi
}

- logout and login

Details:
- /etc/X11/Xsession introduces has_option shell function that check if 
Xsession.options contains predefined option
- /etc/X11/Xsession sources all files under /etc/X11/Xsession.d in alphabetic 
order
- as the scripts are sourced they maintain the same environemnt and definitions 
of variables or functions as Xsession
- however, lightdm uses lightdm-session that also sources /etc/X11/Xsession.d/* 
BUT does NOT define has_option function
- provided script checks if the function has_option already exists (Xsession is 
in play) and if not (lightdm-session's game) it defines it the same way as is 
in /etc/X11/Xsession

Alternative solutions:
- modify lightdm-session to contain has_option the same way as /etc/X11/Xsession
- modify (create) /etc/lightdm/lightdm.conf containing:
[Seat:*]
session-wrapper=/etc/X11/Xsession

- requires reboot; it did not work ok for 100% as my .profile env vars
were not correctly propagated

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

Title:
  ssh-agent fails to start (has_option: command not found)

Status in Light Display Manager:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have been using ssh-agent for years and since I upgraded my system
  to Ubuntu 21.04/groovy, ssh-agent fails to start.

  Here is the error message:

  # journalctl | grep ssh-agent
  [...]
  Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: 
/etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: x11-common 1:7.7+22ubuntu1
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr  3 09:02:46 2021
  Dependencies: lsb-base 11.1.0ubuntu2
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1]
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR
  dmi.board.name: NS50MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1955135] Re: multiple issues with /etc/X11/Xsession.d/ - "has_option: command not found"

2022-09-01 Thread Boris Steiner
*** This bug is a duplicate of bug 1922414 ***
https://bugs.launchpad.net/bugs/1922414

This issue is caused by lightdm running /usr/sbin/lightdm-session
instead of /etc/X11/Xsession.


The simplest workaround for me was:
- introduce has_option functon as 1st step in Xsession.d sourced scripts
- as root create file /etc/X11/Xsession.d/01custom-has-option with following 
content:

#check if has_option is already defined; if not, define

has_option 2>1 > /dev/null || has_option() {
  # Ensure that a later no-foo overrides an earlier foo
  if [ "$(echo "$OPTIONS" | grep -Eo "^(no-)?$1\>" | tail -n 1)" = "$1" ]; then
return 0
  else
return 1
  fi
}


- logout and login

Details:
- /etc/X11/Xsession introduces has_option shell function that check if 
Xsession.options contains predefined option
- /etc/X11/Xsession sources all files under /etc/X11/Xsession.d in alphabetic 
order
- as the scripts are sourced they maintain the same environemnt and definitions 
of variables or functions as Xsession
- however, lightdm uses lightdm-session that also sources /etc/X11/Xsession.d/* 
BUT does NOT define has_option function
- provided script checks if the function has_option already exists (Xsession is 
in play) and if not  (lightdm-session's game) it defines it the same way as is 
in /etc/X11/Xsession

Alternative solutions:
- modify lightdm-session to contain has_option the same way as /etc/X11/Xsession
- modify (create) /etc/lightdm/lightdm.conf containing:
[Seat:*]
session-wrapper=/etc/X11/Xsession

- requires reboot; it did not work ok for 100% as my .profile env vars
were not correctly propagated

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

Title:
  multiple issues with /etc/X11/Xsession.d/ - "has_option: command not
  found"

Status in dbus package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Boot 20211217 Ubuntu MATE daily ISO
  2. Open ~/.xsession-errors

  Expected results:
  * no errors and warnings 

  Actual results:
  * there are two errors about xorg:

  /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not 
found
  /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: x11-common 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Dec 17 14:22:15 2021
  Dependencies: lsb-base 11.1.0ubuntu3
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation GF108M [GeForce GT 425M] [104d:907a]
  LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211217)
  MachineType: Sony Corporation VPCF13Z1R
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2010
  dmi.bios.release: 1.90
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0190Y9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 1.90
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:br1.90:efr1.90:svnSonyCorporation:pnVPCF13Z1R:pvrC606GZYK:skuN/A:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCF13Z1R
  dmi.product.sku: N/A
  dmi.product.version: C606GZYK
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1


[Desktop-packages] [Bug 1976249] Re: `xvfb-run` doesn't support `--auto-display`

2022-08-03 Thread Boris Petrov
There is no "problem" per se. It's just that Ubuntu's version of `xvfb-
run` is not really compatible/consistent with the one in other distros.
Some distros have deprecated `--auto-servernum` in favor of a different
setting `--auto-display` which I guess does something "better". I'm just
saying that Ubuntu's package could be updated to be more in-line with
others.

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

Title:
  `xvfb-run` doesn't support `--auto-display`

Status in xorg-server package in Ubuntu:
  New

Bug description:
  `xvfb` is at version `2:21.1.3-2ubuntu2` which is the latest one.
  However, `xvfb-run -h` doesn't show the `--auto-display` argument and
  running `xvfb-run --auto-display ls` leads to `xvfb-run: unrecognized
  option '--auto-display'`. This is strange because in Arch Linux, the
  same `xvfb-run` version does support `--auto-display`. On Ubuntu one
  must use `--auto-servernum` because of that but that has been
  deprecated for quite a while now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1976249/+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 1976249] Re: `xvfb-run` doesn't support `--auto-display`

2022-06-08 Thread Boris Petrov
** Summary changed:

- `xvfb-run` doesn't support `--auto-servernum`
+ `xvfb-run` doesn't support `--auto-display`

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

Title:
  `xvfb-run` doesn't support `--auto-display`

Status in xorg-server package in Ubuntu:
  New

Bug description:
  `xvfb` is at version `2:21.1.3-2ubuntu2` which is the latest one.
  However, `xvfb-run -h` doesn't show the `--auto-display` argument and
  running `xvfb-run --auto-display ls` leads to `xvfb-run: unrecognized
  option '--auto-display'`. This is strange because in Arch Linux, the
  same `xvfb-run` version does support `--auto-display`. On Ubuntu one
  must use `--auto-servernum` because of that but that has been
  deprecated for quite a while now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1976249/+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 1976249] Re: `xvfb-run` doesn't support `--auto-servernum`

2022-05-30 Thread Boris Petrov
Hi, thanks for the response! I'm also not sure how this package works,
where is its source, where is the upstream, etc. However, as I said, on
Arch Linux `auto-servernum` is marked as deprecated. Googling `auto-
display` leads to some information (also on other distros):

https://bugs.archlinux.org/task/65039
https://bugzilla.redhat.com/show_bug.cgi?id=1787684

** Bug watch added: Red Hat Bugzilla #1787684
   https://bugzilla.redhat.com/show_bug.cgi?id=1787684

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

Title:
  `xvfb-run` doesn't support `--auto-servernum`

Status in xorg-server package in Ubuntu:
  New

Bug description:
  `xvfb` is at version `2:21.1.3-2ubuntu2` which is the latest one.
  However, `xvfb-run -h` doesn't show the `--auto-display` argument and
  running `xvfb-run --auto-display ls` leads to `xvfb-run: unrecognized
  option '--auto-display'`. This is strange because in Arch Linux, the
  same `xvfb-run` version does support `--auto-display`. On Ubuntu one
  must use `--auto-servernum` because of that but that has been
  deprecated for quite a while now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1976249/+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 1976249] [NEW] `xvfb-run` doesn't support `--auto-servernum`

2022-05-30 Thread Boris Petrov
Public bug reported:

`xvfb` is at version `2:21.1.3-2ubuntu2` which is the latest one.
However, `xvfb-run -h` doesn't show the `--auto-display` argument and
running `xvfb-run --auto-display ls` leads to `xvfb-run: unrecognized
option '--auto-display'`. This is strange because in Arch Linux, the
same `xvfb-run` version does support `--auto-display`. On Ubuntu one
must use `--auto-servernum` because of that but that has been deprecated
for quite a while now.

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

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

Title:
  `xvfb-run` doesn't support `--auto-servernum`

Status in xorg-server package in Ubuntu:
  New

Bug description:
  `xvfb` is at version `2:21.1.3-2ubuntu2` which is the latest one.
  However, `xvfb-run -h` doesn't show the `--auto-display` argument and
  running `xvfb-run --auto-display ls` leads to `xvfb-run: unrecognized
  option '--auto-display'`. This is strange because in Arch Linux, the
  same `xvfb-run` version does support `--auto-display`. On Ubuntu one
  must use `--auto-servernum` because of that but that has been
  deprecated for quite a while now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1976249/+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 1968827] [NEW] Pulseaudio disables auto mute, so speaker sound continues when headphones plugged in

2022-04-12 Thread Boris Gjenero
Public bug reported:

My Dell Inspiron 6400 laptop has HDA Intel audio with a STAC9200 codec.
It has speakers and a headphone jack. Previously when the headphone jack
was unplugged sound came from the speakers, and when headphones were
plugged in, sound came only from the headphones. In Ubuntu 22.04, when I
plug in the headphones, sound comes from both the speakers and
headphones.

ALSA has the "Auto-Mute" feature, which mutes the speakers when
headphones are plugged in. The problem is that Pulseaudio disables this
feature. Every time I plug in headphones, I need to again re-enable that
feature using alsamixer to stop sound from speakers.

The problem seems to be this unfixed bug in Pulseaudio:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1297

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bgjenero  15920 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed Apr 13 00:57:54 2022
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to jammy on 2022-04-04 (8 days ago)
dmi.bios.date: 06/13/2007
dmi.bios.release: 1.7
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0XD720
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.7
dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:br1.7:efr1.7:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:sku:
dmi.product.name: MM061
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug jammy

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

Title:
  Pulseaudio disables auto mute, so speaker sound continues when
  headphones plugged in

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  My Dell Inspiron 6400 laptop has HDA Intel audio with a STAC9200
  codec. It has speakers and a headphone jack. Previously when the
  headphone jack was unplugged sound came from the speakers, and when
  headphones were plugged in, sound came only from the headphones. In
  Ubuntu 22.04, when I plug in the headphones, sound comes from both the
  speakers and headphones.

  ALSA has the "Auto-Mute" feature, which mutes the speakers when
  headphones are plugged in. The problem is that Pulseaudio disables
  this feature. Every time I plug in headphones, I need to again re-
  enable that feature using alsamixer to stop sound from speakers.

  The problem seems to be this unfixed bug in Pulseaudio:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1297

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bgjenero  15920 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Apr 13 00:57:54 2022
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to jammy on 2022-04-04 (8 days ago)
  dmi.bios.date: 06/13/2007
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XD720
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:br1.7:efr1.7:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:sku:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1968827/+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 1926316] Re: lxappearance crashes on launch

2021-05-15 Thread Boris Gjenero
This also fixes the Lxdm greeter crash I reported at
https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1922443. I installed
the pre-release builds from
https://launchpad.net/ubuntu/+source/glib2.0/2.68.1-1~ubuntu21.04.1/+build/21536716
and confirm that the bug is fixed.

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

Title:
  lxappearance crashes on launch

Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  Backtrace of the segmentation fault

  Program received signal SIGSEGV, Segmentation fault.
  0x7790c79d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  (gdb) bt
  #0  0x7790c79d in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #1  0x7790ccc1 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x7790cf41 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x7790d079 in g_key_file_load_from_file () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x55407072 in load_icon_themes_from_dir ()
  #5  0x554073dd in icon_theme_init ()
  #6  0x55404c92 in main ()

  Strace shows that the programs borks while trying to load the icon
  theme "/usr/share/icons/gnome/index.theme".

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lxappearance 0.6.3-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Config_System_openbox: Error: [Errno 2] No such file or directory: 
'/etc/xdg/lxsession/openbox/desktop.conf'
  CurrentDesktop: lxde
  Date: Tue Apr 27 21:47:03 2021
  Icons_Default: No icons theme configured by default
  InstallationDate: Installed on 2021-01-12 (105 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: lxappearance
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1926316/+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 1926316] Re: lxappearance crashes on launch

2021-05-01 Thread Boris Gjenero
Seems this should also fix LXDM GTK greeter:
https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1922443

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

Title:
  lxappearance crashes on launch

Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  Backtrace of the segmentation fault

  Program received signal SIGSEGV, Segmentation fault.
  0x7790c79d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  (gdb) bt
  #0  0x7790c79d in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #1  0x7790ccc1 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x7790cf41 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x7790d079 in g_key_file_load_from_file () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x55407072 in load_icon_themes_from_dir ()
  #5  0x554073dd in icon_theme_init ()
  #6  0x55404c92 in main ()

  Strace shows that the programs borks while trying to load the icon
  theme "/usr/share/icons/gnome/index.theme".

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lxappearance 0.6.3-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Config_System_openbox: Error: [Errno 2] No such file or directory: 
'/etc/xdg/lxsession/openbox/desktop.conf'
  CurrentDesktop: lxde
  Date: Tue Apr 27 21:47:03 2021
  Icons_Default: No icons theme configured by default
  InstallationDate: Installed on 2021-01-12 (105 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: lxappearance
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1926316/+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 1916074] [NEW] Firefox has border if started with kwin compositing disabled

2021-02-18 Thread Boris Gjenero
Public bug reported:

If I start Firefox with in KDE Plasma with kwin compositing disabled,
and the Firefox title bar is disabled via Customize, the whole window
has a border. Otherwise my computer is configured to not have window
borders, and other applications don't have such a border. I don't know
how to make that border go away, besides enabling compositing. Playing
with #main-window in userChrome.css shows that the border and margin I
can set there exists inside the border which I'm trying to remove.

KWin has a hotkey for toggling compositing, found in Global Shortcuts.
Default seems to be Alt+Shift+F12. Toggling compositing doesn't seem to
change this immediately. What matters is the state of compositing when
Firefox was started.

I'm attaching a screenshot showing this border.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: firefox 85.0.1+build1-0ubuntu0.20.10.1 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  bgjenero   1908 F pulseaudio
 /dev/snd/controlC0:  bgjenero   1908 F pulseaudio
 /dev/snd/controlC1:  bgjenero   1908 F pulseaudio
BuildID: 20210204182252
CasperMD5CheckResult: skip
Channel: release
CurrentDesktop: KDE
Date: Thu Feb 18 15:15:39 2021
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
IpRoute:
 default via 192.168.1.1 dev eth0 proto static 
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.44
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-99b8dfa6-8d6d-4541-919c-7d2960210213
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
PrefSources:
 /usr/lib/firefox/defaults/pref/vendor-gre.js
 /usr/lib/firefox/defaults/pref/channel-prefs.js
 prefs.js
 user.js
Profiles: Profile0 (Default) - LastVersion=85.0.1/20210204182252 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
SubmittedCrashIDs:
 bp-99b8dfa6-8d6d-4541-919c-7d2960210213
 bp-f8fe1ebe-97ed-4eec-8e60-11f5d0210118
 bp-e9cbbf6c-3c3f-430d-83ce-a0fca0210101
 bp-f2129335-9559-437d-b537-6f4830210101
 bp-70bc911e-707f-4f53-93fe-f2ebf0210101
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to groovy on 2020-10-22 (119 days ago)
dmi.bios.date: 06/19/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F13
dmi.board.name: P35-DS3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P35-DS3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug groovy release-channel third-party-packages

** Attachment added: "Screenshot showing border."
   
https://bugs.launchpad.net/bugs/1916074/+attachment/5464856/+files/Screenshot_2021-02-18_15-18-16.png

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

Title:
  Firefox has border if started with kwin compositing disabled

Status in firefox package in Ubuntu:
  New

Bug description:
  If I start Firefox with in KDE Plasma with kwin compositing disabled,
  and the Firefox title bar is disabled via Customize, the whole window
  has a border. Otherwise my computer is configured to not have window
  borders, and other applications don't have such a border. I don't know
  how to make that border go away, besides enabling compositing. Playing
  with #main-window in userChrome.css shows that the border and margin I
  can set there exists inside the border which I'm trying to remove.

  KWin has a hotkey for toggling compositing, found in Global Shortcuts.
  Default seems to be Alt+Shift+F12. Toggling compositing doesn't seem
  to change this immediately. What matters is the state of compositing
  when Firefox was started.

  I'm attaching a screenshot showing this border.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: firefox 85.0.1+build1-0ubuntu0.20.10.1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  bgjenero   1908 F pulseaudio
   /dev/snd/controlC0:  bgjenero   1908 

[Desktop-packages] [Bug 1912030] Re: Crash unless ffmpeg direct rendering disabled with ATI X1400

2021-01-17 Thread Boris Gjenero
But, not all VLC video outputs are supposed to use OpenGL, so I don't
see why Mesa is relevant. One of the crash backtraces doesn't involve
Mesa.

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

Title:
  Crash unless ffmpeg direct rendering disabled with ATI X1400

Status in mesa package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 20.10, VLC started crashing when I tried to
  play video. I tried changing to different video output methods, but
  none of them worked. In the past, I remember several methods working
  fine.

  In the ffmpeg advanced preferences page, disabling the direct
  rendering option made video playback work.

  I thought the vaapi errors VLC reports had something to do with it,
  but apparently not, because they still happen with successful
  playback. This is on a Dell Inspiron 6400 with ATI Mobility Radeon
  X1400, which doesn't support hardware decoding of the H.264 video I'm
  trying to play.

  Here's one backtrace:
  Thread 26 "vlc" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fff880df640 (LWP 11335)]
  __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:104
  104 ../sysdeps/x86_64/multiarch/memcpy-ssse3.S: No such file or directory.
  (gdb) bt
  #0  __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:104
  #1  0x77d03fc2 in picture_CopyPixels ()
  at /usr/lib/x86_64-linux-gnu/libvlccore.so.9
  #2  0x77d04016 in picture_Copy ()
  at /usr/lib/x86_64-linux-gnu/libvlccore.so.9
  #3  0x77cdf1ea in  () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9
  #4  0x77ce1438 in  () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9
  #5  0x77f67590 in start_thread (arg=0x7fff880df640)
  at pthread_create.c:463
  #6  0x77e87223 in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  Also another:
  #0  __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:104
  #1  0x7fffc7022bff in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
  #2  0x7fffc74f1d66 in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
  #3  0x7fffc6b41317 in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
  #4  0x7fffc6cb4b07 in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
  #5  0x7fffc6cb7dcc in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
  #6  0x7fffc6cbd9d9 in  () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so
  #7  0x7fff885b2eee in  ()
  at /usr/lib/x86_64-linux-gnu/vlc/plugins/video_output/libgles2_plugin.so
  #8  0x7fff885ad2c5 in  ()
  at /usr/lib/x86_64-linux-gnu/vlc/plugins/video_output/libgles2_plugin.so
  #9  0x7fff885b3cee in  ()
  at /usr/lib/x86_64-linux-gnu/vlc/plugins/video_output/libgles2_plugin.so
  #10 0x77cdf4e6 in  () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9
  #11 0x77ce1438 in  () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9
  #12 0x77f67590 in start_thread (arg=0x7fff886bb640)
  at pthread_create.c:463
  #13 0x77e87223 in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: vlc 3.0.11.1-2
  ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Jan 15 18:46:42 2021
  InstallationDate: Installed on 2012-01-19 (3284 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: vlc
  UpgradeStatus: Upgraded to groovy on 2020-10-21 (86 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1912030/+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 1909818] Re: Printer stops working with a message "No suitable destinatin host found by cups-browsed""

2021-01-01 Thread Boris Rybalkin
** Description changed:

- I have a "Brother DCP 9020 CDW" network printer. 
+ I have a "Brother DCP 9020 CDW" network printer.
  Most of the time it is working fine, but sometimes I cannot print and I get 
this message in any app (Firefox, Document Viewer):
  
  "No suitable destination host found by cups-browsed"
  
  Then I restart printer and I get a second entry in printer list:
  
  1. Brother-DCP-9020CDW which says "Getting printer information ..." and print 
button disabled
  2. Brother_DCP_9020CDW which says "No suitable destination host found by 
cups-browsed" and print button enabled but all print jobs are paused.
  
- 
- Then I reboot my PC and things get back to normal.
+ Then I reboot my PC and then restart printer and then things get back to
+ normal.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: cups-browsed 1.28.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CupsErrorLog:
-  E [01/Jan/2021:16:05:51 +] [Job 1] No suitable destination host found by 
cups-browsed.
-  E [01/Jan/2021:16:05:51 +] [Job 1] Job held for 300 seconds since it 
could not be sent.
-  E [01/Jan/2021:16:10:52 +] [Job 1] No suitable destination host found by 
cups-browsed.
-  E [01/Jan/2021:16:10:52 +] [Job 1] Job held for 300 seconds since it 
could not be sent.
+  E [01/Jan/2021:16:05:51 +] [Job 1] No suitable destination host found by 
cups-browsed.
+  E [01/Jan/2021:16:05:51 +] [Job 1] Job held for 300 seconds since it 
could not be sent.
+  E [01/Jan/2021:16:10:52 +] [Job 1] No suitable destination host found by 
cups-browsed.
+  E [01/Jan/2021:16:10:52 +] [Job 1] Job held for 300 seconds since it 
could not be sent.
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  1 16:13:14 2021
  InstallationDate: Installed on 2020-12-15 (16 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lpstat: device for Brother_DCP_9020CDW: implicitclass://Brother_DCP_9020CDW/
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Brother_DCP_9020CDW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Brother_DCP_9020CDW.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=2426cc97-af0d-4826-80aa-a05ec1ef1e8e ro quiet splash vt.handoff=7
  SourcePackage: cups-filters
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.70
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M MORTAR MAX (MS-7B89)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.70:bd04/21/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B89
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

Title:
  Printer stops working with a message "No suitable destinatin host
  found by cups-browsed""

Status in cups-filters package in Ubuntu:
  New

Bug description:
  I have a "Brother DCP 9020 CDW" network printer.
  Most of the time it is working fine, but sometimes I cannot print and I get 
this message in any app (Firefox, Document Viewer):

  "No suitable destination host found by cups-browsed"

  Then I restart printer and I get a second entry in printer list:

  1. Brother-DCP-9020CDW which says "Getting printer information ..." and print 
button disabled
  2. Brother_DCP_9020CDW which says "No suitable destination host found by 
cups-browsed" and print button enabled but all print jobs are paused.

  Then I reboot my PC and then restart printer and then things get back
  to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: cups-browsed 1.28.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CupsErrorLog:
   E [01/Jan/2021:16:05:51 +] [Job 1] No suitable destination host found by 
cups-browsed.
   E [01/Jan/2021:16:05:51 +] [Job 1] Job held for 300 seconds since it 
could not be sent.
   E [01/Jan/2021:16:10:52 +] [Job 1] No 

[Desktop-packages] [Bug 1909818] [NEW] Printer stops working with a message "No suitable destinatin host found by cups-browsed""

2021-01-01 Thread Boris Rybalkin
Public bug reported:

I have a "Brother DCP 9020 CDW" network printer.
Most of the time it is working fine, but sometimes I cannot print and I get 
this message in any app (Firefox, Document Viewer):

"No suitable destination host found by cups-browsed"

Then I restart printer and I get a second entry in printer list:

1. Brother-DCP-9020CDW which says "Getting printer information ..." and print 
button disabled
2. Brother_DCP_9020CDW which says "No suitable destination host found by 
cups-browsed" and print button enabled but all print jobs are paused.

Then I reboot my PC and then restart printer and then things get back to
normal.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: cups-browsed 1.28.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
CupsErrorLog:
 E [01/Jan/2021:16:05:51 +] [Job 1] No suitable destination host found by 
cups-browsed.
 E [01/Jan/2021:16:05:51 +] [Job 1] Job held for 300 seconds since it could 
not be sent.
 E [01/Jan/2021:16:10:52 +] [Job 1] No suitable destination host found by 
cups-browsed.
 E [01/Jan/2021:16:10:52 +] [Job 1] Job held for 300 seconds since it could 
not be sent.
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan  1 16:13:14 2021
InstallationDate: Installed on 2020-12-15 (16 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Lpstat: device for Brother_DCP_9020CDW: implicitclass://Brother_DCP_9020CDW/
MachineType: Micro-Star International Co., Ltd. MS-7B89
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Brother_DCP_9020CDW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Brother_DCP_9020CDW.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=2426cc97-af0d-4826-80aa-a05ec1ef1e8e ro quiet splash vt.handoff=7
SourcePackage: cups-filters
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2020
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.70
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M MORTAR MAX (MS-7B89)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.70:bd04/21/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B89
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug groovy

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

Title:
  Printer stops working with a message "No suitable destinatin host
  found by cups-browsed""

Status in cups-filters package in Ubuntu:
  New

Bug description:
  I have a "Brother DCP 9020 CDW" network printer.
  Most of the time it is working fine, but sometimes I cannot print and I get 
this message in any app (Firefox, Document Viewer):

  "No suitable destination host found by cups-browsed"

  Then I restart printer and I get a second entry in printer list:

  1. Brother-DCP-9020CDW which says "Getting printer information ..." and print 
button disabled
  2. Brother_DCP_9020CDW which says "No suitable destination host found by 
cups-browsed" and print button enabled but all print jobs are paused.

  Then I reboot my PC and then restart printer and then things get back
  to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: cups-browsed 1.28.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CupsErrorLog:
   E [01/Jan/2021:16:05:51 +] [Job 1] No suitable destination host found by 
cups-browsed.
   E [01/Jan/2021:16:05:51 +] [Job 1] Job held for 300 seconds since it 
could not be sent.
   E [01/Jan/2021:16:10:52 +] [Job 1] No suitable destination host found by 
cups-browsed.
   E [01/Jan/2021:16:10:52 +] [Job 1] Job held for 300 seconds since it 
could not be sent.
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  1 16:13:14 2021
  InstallationDate: Installed on 2020-12-15 (16 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lpstat: device for Brother_DCP_9020CDW: implicitclass://Brother_DCP_9020CDW/
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  

[Desktop-packages] [Bug 1909108] [NEW] Second static mouse pointer on two screen setup

2020-12-23 Thread Boris Rybalkin
Public bug reported:

I have two screens and a Bluetooth mouse. When I wake PC up from the suspend 
the second frozen cursor is left on the screen.
Screenshot tool does not see it.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 23 11:06:00 2020
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] [1002:67e3] 
(prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 
4100] [1002:0b0d]
InstallationDate: Installed on 2020-12-15 (7 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: Micro-Star International Co., Ltd. MS-7B89
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=2426cc97-af0d-4826-80aa-a05ec1ef1e8e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2020
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.70
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M MORTAR MAX (MS-7B89)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.70:bd04/21/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B89
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug groovy ubuntu

** Attachment added: "IMG_20201223_111820-1.jpg"
   
https://bugs.launchpad.net/bugs/1909108/+attachment/5446192/+files/IMG_20201223_111820-1.jpg

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

Title:
  Second static mouse pointer on two screen setup

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two screens and a Bluetooth mouse. When I wake PC up from the suspend 
the second frozen cursor is left on the screen.
  Screenshot tool does not see it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 23 11:06:00 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] 
[1002:67e3] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 
4100] [1002:0b0d]
  InstallationDate: Installed on 2020-12-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=2426cc97-af0d-4826-80aa-a05ec1ef1e8e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.70
  dmi.board.asset.tag: To be 

[Desktop-packages] [Bug 1907479] [NEW] Mouse movement stops after switching to text VT and back to X

2020-12-09 Thread Boris Gjenero
Public bug reported:

My Dell Inspiron 6400 laptop has a Synaptics touchpad. If I'm using
xserver-xorg-input-synaptics and I use Control-Alt-Fkey or sudo chvt to
switch to a text virtual console and then switch back to X, the mouse
stops moving via the touchpad. The touchpad seems totally ignored, and I
can't tap to click either. However, the two physical mouse buttons
located below the touchpad continue to work properly. Also, sudo evtest
shows that touchpad events are still delivered by the kernel.

If I apt purge xserver-xorg-input-synaptics and use the touchpad like a
generic mouse, this does not happen. If I do that and then install
xserver-xorg-input-libinput, using the touchpad via libinput, this also
does not happen.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
Uname: Linux 5.8.0-31-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Wed Dec  9 11:32:34 2020
DistUpgraded: 2020-10-21 19:30:44,581 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: groovy
DistroVariant: ubuntu
InstallationDate: Installed on 2012-01-19 (3247 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M
MachineType: Dell Inc. MM061
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-31-generic 
root=UUID=d590f141-7b8d-421d-84b3-baa43181a241 ro resume=/dev/sda5
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: Upgraded to groovy on 2020-10-21 (48 days ago)
dmi.bios.date: 06/13/2007
dmi.bios.release: 1.7
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0XD720
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.7
dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:br1.7:efr1.7:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MM061
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy ubuntu

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

Title:
  Mouse movement stops after switching to text VT and back to X

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  My Dell Inspiron 6400 laptop has a Synaptics touchpad. If I'm using
  xserver-xorg-input-synaptics and I use Control-Alt-Fkey or sudo chvt
  to switch to a text virtual console and then switch back to X, the
  mouse stops moving via the touchpad. The touchpad seems totally
  ignored, and I can't tap to click either. However, the two physical
  mouse buttons located below the touchpad continue to work properly.
  Also, sudo evtest shows that touchpad events are still delivered by
  the kernel.

  If I apt purge xserver-xorg-input-synaptics and use the touchpad like
  a generic mouse, this does not happen. If I do that and then install
  xserver-xorg-input-libinput, using the touchpad via libinput, this
  also does not happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
  Uname: Linux 5.8.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Dec  9 11:32:34 2020
  DistUpgraded: 2020-10-21 19:30:44,581 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: groovy
  DistroVariant: ubuntu
  InstallationDate: Installed on 

[Desktop-packages] [Bug 141081] Re: Firefox opens 2 extra tabs on middle button click

2020-11-13 Thread Boris Rybalkin
Thank you very much, sorry for that :)

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

Title:
  Firefox opens 2 extra tabs on middle button click

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  Whenever i click the middle mouse button (scroll wheel) on a weblink
  to open a new tab firefox opens 2 additional tabs of the same thing.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Sep 19 16:48:46 2007
  DistroRelease: Ubuntu 7.04
  Package: firefox 2.0.0.6+1-0ubuntu1
  PackageArchitecture: i386
  SourcePackage: firefox
  Uname: Linux jack-desktop 2.6.22.6-custom #1 Fri Sep 7 21:19:59 EDT 2007 i686 
GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/141081/+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 141081] Re: Firefox opens 2 extra tabs on middle button click

2020-11-12 Thread Boris Rybalkin
Hi, it actually shows two events sometimes:

xev -event button 
Outer window is 0x341, inner window is 0x342

ButtonPress event, serial 25, synthetic NO, window 0x341,
root 0x57c, subw 0x342, time 192169015, (41,34), root:(803,559),
state 0x10, button 2, same_screen YES

ButtonRelease event, serial 25, synthetic NO, window 0x341,
root 0x57c, subw 0x342, time 192169071, (41,34), root:(803,559),
state 0x210, button 2, same_screen YES

ButtonPress event, serial 25, synthetic NO, window 0x341,
root 0x57c, subw 0x342, time 192169096, (41,34), root:(803,559),
state 0x10, button 2, same_screen YES

ButtonRelease event, serial 25, synthetic NO, window 0x341,
root 0x57c, subw 0x342, time 192169191, (41,34), root:(803,559),
state 0x210, button 2, same_screen YES

ClientMessage event, serial 25, synthetic YES, window 0x341,
message_type 0x146 (WM_PROTOCOLS), format 32, message 0x144 
(WM_DELETE_WINDOW)

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

Title:
  Firefox opens 2 extra tabs on middle button click

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  Whenever i click the middle mouse button (scroll wheel) on a weblink
  to open a new tab firefox opens 2 additional tabs of the same thing.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Sep 19 16:48:46 2007
  DistroRelease: Ubuntu 7.04
  Package: firefox 2.0.0.6+1-0ubuntu1
  PackageArchitecture: i386
  SourcePackage: firefox
  Uname: Linux jack-desktop 2.6.22.6-custom #1 Fri Sep 7 21:19:59 EDT 2007 i686 
GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/141081/+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 141081] Re: Firefox opens 2 extra tabs on middle button click

2020-11-10 Thread Boris Rybalkin
Yes, just did, restart in safe mode. Also removed all the extensions before 
that.
Issue still persists.

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

Title:
  Firefox opens 2 extra tabs on middle button click

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  Whenever i click the middle mouse button (scroll wheel) on a weblink
  to open a new tab firefox opens 2 additional tabs of the same thing.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Sep 19 16:48:46 2007
  DistroRelease: Ubuntu 7.04
  Package: firefox 2.0.0.6+1-0ubuntu1
  PackageArchitecture: i386
  SourcePackage: firefox
  Uname: Linux jack-desktop 2.6.22.6-custom #1 Fri Sep 7 21:19:59 EDT 2007 i686 
GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/141081/+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 141081] Re: Firefox opens 2 extra tabs on middle button click

2020-11-06 Thread Boris Rybalkin
Firefox: 82.0 (64-bit)
Ubuntu 20.04.1 LTS

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

Title:
  Firefox opens 2 extra tabs on middle button click

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  Whenever i click the middle mouse button (scroll wheel) on a weblink
  to open a new tab firefox opens 2 additional tabs of the same thing.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Sep 19 16:48:46 2007
  DistroRelease: Ubuntu 7.04
  Package: firefox 2.0.0.6+1-0ubuntu1
  PackageArchitecture: i386
  SourcePackage: firefox
  Uname: Linux jack-desktop 2.6.22.6-custom #1 Fri Sep 7 21:19:59 EDT 2007 i686 
GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/141081/+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 141081] Re: Firefox opens 2 extra tabs on middle button click

2020-11-06 Thread Boris Rybalkin
This issue just started to happen to me.
Sometimes opens two or even three tabs of the same thing.

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

Title:
  Firefox opens 2 extra tabs on middle button click

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  Whenever i click the middle mouse button (scroll wheel) on a weblink
  to open a new tab firefox opens 2 additional tabs of the same thing.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Sep 19 16:48:46 2007
  DistroRelease: Ubuntu 7.04
  Package: firefox 2.0.0.6+1-0ubuntu1
  PackageArchitecture: i386
  SourcePackage: firefox
  Uname: Linux jack-desktop 2.6.22.6-custom #1 Fri Sep 7 21:19:59 EDT 2007 i686 
GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/141081/+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 1894712] [NEW] No sound on Ubuntu 18.04 regardless of any action

2020-09-07 Thread Boris Godunov
Public bug reported:

I've had some trouble with sound recently after an update, it won't turn
on. I've tried numerous things: from playing around with alsamixer,
pulseaudio, pavucontrol to alsa force-reload and reinstalling alsamixer
and pulseaudio. No result. It displays everything correctly and seems to
be working, but the sound won't come out. On Windows it works perfectly.
It did work well before, it just turned off unexpectedly.

I have a dual boot Ubuntu 18.04 with Windows 10, maybe that causes the bug.
I think so because I've had some trouble with my wi-fi adapter not found, which 
was caused by Windows fast-boot option enabled.

I've asked questions on askubuntu and linux stackexchange, no one knows.
Someone suggested that I need to report a bug, and that's what I'm
doing. I'm attaching link to the question, as I posted some information
there:

https://unix.stackexchange.com/questions/608305/no-sound-on-
ubuntu-18-04-after-a-system-update

I am not sure what I can do now to enable it...
Please help.

$ lsb_release -rd:

Description:Ubuntu 18.04.5 LTS
Release:18.04

$ cat /proc/asound/version:

Advanced Linux Sound Architecture Driver Version k5.4.0-45-generic.

$ aplay --version:

aplay: version 1.1.3 by Jaroslav Kysela 

I hope that I have given enough info about the bug, however if anything
else is required, please feel free to ask me. Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-45.49~18.04.2-generic 5.4.55
Uname: Linux 5.4.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  fortminor   2055 F pulseaudio
 /dev/snd/controlC0:  fortminor   2055 F pulseaudio
 /dev/snd/controlC1:  fortminor   2055 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep  7 15:23:50 2020
InstallationDate: Installed on 2020-08-27 (10 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed
Symptom_Card: HD-Audio Generic - HD-Audio Generic
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [ROG Zephyrus G15 GA502IV_GA502IV, Realtek ALC294, Speaker, Internal] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GA502IV.207
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GA502IV
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGA502IV.207:bd08/03/2020:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG15GA502IV_GA502IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA502IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG Zephyrus G15
dmi.product.name: ROG Zephyrus G15 GA502IV_GA502IV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  No sound on Ubuntu 18.04 regardless of any action

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've had some trouble with sound recently after an update, it won't
  turn on. I've tried numerous things: from playing around with
  alsamixer, pulseaudio, pavucontrol to alsa force-reload and
  reinstalling alsamixer and pulseaudio. No result. It displays
  everything correctly and seems to be working, but the sound won't come
  out. On Windows it works perfectly. It did work well before, it just
  turned off unexpectedly.

  I have a dual boot Ubuntu 18.04 with Windows 10, maybe that causes the bug.
  I think so because I've had some trouble with my wi-fi adapter not found, 
which was caused by Windows fast-boot option enabled.

  I've asked questions on askubuntu and linux stackexchange, no one
  knows. Someone suggested that I need to report a bug, and that's what
  I'm doing. I'm attaching link to the question, as I posted some
  information there:

  https://unix.stackexchange.com/questions/608305/no-sound-on-
  ubuntu-18-04-after-a-system-update

  I am not sure what I can do now to enable it...
  Please help.

  $ lsb_release -rd:

  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  $ cat /proc/asound/version:

  Advanced Linux Sound Architecture Driver Version k5.4.0-45-generic.

  $ aplay --version:

  aplay: version 1.1.3 by Jaroslav Kysela 

  I hope that I have given enough info about the bug, however if
  anything 

[Desktop-packages] [Bug 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake

2020-07-23 Thread Boris-Barboris
I'm also affected by it on a recent pulseaudio version 13.0, kernel 5.7.8
Seems like a revival of 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

Displayport GPU audio device is incorrectly being re-enabled on login by
pulseaudio.

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

Title:
  pulseaudio has is buggy with hdmi audio and sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs
  with pulseaudio after putting my system to sleep and then waking it
  up. these bugs aren't present on a fresh boot, only after resuming
  from sleep:

  - it forgets which sound output device it's set to, and always reverse to the 
motherboard's S/PDIF output.
  - I have two devices connected to my video card, one is a displayport 
monitor, and one is a home theater receiver via HDMI. it confuses the two, and 
randomly switches which device it thinks is capable of surround sound.
  - it sometimes refuses to switch to the correct audio device, and just resets 
any choice back to the internal S/PDIF, until the system is rebooted.

  as you can imagine, this a pretty frustrating state of affairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.4
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa  3387 F pulseaudio
   /dev/snd/pcmC1D7p:   tessa  3387 F...m pulseaudio
   /dev/snd/controlC2:  tessa  3387 F pulseaudio
   /dev/snd/controlC0:  tessa  3387 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 18:38:42 2020
  InstallationDate: Installed on 2020-07-15 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z97
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2020-07-01 Thread Boris Rybalkin
Fresh (unlike upgrade previously) install of 20.04 fixed it.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Won't Fix
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

     On Xenial X runs on VT7 thus the graphical environment is not affected in 
the default configuration, but the keyboard-configuration postinst maintaner 

[Desktop-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2020-07-01 Thread Boris Rybalkin
Fresh install of 20.04 fixed the issue.
Probably previously I had something installed which was triggering it.

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-07-21 (213 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2020-05-30 Thread Boris Rybalkin
I have this issue. kbd_mode -s fixes it but then gnome session restarts
when I hit enter anywhere.

Ubuntu 20.04 LTS
Linux 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Won't Fix
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

     

[Desktop-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2020-05-30 Thread Boris Rybalkin
Please reopen the bug it is not working.

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-07-21 (213 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2020-05-30 Thread Boris Rybalkin
I think this is exactly my problem:
https://bugs.launchpad.net/ubuntu/+source/console-
setup/+bug/520546/comments/1

>From time to time my keyboard switches to a mode when alt + f1 starts to 
>switch me to console.
The bug comment also mentions Ctrl+C killing the GUI.

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-07-21 (213 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1877238] [NEW] package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: попытка перезаписать общий «/usr/sh

2020-05-07 Thread Boris Kaganovich
Public bug reported:

-

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: 
usr/share/glvnd/egl_vendor.d/50_mesa.json]
Uname: Linux 4.9.140-tegra aarch64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: arm64
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu May  7 09:53:41 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ErrorMessage: попытка перезаписать общий 
«/usr/share/glvnd/egl_vendor.d/50_mesa.json», который отличается от других 
экземпляров пакета libegl-mesa0:armhf
GraphicsCard:
 
ProcKernelCmdLine: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M 
memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 
touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 
debug_uartport=lsport,2 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 
usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff78 core_edp_mv=1075 
core_edp_ma=4000  root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 
console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0
root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 
console=tty0 fbcon=map:0 net.ifnames=0 quiet
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.12
SourcePackage: mesa
Title: package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: 
usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: попытка 
перезаписать общий «/usr/share/glvnd/egl_vendor.d/50_mesa.json», который 
отличается от других экземпляров пакета libegl-mesa0:armhf
UpgradeStatus: No upgrade log present (probably fresh install)
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
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 N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: apport-package arm64 bionic compiz-0.9 ubuntu

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

Title:
  package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified:
  usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade:
  попытка перезаписать общий
  «/usr/share/glvnd/egl_vendor.d/50_mesa.json», который отличается от
  других экземпляров пакета libegl-mesa0:armhf

Status in mesa package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: 
usr/share/glvnd/egl_vendor.d/50_mesa.json]
  Uname: Linux 4.9.140-tegra aarch64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: arm64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu May  7 09:53:41 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ErrorMessage: попытка перезаписать общий 
«/usr/share/glvnd/egl_vendor.d/50_mesa.json», который отличается от других 
экземпляров пакета libegl-mesa0:armhf
  GraphicsCard:
   
  ProcKernelCmdLine: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M 
memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 
touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 
debug_uartport=lsport,2 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 
usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff78 core_edp_mv=1075 
core_edp_ma=4000  root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 
console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0
root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 
console=tty0 fbcon=map:0 net.ifnames=0 quiet
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: mesa
  Title: package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: 
usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: попытка 
перезаписать общий «/usr/share/glvnd/egl_vendor.d/50_mesa.json», который 
отличается от других экземпляров пакета libegl-mesa0:armhf
  UpgradeStatus: No upgrade log present 

[Desktop-packages] [Bug 1872791] Re: PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200

2020-04-14 Thread Boris Gjenero
I did some more investigation and found that without the workaround the
analog output only appears while headphones are plugged in. The SPDIF
output disappears while headphones are plugged in.

The bug has been submitted with this new information at
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/852

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #852
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/852

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

Title:
  PulseAudio doesn't see analog output on Dell Inspiron 6400 with
  STAC9200

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio currently doesn't see the analog audio output in my Dell
  Inspiron 6400 laptop with Intel HDA STAC9200 audio. It only sees the
  SPDIF output. This is the situation in both "pactl list sinks" and
  pavucontrol. I hear no sound from applications, probably because it's
  going to SPDIF. I don't have a way to listen to SPDIF to see if that
  is indeed the case.

  ALSA sees the analog output and "speaker-test -D plughw:0" plays sound
  through the laptop's speakers.

  This problem never happened in Ubuntu 19.10 and earlier. It might have
  worked earlier in 20.04 also, but I'm not sure of that. Rebooting
  didn't help. Purging and reinstalling pulseaudio and its automatically
  installed dependencies didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bgjenero   1414 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27'
 Mixer name : 'SigmaTel STAC9200'
 Components : 'HDA:83847690,102801bd,00102201 
HDA:14f12bfa,14f100c3,0009'
 Controls  : 22
 Simple ctrls  : 9
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Apr 14 13:37:43 2020
  InstallationDate: Installed on 2012-01-19 (3008 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-05 (9 days ago)
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XD720
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872791/+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 1872791] Re: PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200

2020-04-14 Thread Boris Gjenero
It was easy to fix this by adding the following line to /etc/pulse/default.pa
load-module module-alsa-sink device=hw:0,0

After doing that and rebooting, I had to set the analog device as the
fallback device in pavucontrol. (Before the default.pa change, the SPDIF
device had been the only playback device there.)

So, sound works now. But, why did I have to do that? Why was the SPDIF
device automatically detected but not the audio device?

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

Title:
  PulseAudio doesn't see analog output on Dell Inspiron 6400 with
  STAC9200

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio currently doesn't see the analog audio output in my Dell
  Inspiron 6400 laptop with Intel HDA STAC9200 audio. It only sees the
  SPDIF output. This is the situation in both "pactl list sinks" and
  pavucontrol. I hear no sound from applications, probably because it's
  going to SPDIF. I don't have a way to listen to SPDIF to see if that
  is indeed the case.

  ALSA sees the analog output and "speaker-test -D plughw:0" plays sound
  through the laptop's speakers.

  This problem never happened in Ubuntu 19.10 and earlier. It might have
  worked earlier in 20.04 also, but I'm not sure of that. Rebooting
  didn't help. Purging and reinstalling pulseaudio and its automatically
  installed dependencies didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bgjenero   1414 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27'
 Mixer name : 'SigmaTel STAC9200'
 Components : 'HDA:83847690,102801bd,00102201 
HDA:14f12bfa,14f100c3,0009'
 Controls  : 22
 Simple ctrls  : 9
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Apr 14 13:37:43 2020
  InstallationDate: Installed on 2012-01-19 (3008 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-05 (9 days ago)
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XD720
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872791/+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 1872791] [NEW] PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200

2020-04-14 Thread Boris Gjenero
Public bug reported:

PulseAudio currently doesn't see the analog audio output in my Dell
Inspiron 6400 laptop with Intel HDA STAC9200 audio. It only sees the
SPDIF output. This is the situation in both "pactl list sinks" and
pavucontrol. I hear no sound from applications, probably because it's
going to SPDIF. I don't have a way to listen to SPDIF to see if that is
indeed the case.

ALSA sees the analog output and "speaker-test -D plughw:0" plays sound
through the laptop's speakers.

This problem never happened in Ubuntu 19.10 and earlier. It might have
worked earlier in 20.04 also, but I'm not sure of that. Rebooting didn't
help. Purging and reinstalling pulseaudio and its automatically
installed dependencies didn't help.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-21-generic.
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
ArecordDevices:
  List of CAPTURE Hardware Devices 
 card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bgjenero   1414 F pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27'
   Mixer name   : 'SigmaTel STAC9200'
   Components   : 'HDA:83847690,102801bd,00102201 
HDA:14f12bfa,14f100c3,0009'
   Controls  : 22
   Simple ctrls  : 9
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Apr 14 13:37:43 2020
InstallationDate: Installed on 2012-01-19 (3008 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to focal on 2020-04-05 (9 days ago)
dmi.bios.date: 06/13/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0XD720
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MM061
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  PulseAudio doesn't see analog output on Dell Inspiron 6400 with
  STAC9200

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio currently doesn't see the analog audio output in my Dell
  Inspiron 6400 laptop with Intel HDA STAC9200 audio. It only sees the
  SPDIF output. This is the situation in both "pactl list sinks" and
  pavucontrol. I hear no sound from applications, probably because it's
  going to SPDIF. I don't have a way to listen to SPDIF to see if that
  is indeed the case.

  ALSA sees the analog output and "speaker-test -D plughw:0" plays sound
  through the laptop's speakers.

  This problem never happened in Ubuntu 19.10 and earlier. It might have
  worked earlier in 20.04 also, but I'm not sure of that. Rebooting
  didn't help. Purging and reinstalling pulseaudio and its automatically
  installed dependencies didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bgjenero   1414 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27'
 Mixer name : 'SigmaTel STAC9200'
 Components : 'HDA:83847690,102801bd,00102201 
HDA:14f12bfa,14f100c3,0009'
 Controls  : 22
 Simple ctrls  : 9
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Apr 14 13:37:43 2020
  InstallationDate: Installed on 2012-01-19 (3008 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-05 (9 days ago)
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XD720
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1871095] [NEW] Upgrade to GCC 7.5.0 breaks ODB

2020-04-06 Thread Boris Kolpackov
Public bug reported:

An upgrade to GCC 7.5.0 on Ubuntu 18.04 appears to break ODB 2.4.0. We
so far have three reports on our mailing list (all submitted in the past
week):

https://www.codesynthesis.com/pipermail/odb-users/2020-March/004471.html
https://www.codesynthesis.com/pipermail/odb-users/2020-March/004471.html
https://www.codesynthesis.com/pipermail/odb-users/2020-April/004480.html

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

** Package changed: libreoffice (Ubuntu) => odb (Ubuntu)

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

Title:
  Upgrade to GCC 7.5.0 breaks ODB

Status in odb package in Ubuntu:
  New

Bug description:
  An upgrade to GCC 7.5.0 on Ubuntu 18.04 appears to break ODB 2.4.0. We
  so far have three reports on our mailing list (all submitted in the
  past week):

  https://www.codesynthesis.com/pipermail/odb-users/2020-March/004471.html
  https://www.codesynthesis.com/pipermail/odb-users/2020-March/004471.html
  https://www.codesynthesis.com/pipermail/odb-users/2020-April/004480.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/odb/+bug/1871095/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2020-03-24 Thread Boris Rybalkin
Issues sill happens even in XWayland session :(
No crash dumps yet.

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-07-21 (213 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2020-03-20 Thread Boris Rybalkin
XWayland does not have this issue for me.

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-07-21 (213 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2020-02-26 Thread Boris Rybalkin
I am actually typing this comment form Ubuntu on Wayland, should it
help?

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-07-21 (213 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2020-02-20 Thread Boris Rybalkin
Actually there is one crash file from gnome you are right:
https://errors.ubuntu.com/oops/071369c4-5364-11ea-a0ab-fa163e6cac46

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-07-21 (213 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1853199] ShellJournal.txt

2020-02-19 Thread Boris Rybalkin
apport information

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

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-07-21 (213 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2020-02-19 Thread Boris Rybalkin
it stopped crashing for few days I think but then started again, so ran
"apport-collect 1853199" to provide more info.

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-07-21 (213 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

2020-02-19 Thread Boris Rybalkin
apport information

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

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-07-21 (213 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2020-02-19 Thread Boris Rybalkin
apport information

** Tags added: apport-collected

** Description changed:

  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.
  
  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.2
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2019-07-21 (213 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
+ RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
+ Tags:  eoan
+ Uname: Linux 5.3.0-29-generic x86_64
+ UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as 

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

2020-02-19 Thread Boris Rybalkin
apport information

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

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-07-21 (213 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1853199] monitors.xml.txt

2020-02-19 Thread Boris Rybalkin
apport information

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

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-07-21 (213 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

2020-02-19 Thread Boris Rybalkin
apport information

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

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-07-21 (213 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2020-01-23 Thread Boris Rybalkin
1. removed the files
2. done ctrl + c
3. gnome restarted 
4. had to repeat login for 10-20 times before gnome actually opened the desktop
5. /var/crash is empty :(

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+attachment/5322427/+files/journal.txt

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2020-01-19 Thread Boris Rybalkin
Another one

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+attachment/5321569/+files/journal.txt

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2020-01-18 Thread Boris Rybalkin
attached the output

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+attachment/5321345/+files/journal.txt

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2020-01-09 Thread Boris Rybalkin
This was actually ctrl + x inside libreoffice calc 100% reproducable
(did 3 times in a row).

https://errors.ubuntu.com/oops/0a86d610-331b-11ea-b88b-fa163e102db1
https://errors.ubuntu.com/oops/615fd93e-3312-11ea-b1f4-fa163e983629
https://errors.ubuntu.com/oops/3279fd88-3188-11ea-a9c1-fa163e6cac46

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2020-01-06 Thread Boris Rybalkin
Also I think at the same time Alt + F4 stops closing apps but instead
switches to another console.

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2020-01-05 Thread Boris Rybalkin
Crashed few times today and yesterday, /var/crash is empty :(

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2019-12-21 Thread Boris Rybalkin
One more, I not sure if I have restarted after adding G_SLICE.

https://errors.ubuntu.com/oops/7d2f8154-2427-11ea-a97e-fa163e6cac46

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2019-12-17 Thread Boris Rybalkin
This one is definitely after the crash:
https://errors.ubuntu.com/oops/94669eda-2034-11ea-a701-fa163ee63de6

Strange thing that, file says Dec 16, 18:47:

tv@tv:/var/crash$ ll
total 22492
drwxrwsrwt  2 root whoopsie 4096 Dec 17 07:35 ./
drwxr-xr-x 15 root root 4096 Aug  8 08:05 ../
-rw-r-  1 gdm  whoopsie 23015251 Dec 16 18:47 
_usr_bin_gnome-shell.123.crash
-rw-r--r--  1 root whoopsie0 Dec 16 18:47 
_usr_bin_gnome-shell.123.upload
-rw---  1 whoopsie whoopsie   37 Dec 16 18:48 
_usr_bin_gnome-shell.123.uploaded

But report on my whoopsie page says:

OccurredReceivedProblem TypeProgram
2019-12-13 09:122019-12-16 18:12 UTCCrash   gnome-shell

Uploaded file content is the same.

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2019-12-16 Thread Boris Rybalkin
Two more:

https://errors.ubuntu.com/oops/50e85af4-19fe-11ea-b10e-fa163e983629
https://errors.ubuntu.com/oops/94669eda-2034-11ea-a701-fa163ee63de6

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2019-11-19 Thread Boris Rybalkin
attaching journalctl.log

** Attachment added: "journalctl.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1853199/+attachment/5306520/+files/journalctl.log

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in xorg package in Ubuntu:
  New

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It takes few login attempts to actually login back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1853199/+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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

2019-11-19 Thread Boris Rybalkin
It happened around this time (journalctl.log):

Nov 19 20:38:00 tv xdg-desktop-por[3284]: xdg-desktop-portal-gtk: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
Nov 19 20:38:00 tv gdm-password][1338]: pam_unix(gdm-password:session): session 
closed for user tv
Nov 19 20:38:00 tv systemd[3095]: xdg-desktop-portal-gtk.service: Main process 
exited, code=exited, status=1/FAILURE
Nov 19 20:38:00 tv systemd[3095]: xdg-desktop-portal-gtk.service: Failed with 
result 'exit-code'.
Nov 19 20:38:00 tv pulseaudio[3108]: X connection to :0 broken (explicit kill 
or server shutdown).
Nov 19 20:38:00 tv kernel: rfkill: input handler enabled

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in xorg package in Ubuntu:
  New

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It takes few login attempts to actually login back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1853199/+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 1853199] [NEW] Ctrl + c (copy) anywhere some times crashes gnome session

2019-11-19 Thread Boris Rybalkin
Public bug reported:

Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
It takes few login attempts to actually login back.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 19 20:55:37 2019
DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
InstallationDate: Installed on 2019-07-21 (121 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
 Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
 Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Shuttle Inc. XH270
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
dmi.bios.date: 01/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.02
dmi.board.asset.tag: Default string
dmi.board.name: FH270
dmi.board.vendor: Shuttle Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: X
dmi.product.name: XH270
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Shuttle Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug crash eoan 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/1853199

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in xorg package in Ubuntu:
  New

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It takes few login attempts to actually login back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: 

[Desktop-packages] [Bug 1774957] Re: Network icons in status menu disappearing

2018-12-07 Thread boris
Same here! There are times my Wifi icon and the VPN icon when connecting to a 
VPN service are missing.
When extending the panel you can't use the switches to enable VPN configuration 
and the VPN is indicating to off although connencted.


** Attachment added: "Connected to VPN and Wifi although the icons are missing 
from menu"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774957/+attachment/5219972/+files/Screenshot%20from%202018-12-07%2011-06-09.png

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

Title:
  Network icons in status menu disappearing

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/140

  ---

  Ever since the update to Ubuntu 18.04 I'm having issues with the
  status menu at the top right of the screen.

  Normally you'd have a wired network connection icon displayed at the top 
without opening the menu. In my case it is not displayed half of the time. In 
the menu list no icon nor label is displayed for the wired connection menu item.
  When talking about half of the time it means that I can randomly make it 
display again when removing the USB network adapter and reconnecting it e.g.
  This does not work reliably though.

  When connecting to a VPN, normally you'd get an additional icon at the
  top. This is not the case any more, nor does the switch behind an
  activated VPN turns change to an active state. The result is that you
  can activate a VPN using the switch, but you can verify that it is
  activated, nor can you de-active the VPN through the menu. This does
  change in settings though.

  Wireless settings are no longer displayed in the menu at all. So no
  way to activate it or connect to a specific network.

  I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as
  network-manager-gnome, to no avail.

  Attached you'll find a screenshot illustrating the issue. You'll see
  two icons missing to the left of the volume icon, as well as the
  wireless menu missing completely and no icon and text label for the
  wired connection menu item.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  4 10:47:05 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-07 (604 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774957/+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 1174162] Re: chrome-browser makes gnome-keyring-daemon use 100% cpu

2018-10-12 Thread Boris Gjenero
This never happened in 18.04, and started happening after upgrading to
18.10. The keyring daemon when taking 100% CPU on one core also seems to
hang and not respond to applications. I've had Chrome hang on startup,
and I've had ssh and scp hang.

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

Title:
  chrome-browser makes gnome-keyring-daemon use 100% cpu

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 13.04, when starting the chromium browser, the
  gnome-keyring-daemon runs at full CPU load and the chromium-browser
  has no access to the stored passwords.

  The issue seems to be known
  (https://code.google.com/p/chromium/issues/detail?id=98601). I'm
  personally a bit surprised that Ubuntu 13.04 was released with such a
  serious problem.

  The frequently proposed workaround (e.g.
  https://plus.google.com/110130355317073712944/posts/PckhFj5HUn4)
  doesn't work because (a) there is no .gnome2/keyrings any more and (b)
  it's rather inresponsible to store your passwords unencryted.

  I found that killing gnome-keyring-server several times eventually gives you 
a working system.
  --- 
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mnl   18759 F pulseaudio
  CRDA:
   country DE:
(2400 - 2483 @ 40), (N/A, 20)
(5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
(5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
(5470 - 5725 @ 40), (N/A, 26), DFS
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=86292e17-edd2-4a1b-8e1b-5208a1731140
  InstallationDate: Installed on 2010-11-10 (900 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MachineType: Hewlett-Packard HP Compaq 6730b (GB990EA#ABD)
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=cff10fb4-08a2-459b-be12-80698b20d2d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  Tags:  raring
  Uname: Linux 3.8.0-19-generic i686
  UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare voice 
wireshark
  WifiSyslog: Apr 29 07:28:34 lipp-nb wpa_supplicant[1803]: wlan0: WPA: Group 
rekeying completed with c0:25:06:24:93:e1 [GTK=CCMP]
  dmi.bios.date: 12/07/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDD Ver. F.20
  dmi.board.name: 30DD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.23
  dmi.chassis.asset.tag: CNU9326SJY
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDDVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPCompaq6730b(GB990EA#ABD):pvrF.20:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6730b (GB990EA#ABD)
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1174162/+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 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.1

2018-09-25 Thread Boris Malkov
Proposed package 340.107-0ubuntu0.18.04.1 from #7 fixed the problem for
me after manual download and install with dpkg.

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

Title:
  package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also
  in package nvidia-340 340.107-0ubuntu0~gpu18.04.1

Status in libglvnd package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in libglvnd source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]

  The new libgles1 conflicts with nvidia-340 which ships it's own copy
  of libGLESv1_CM.so

  [Test case]

  Enable proposed, install libgles1 and nvidia-340, they should install
  fine.

  [Regression potential]

  none, just fixes a file conflict

  --

  Looks like I had a similar problem on 18.04.1 than
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1728352, just
  with nvidia-340 from https://launchpad.net/~graphics-
  drivers/+archive/ubuntu/ppa .

  Apt output:
  ```
  $ sudo apt dist-upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
    libgles1
  The following packages will be upgraded:
    libegl1 libgl1 libgles2 libglvnd-core-dev libglvnd-dev libglvnd0 libglx0 
libopengl0
  8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 268 kB of archives.
  After this operation, 66,6 kB of additional disk space will be used.
  Do you want to continue? [Y/n]
  Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
libglvnd-dev amd64 1.0.0-2ubuntu2.2 [3 408 B]
  Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
libglvnd-core-dev amd64 1.0.0-2ubuntu2.2 [12,9 kB]
  Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles2 
amd64 1.0.0-2ubuntu2.2 [17,4 kB]
  Get:4 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgl1 
amd64 1.0.0-2ubuntu2.2 [84,8 kB]
  Get:5 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglx0 
amd64 1.0.0-2ubuntu2.2 [28,1 kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libopengl0 
amd64 1.0.0-2ubuntu2.2 [31,3 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libegl1 
amd64 1.0.0-2ubuntu2.2 [31,9 kB]
  Get:8 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd0 
amd64 1.0.0-2ubuntu2.2 [46,6 kB]
  Get:9 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles1 
amd64 1.0.0-2ubuntu2.2 [11,2 kB]
  Fetched 268 kB in 0s (1 575 kB/s)
  (Reading database ... 141610 files and directories currently installed.)
  Preparing to unpack .../0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is 
also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1
  Preparing to unpack .../1-libglvnd-core-dev_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglvnd-core-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) 
...
  Preparing to unpack .../2-libgles2_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libgles2:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../3-libgl1_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libgl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../4-libglx0_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglx0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../5-libopengl0_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libopengl0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../6-libegl1_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libegl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../7-libglvnd0_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglvnd0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Selecting previously unselected package libgles1:amd64.
  Preparing to unpack .../8-libgles1_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libgles1:amd64 (1.0.0-2ubuntu2.2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is 
also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb
   /tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb
 

[Desktop-packages] [Bug 1709084] Re: Screensaver not suppressed when watching full screen video

2018-01-07 Thread Boris Erdmann
*** This bug is a duplicate of bug 1697373 ***
https://bugs.launchpad.net/bugs/1697373

Or maybe the caffeine just doesn't work with wayland?

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

Title:
  Screensaver not suppressed when watching full screen video

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Using chromium 59 on an up to date 17.10 and watching a full screen
  video, the screensaver kicks in after 5 minutes. It should be
  suppressed. This only happens in chrome/chromium. Firefox is
  unaffected. Unfortunately my TV provider doesn't support Firefox, so I
  have to use Chrome.

  Steps to reproduce.

  In Settings -> Power -> Set Blank screen to 5 minutes
  Open chromium
  Play a long video such as https://www.youtube.com/watch?v=jX6kn9_U8qk
  Full screen (and optionally mute) the video
  Leave computer alone

  Expected result

  10 hours of video plays

  Actual result

  After 5 minutes, the screen goes blank

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: chromium-browser 59.0.3071.109-0ubuntu1.1360
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAw5AYEAAAXAQSVHxF46tyVo1hVoCYNUFQBAQEBAQEBAQEBAQEBAQEBujaArHA4JEA8JDUANa8QAAAa/gBMRyBEaXNwbGF5CiAg/gBMUDE0MFdGMS1TUEoxAHk=
   modes: 1920x1080
  Date: Mon Aug  7 14:24:55 2017
  Desktop-Session:
   'ubuntu-wayland'
   'None'
   'None'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2017-08-02 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => libgnome-shell-browser-plugin.so
   (size: 18920 bytes, mtime: Sun Jul 23 18:08:04 2017)
  Load-Avg-1min: 0.54
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 20BV001BUK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed 
root=UUID=20b4dfc6-b888-4543-b51f-3346a19a0e18 ro quiet splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BV001BUK
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1709084/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-10-05 Thread Boris Malkov
It already looks like some kind of a tradition for ubuntu to break
something critical in every single release and keep those bugs as long
as possible.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1624317/+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 1678271] Re: Background color erase (bce) is broken

2017-04-30 Thread Boris Gjenero
I tried installing some old libraries and binaries from Yakkety but even
with that I couldn't reproduce it in Ubuntu 17.04. I don't have any more
Yakkety systems to test on. I also can't reproduce it in 16.04.2 LTS in
Windows 10. I don't think any DOSBox changes could have changed this
either. So I'm a bit mystified here. Sorry about wasting your time.

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

Title:
  Background color erase (bce) is broken

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I'm running my ncursesw application, displaying a black background.
  When the screen or a region scrolls up by one line, empty areas of the
  screen in the newly visible line show the default white background of
  gnome-terminal.

  If I remove the bce capability from the Terminfo for that terminal type, the 
problem goes away. This workaround involves:
  "infocmp xterm-256color > xt.ti" to get the Terminfo data in text format.
  Editing xt.ti and removing "bce, " on the 3rd line
  "tic xt.ti" to compile this text to Terminfo again. Without sudo that ends up 
in ~/.terminfo, overriding the system's entry, and with sudo it would overwrite 
the system's Terminfo entry for that terminal type.

  Another workaround would be to use a different terminal type without
  bce, like TERM=screen, but removing bce is better because that leaves
  other capabilities intact.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-terminal 3.20.2-1ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 13:49:01 2017
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (169 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1678271/+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 1678271] Re: Background color erase (bce) is broken

2017-04-21 Thread Boris Gjenero
I'm not able to reproduce this now in Zesty with gnome-terminal
3.20.2-1ubuntu8. Program that was causing problems before is DOSBox SVN
with ncursesw output added, https://github.com/dreamlayers/em-
dosbox/tree/contxt-only but that works fine now. infocmp $TERM shows I'm
using /lib/terminfo/x/xterm-256color and bce is present there, so it
seems bce now works.

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

Title:
  Background color erase (bce) is broken

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I'm running my ncursesw application, displaying a black background.
  When the screen or a region scrolls up by one line, empty areas of the
  screen in the newly visible line show the default white background of
  gnome-terminal.

  If I remove the bce capability from the Terminfo for that terminal type, the 
problem goes away. This workaround involves:
  "infocmp xterm-256color > xt.ti" to get the Terminfo data in text format.
  Editing xt.ti and removing "bce, " on the 3rd line
  "tic xt.ti" to compile this text to Terminfo again. Without sudo that ends up 
in ~/.terminfo, overriding the system's entry, and with sudo it would overwrite 
the system's Terminfo entry for that terminal type.

  Another workaround would be to use a different terminal type without
  bce, like TERM=screen, but removing bce is better because that leaves
  other capabilities intact.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-terminal 3.20.2-1ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 13:49:01 2017
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (169 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1678271/+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 1680642] [NEW] xdg-icon-resource does not set permissions when installing icon

2017-04-06 Thread Boris Gjenero
Public bug reported:

When installing an icon using a command such as "sudo xdg-icon-resource
install --novendor --context apps --size 256 synaesthesia.png
synaesthesia", the ownership of the file created at
/usr/local/share/icons/hicolor/256x256/apps/synaesthesia.png is set to
root:root, but the permissions aren't changed.

I ran into this problem when installing a .desktop file and icon and
finding that the icon failed to show up. The problem was that the .png
file was not world readable, and so after the ownership was changed it
was not readable to me anymore.

xdg-icon-resource does at least remove the setuid and setgid bits, so
although I can make a copy of bash with the .png extension, install
that, and run it, I can't use this to make a setuid root bash.

"sudo xdg-desktop-menu install" seems to do the same thing with the
files it puts in /usr/share/applications

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xdg-utils 1.1.1-1ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Apr  6 20:40:29 2017
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to yakkety on 2016-10-13 (175 days ago)

** Affects: xdg-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

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

Title:
  xdg-icon-resource does not set permissions when installing icon

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  When installing an icon using a command such as "sudo xdg-icon-
  resource install --novendor --context apps --size 256 synaesthesia.png
  synaesthesia", the ownership of the file created at
  /usr/local/share/icons/hicolor/256x256/apps/synaesthesia.png is set to
  root:root, but the permissions aren't changed.

  I ran into this problem when installing a .desktop file and icon and
  finding that the icon failed to show up. The problem was that the .png
  file was not world readable, and so after the ownership was changed it
  was not readable to me anymore.

  xdg-icon-resource does at least remove the setuid and setgid bits, so
  although I can make a copy of bash with the .png extension, install
  that, and run it, I can't use this to make a setuid root bash.

  "sudo xdg-desktop-menu install" seems to do the same thing with the
  files it puts in /usr/share/applications

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xdg-utils 1.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr  6 20:40:29 2017
  PackageArchitecture: all
  SourcePackage: xdg-utils
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (175 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1680642/+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 1679487] Re: PDF+LaTeX incorrectly replaces \\ (two backslashes) by a newline

2017-04-04 Thread Boris Dalstein
pdf_tex export from a previous Inkscape version (retrieve from my
archives)

** Attachment added: "mobius-vs-cylinder.pdf_tex"
   
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1679487/+attachment/4854003/+files/mobius-vs-cylinder.pdf_tex

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

Title:
  PDF+LaTeX incorrectly replaces \\ (two backslashes) by a newline

Status in inkscape package in Ubuntu:
  New

Bug description:
  I have an SVG file which contains text like such, the important part
  being the double backslash:

  $\sboundary f = 
  \left[\begin{array}{c} 
  \gamma_1 = [ (e^\circ, \top) ] \\
  \gamma_2 = [ (e^\circ, \top) ]
  \end{array}\right]$

  Using Inkscape 0.91 r13725, on Kubuntu 16.04 64bits, PDF+LaTeX
  converts the text to the following, that is, replaces the double
  backslashes by a newline!

  
  
\put(0.50170692,0.32122315){\color[rgb]{0,0,0}\makebox(0,0)[b]{\smash{$\sboundary
 f = 
\left[\begin{array}{c} 
\gamma_1 = [ (e^\circ, \top) ] 
   
\gamma_2 = [ (e^\circ, \top) ]
\end{array}\right]$}}}%

  Which makes LaTeX crash with the error:

  Runaway argument?
  {$\sboundary f = \left [\begin {array}{c} \gamma _1 = [ (e^\circ , \top \ETC.
  ! Paragraph ended before \makesm@sh was complete.
   
 \par 
  l.64   \end{array}\right]$}}}
   %

  I do need the backslashes so that the array environment knows where
  the next row starts. It seems Inkscape is trying to be too smart. In a
  previous version of Inkscape (sorry, I don't know which), this text
  used to be correctly exported as the following:

  
\put(0.50170692,0.32122315){\color[rgb]{0,0,0}\makebox(0,0)[b]{\smash{$\sboundary
 f = 
  \left[\begin{array}{c} 
  \gamma_1 = [ (e^\circ, \top) ] \\
  \gamma_2 = [ (e^\circ, \top) ]
  \end{array}\right]$}}}%

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1679487/+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 1679487] Re: PDF+LaTeX incorrectly replaces \\ (two backslashes) by a newline

2017-04-04 Thread Boris Dalstein
PDF export

** Attachment added: "mobius-vs-cylinder.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1679487/+attachment/4854001/+files/mobius-vs-cylinder.pdf

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

Title:
  PDF+LaTeX incorrectly replaces \\ (two backslashes) by a newline

Status in inkscape package in Ubuntu:
  New

Bug description:
  I have an SVG file which contains text like such, the important part
  being the double backslash:

  $\sboundary f = 
  \left[\begin{array}{c} 
  \gamma_1 = [ (e^\circ, \top) ] \\
  \gamma_2 = [ (e^\circ, \top) ]
  \end{array}\right]$

  Using Inkscape 0.91 r13725, on Kubuntu 16.04 64bits, PDF+LaTeX
  converts the text to the following, that is, replaces the double
  backslashes by a newline!

  
  
\put(0.50170692,0.32122315){\color[rgb]{0,0,0}\makebox(0,0)[b]{\smash{$\sboundary
 f = 
\left[\begin{array}{c} 
\gamma_1 = [ (e^\circ, \top) ] 
   
\gamma_2 = [ (e^\circ, \top) ]
\end{array}\right]$}}}%

  Which makes LaTeX crash with the error:

  Runaway argument?
  {$\sboundary f = \left [\begin {array}{c} \gamma _1 = [ (e^\circ , \top \ETC.
  ! Paragraph ended before \makesm@sh was complete.
   
 \par 
  l.64   \end{array}\right]$}}}
   %

  I do need the backslashes so that the array environment knows where
  the next row starts. It seems Inkscape is trying to be too smart. In a
  previous version of Inkscape (sorry, I don't know which), this text
  used to be correctly exported as the following:

  
\put(0.50170692,0.32122315){\color[rgb]{0,0,0}\makebox(0,0)[b]{\smash{$\sboundary
 f = 
  \left[\begin{array}{c} 
  \gamma_1 = [ (e^\circ, \top) ] \\
  \gamma_2 = [ (e^\circ, \top) ]
  \end{array}\right]$}}}%

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1679487/+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 1679487] Re: PDF+LaTeX incorrectly replaces \\ (two backslashes) by a newline

2017-04-04 Thread Boris Dalstein
Note: this SVG file also exhibits the following export error:

https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1417470

I fixed it by using the following definition of \includesvg, inspired by
one comment in the above bug:

\newcommand{\includesvg}[2][]{%
\executeiffilenewer{images/#2.svg}{images/#2.pdf}%
{\unexpanded{PDF_FILE="./images/#2.pdf"; inkscape -z --file=./images/#2.svg 
--export-pdf=$PDF_FILE --export-latex; sed -i 's//\n/g' ${PDF_FILE}_tex; 
MAXPAGE=$(pdfinfo $PDF_FILE | grep -oP "(?<=Pages:)\s*[0-9]+" | tr -d " ") ; 
sed -i "/page=$(($MAXPAGE+1))/,\${/page=/d}" ${PDF_FILE}_tex; } }
\ifthenelse{\isempty{#1}}{\small}{#1}
\input{images/#2.pdf_tex}%
}

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

Title:
  PDF+LaTeX incorrectly replaces \\ (two backslashes) by a newline

Status in inkscape package in Ubuntu:
  New

Bug description:
  I have an SVG file which contains text like such, the important part
  being the double backslash:

  $\sboundary f = 
  \left[\begin{array}{c} 
  \gamma_1 = [ (e^\circ, \top) ] \\
  \gamma_2 = [ (e^\circ, \top) ]
  \end{array}\right]$

  Using Inkscape 0.91 r13725, on Kubuntu 16.04 64bits, PDF+LaTeX
  converts the text to the following, that is, replaces the double
  backslashes by a newline!

  
  
\put(0.50170692,0.32122315){\color[rgb]{0,0,0}\makebox(0,0)[b]{\smash{$\sboundary
 f = 
\left[\begin{array}{c} 
\gamma_1 = [ (e^\circ, \top) ] 
   
\gamma_2 = [ (e^\circ, \top) ]
\end{array}\right]$}}}%

  Which makes LaTeX crash with the error:

  Runaway argument?
  {$\sboundary f = \left [\begin {array}{c} \gamma _1 = [ (e^\circ , \top \ETC.
  ! Paragraph ended before \makesm@sh was complete.
   
 \par 
  l.64   \end{array}\right]$}}}
   %

  I do need the backslashes so that the array environment knows where
  the next row starts. It seems Inkscape is trying to be too smart. In a
  previous version of Inkscape (sorry, I don't know which), this text
  used to be correctly exported as the following:

  
\put(0.50170692,0.32122315){\color[rgb]{0,0,0}\makebox(0,0)[b]{\smash{$\sboundary
 f = 
  \left[\begin{array}{c} 
  \gamma_1 = [ (e^\circ, \top) ] \\
  \gamma_2 = [ (e^\circ, \top) ]
  \end{array}\right]$}}}%

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1679487/+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 1679487] Re: PDF+LaTeX incorrectly replaces \\ (two backslashes) by a newline

2017-04-04 Thread Boris Dalstein
pdf_tex export

** Attachment added: "mobius-vs-cylinder.pdf_tex"
   
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1679487/+attachment/4854002/+files/mobius-vs-cylinder.pdf_tex

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

Title:
  PDF+LaTeX incorrectly replaces \\ (two backslashes) by a newline

Status in inkscape package in Ubuntu:
  New

Bug description:
  I have an SVG file which contains text like such, the important part
  being the double backslash:

  $\sboundary f = 
  \left[\begin{array}{c} 
  \gamma_1 = [ (e^\circ, \top) ] \\
  \gamma_2 = [ (e^\circ, \top) ]
  \end{array}\right]$

  Using Inkscape 0.91 r13725, on Kubuntu 16.04 64bits, PDF+LaTeX
  converts the text to the following, that is, replaces the double
  backslashes by a newline!

  
  
\put(0.50170692,0.32122315){\color[rgb]{0,0,0}\makebox(0,0)[b]{\smash{$\sboundary
 f = 
\left[\begin{array}{c} 
\gamma_1 = [ (e^\circ, \top) ] 
   
\gamma_2 = [ (e^\circ, \top) ]
\end{array}\right]$}}}%

  Which makes LaTeX crash with the error:

  Runaway argument?
  {$\sboundary f = \left [\begin {array}{c} \gamma _1 = [ (e^\circ , \top \ETC.
  ! Paragraph ended before \makesm@sh was complete.
   
 \par 
  l.64   \end{array}\right]$}}}
   %

  I do need the backslashes so that the array environment knows where
  the next row starts. It seems Inkscape is trying to be too smart. In a
  previous version of Inkscape (sorry, I don't know which), this text
  used to be correctly exported as the following:

  
\put(0.50170692,0.32122315){\color[rgb]{0,0,0}\makebox(0,0)[b]{\smash{$\sboundary
 f = 
  \left[\begin{array}{c} 
  \gamma_1 = [ (e^\circ, \top) ] \\
  \gamma_2 = [ (e^\circ, \top) ]
  \end{array}\right]$}}}%

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1679487/+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 1679487] [NEW] PDF+LaTeX incorrectly replaces \\ (two backslashes) by a newline

2017-04-04 Thread Boris Dalstein
Public bug reported:

I have an SVG file which contains text like such, the important part
being the double backslash:

$\sboundary f = 
\left[\begin{array}{c} 
\gamma_1 = [ (e^\circ, \top) ] \\
\gamma_2 = [ (e^\circ, \top) ]
\end{array}\right]$

Using Inkscape 0.91 r13725, on Kubuntu 16.04 64bits, PDF+LaTeX converts
the text to the following, that is, replaces the double backslashes by a
newline!



\put(0.50170692,0.32122315){\color[rgb]{0,0,0}\makebox(0,0)[b]{\smash{$\sboundary
 f = 
  \left[\begin{array}{c} 
  \gamma_1 = [ (e^\circ, \top) ] 
 
  \gamma_2 = [ (e^\circ, \top) ]
  \end{array}\right]$}}}%

Which makes LaTeX crash with the error:

Runaway argument?
{$\sboundary f = \left [\begin {array}{c} \gamma _1 = [ (e^\circ , \top \ETC.
! Paragraph ended before \makesm@sh was complete.
 
   \par 
l.64   \end{array}\right]$}}}
 %

I do need the backslashes so that the array environment knows where the
next row starts. It seems Inkscape is trying to be too smart. In a
previous version of Inkscape (sorry, I don't know which), this text used
to be correctly exported as the following:


\put(0.50170692,0.32122315){\color[rgb]{0,0,0}\makebox(0,0)[b]{\smash{$\sboundary
 f = 
\left[\begin{array}{c} 
\gamma_1 = [ (e^\circ, \top) ] \\
\gamma_2 = [ (e^\circ, \top) ]
\end{array}\right]$}}}%

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

** Attachment added: "mobius-vs-cylinder.svg"
   
https://bugs.launchpad.net/bugs/1679487/+attachment/4854000/+files/mobius-vs-cylinder.svg

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

Title:
  PDF+LaTeX incorrectly replaces \\ (two backslashes) by a newline

Status in inkscape package in Ubuntu:
  New

Bug description:
  I have an SVG file which contains text like such, the important part
  being the double backslash:

  $\sboundary f = 
  \left[\begin{array}{c} 
  \gamma_1 = [ (e^\circ, \top) ] \\
  \gamma_2 = [ (e^\circ, \top) ]
  \end{array}\right]$

  Using Inkscape 0.91 r13725, on Kubuntu 16.04 64bits, PDF+LaTeX
  converts the text to the following, that is, replaces the double
  backslashes by a newline!

  
  
\put(0.50170692,0.32122315){\color[rgb]{0,0,0}\makebox(0,0)[b]{\smash{$\sboundary
 f = 
\left[\begin{array}{c} 
\gamma_1 = [ (e^\circ, \top) ] 
   
\gamma_2 = [ (e^\circ, \top) ]
\end{array}\right]$}}}%

  Which makes LaTeX crash with the error:

  Runaway argument?
  {$\sboundary f = \left [\begin {array}{c} \gamma _1 = [ (e^\circ , \top \ETC.
  ! Paragraph ended before \makesm@sh was complete.
   
 \par 
  l.64   \end{array}\right]$}}}
   %

  I do need the backslashes so that the array environment knows where
  the next row starts. It seems Inkscape is trying to be too smart. In a
  previous version of Inkscape (sorry, I don't know which), this text
  used to be correctly exported as the following:

  
\put(0.50170692,0.32122315){\color[rgb]{0,0,0}\makebox(0,0)[b]{\smash{$\sboundary
 f = 
  \left[\begin{array}{c} 
  \gamma_1 = [ (e^\circ, \top) ] \\
  \gamma_2 = [ (e^\circ, \top) ]
  \end{array}\right]$}}}%

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1679487/+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 1417470] Re: PDF+Latex export creates multipage pdf, pages missing

2017-04-03 Thread Boris Dalstein
Just adding my voice here. This bug makes PDF+LaTeX pretty unusable as
of now. Rolling back to previous behaviour seems advisable, at least
until an actual fix is made.

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

Title:
  PDF+Latex export creates multipage pdf, pages missing

Status in Inkscape:
  Confirmed
Status in inkscape package in Ubuntu:
  Confirmed
Status in inkscape package in Debian:
  Confirmed

Bug description:
  In 0.91 the z-order information in svg is used to create multipage
  PDF+LaTeX documents as per bug 771957. However, for the SVGs I have
  been converting to PDF+LaTeX in this way, the TeX-file instructs to
  load more pages than the PDF has, for example the PDF has only three
  pages and the TeX file also includes page=4. This basically breaks the
  PDF+LaTeX export for me and I have to use EPS+LaTeX + epstopdf
  package.

  The bug occurs on OpenSuse 13.1 and Windows 8.1.

  Attached a zip file with two svg files and their broken PDF+LaTeX
  counterparts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1417470/+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 1678271] [NEW] Background color erase (bce) is broken

2017-03-31 Thread Boris Gjenero
Public bug reported:

I'm running my ncursesw application, displaying a black background. When
the screen or a region scrolls up by one line, empty areas of the screen
in the newly visible line show the default white background of gnome-
terminal.

If I remove the bce capability from the Terminfo for that terminal type, the 
problem goes away. This workaround involves:
"infocmp xterm-256color > xt.ti" to get the Terminfo data in text format.
Editing xt.ti and removing "bce, " on the 3rd line
"tic xt.ti" to compile this text to Terminfo again. Without sudo that ends up 
in ~/.terminfo, overriding the system's entry, and with sudo it would overwrite 
the system's Terminfo entry for that terminal type.

Another workaround would be to use a different terminal type without
bce, like TERM=screen, but removing bce is better because that leaves
other capabilities intact.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gnome-terminal 3.20.2-1ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
Uname: Linux 4.8.0-45-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar 31 13:49:01 2017
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to yakkety on 2016-10-13 (169 days ago)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Background color erase (bce) is broken

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I'm running my ncursesw application, displaying a black background.
  When the screen or a region scrolls up by one line, empty areas of the
  screen in the newly visible line show the default white background of
  gnome-terminal.

  If I remove the bce capability from the Terminfo for that terminal type, the 
problem goes away. This workaround involves:
  "infocmp xterm-256color > xt.ti" to get the Terminfo data in text format.
  Editing xt.ti and removing "bce, " on the 3rd line
  "tic xt.ti" to compile this text to Terminfo again. Without sudo that ends up 
in ~/.terminfo, overriding the system's entry, and with sudo it would overwrite 
the system's Terminfo entry for that terminal type.

  Another workaround would be to use a different terminal type without
  bce, like TERM=screen, but removing bce is better because that leaves
  other capabilities intact.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-terminal 3.20.2-1ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 13:49:01 2017
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (169 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1678271/+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 1671920] [NEW] Mode changes fail unless some xorg.conf screen options are set

2017-03-10 Thread Boris Gjenero
Public bug reported:

The first mode change always works, but subsequent mode changes keep
failing. Running xrandr --output DVI-I-2 --mode 1600x1200 to go back to
the native resolution or any other supported resolution fails with:

xrandr: Configure crtc 0 failed
X Error of failed request:  BadValue (integer parameter out of range for 
operation)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  21 (RRSetCrtcConfig)
  Value in failed request:  0x0
  Serial number of failed request:  38
  Current serial number in output stream:  38

Mode changes from SDL 1.2 and 2.0 also fail, and a SDL 1.2 program is
killed by the error when returning from full screen.

These are changes for modes on my first monitor, which I use all the
time. I think the bug is happening because the second monitor provides
invalid EDID while turned off via the switch on the back. Everything
works if the switch on the back of the second monitor is turned on or if
an /etc/X11/xorg.conf file with sufficient options in the screen section
is in place. Ubuntu upgrades rename the xorg.conf file and deactivate
it, and I was running into the bug because of that. I'm not yet sure
which option lines in the screen section are required. I'm attaching my
normal xorg.conf file, which makes things work. I'm calling this a bug
because the second monitor shouldn't break mode changes on the first
monitor.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nvidia-340 340.101-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar 10 15:12:33 2017
SourcePackage: nvidia-graphics-drivers-340
UpgradeStatus: Upgraded to yakkety on 2016-10-13 (148 days ago)
modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted]

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


** Tags: amd64 apport-bug yakkety

** Attachment added: "This xorg.conf file makes the problem go away"
   https://bugs.launchpad.net/bugs/1671920/+attachment/4835491/+files/xorg.conf

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

Title:
  Mode changes fail unless some xorg.conf screen options are set

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

Bug description:
  The first mode change always works, but subsequent mode changes keep
  failing. Running xrandr --output DVI-I-2 --mode 1600x1200 to go back
  to the native resolution or any other supported resolution fails with:

  xrandr: Configure crtc 0 failed
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  140 (RANDR)
Minor opcode of failed request:  21 (RRSetCrtcConfig)
Value in failed request:  0x0
Serial number of failed request:  38
Current serial number in output stream:  38

  Mode changes from SDL 1.2 and 2.0 also fail, and a SDL 1.2 program is
  killed by the error when returning from full screen.

  These are changes for modes on my first monitor, which I use all the
  time. I think the bug is happening because the second monitor provides
  invalid EDID while turned off via the switch on the back. Everything
  works if the switch on the back of the second monitor is turned on or
  if an /etc/X11/xorg.conf file with sufficient options in the screen
  section is in place. Ubuntu upgrades rename the xorg.conf file and
  deactivate it, and I was running into the bug because of that. I'm not
  yet sure which option lines in the screen section are required. I'm
  attaching my normal xorg.conf file, which makes things work. I'm
  calling this a bug because the second monitor shouldn't break mode
  changes on the first monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nvidia-340 340.101-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 10 15:12:33 2017
  SourcePackage: nvidia-graphics-drivers-340
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (148 days ago)
  modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1671920/+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 971219] Re: Remmina Crashes with when connecting to some RDP hosts

2017-01-30 Thread Boris Malkov
The problem still persists.

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

Title:
  Remmina Crashes with when connecting to some RDP hosts

Status in freerdp package in Ubuntu:
  Confirmed

Bug description:
  When connecting to some RDP Hosts Remmina will crash every time they
  are 2008 server hosts but not all 2008 server hosts have the problem.

  [ 2375.493642] remmina[7647]: segfault at 10018 ip 7f0db307718c sp 
7f0da4c836f0 error 6 in libfreerdp-core.so.1.0.1[7f0db306+42000]
  [ 2509.507670] remmina[7727]: segfault at 10018 ip 7fe454b6b18c sp 
7fe4467b36f0 error 6 in libfreerdp-core.so.1.0.1[7fe454b54000+42000]

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: remmina 1.0.0-1ubuntu5
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  Date: Mon Apr  2 11:24:51 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/971219/+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 1508092] Re: [Asus 1011PX, Realtek ALC269VB, Speaker, Internal] no sound from speakers, only headphones

2016-09-29 Thread Boris
*** This bug is a duplicate of bug 1553531 ***
https://bugs.launchpad.net/bugs/1553531

** This bug has been marked a duplicate of bug 1553531
   [Beta1] No speaker output on Asus Eee PC 1011PX

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

Title:
  [Asus 1011PX, Realtek ALC269VB, Speaker, Internal] no sound from
  speakers, only headphones

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound comes out of the headphones when I insert the jack, but does NOT
  come out of the speakers when I unplug it. This includes sound from
  any source, including aplay.

  This is a newly installed Lubuntu daily build (Lubuntu 15.10 "Wily
  Werewolf" - Alpha i386 20151017.1). If I go back to running from the
  Live USB install media, the sound works fine from the speakers OR the
  headphones, as expected.

  As suggested by 
https://help.ubuntu.com/community/SoundTroubleshootingProcedure I have tried:
  * killing and reloading pulseaudio and alsa-mixer 
  * purging (.config/) .pulse/ then killing/reloading and rebooting
  * installing and reinstalling pavucontrol linux-sound-base alsa-base 
alsa-utils libasound2

  In the installed version I notice that in Volume Control (pavucontrol)
  the output switches automatically between headphones and speaker when
  the jack is plugged and unplugged - as one would expect - and in
  alsamixer I can see the inactive device being muted automatically.
  However the speaker never issues any sound :(  On the contrary in the
  live usb I notice that alsamixer leaves both outputs active (unmuted)
  and simply relies on the microswitch in the headphone jack to control
  whether the speaker can be heard or not.

  For reference I past the output of the FAILING test case's alsa-
  info.sh below and attach the output of the WORKING test case's alsa-
  info.sh

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   elda   1480 F...m pulseaudio
   /dev/snd/pcmC0D0p:   elda   1480 F...m pulseaudio
   /dev/snd/controlC0:  elda   1480 F pulseaudio
  CurrentDesktop: LXDE
  Date: Tue Oct 20 16:36:58 2015
  InstallationDate: Installed on 2015-10-19 (0 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha i386 (20151017.1)
  JournalErrors:
   No journal files were found.
   -- No entries --
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1015PE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd05/06/2011:svnASUSTeKComputerINC.:pn1011PX:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1011PX
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1508092/+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 1592514] Re: 3G usb Card - mmcli and network manager broken compatibility

2016-09-07 Thread Gnassounou boris
I m affected as well ... Please help fix it. Thanks for your script
tho... but I hope it's a temporary fix.

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

Title:
  3G usb Card - mmcli and network manager broken compatibility

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This bug is specific to "ipv4 only" 3g providers

  Here is syslog

  Jun 14 19:26:12 Latitude-E5440 NetworkManager[758]:   [1465928772.9535] 
device (cdc-wdm1): Activation: starting connection 'XXXx X / XXX XXX XXX' 
(1554021e-ff2e-44f9-8e2d-c16cae73bfe0)
  Jun 14 19:26:12 Latitude-E5440 NetworkManager[758]:   [1465928772.9538] 
audit: op="connection-activate" uuid="1554021e-ff2e-44f9-8e2d-c16cae73bfe0" 
name="XXXx X / XXX XXX XXX" pid=1663 uid=1000 result="success"
  Jun 14 19:26:12 Latitude-E5440 NetworkManager[758]:   [1465928772.9542] 
device (cdc-wdm1): state change: disconnected -> prepare (reason 'none') [30 40 
0]
  Jun 14 19:26:12 Latitude-E5440 ModemManager[675]:   Simple connect 
started...
  Jun 14 19:26:12 Latitude-E5440 ModemManager[675]:   Simple connect 
state (4/8): Wait to get fully enabled
  Jun 14 19:26:12 Latitude-E5440 ModemManager[675]:   Simple connect 
state (5/8): Register
  Jun 14 19:26:12 Latitude-E5440 ModemManager[675]:   Simple connect 
state (6/8): Bearer
  Jun 14 19:26:12 Latitude-E5440 ModemManager[675]:   Simple connect 
state (7/8): Connect
  Jun 14 19:26:12 Latitude-E5440 ModemManager[675]:   Modem 
/org/freedesktop/ModemManager1/Modem/2: state changed (registered -> connecting)
  Jun 14 19:26:15 Latitude-E5440 ModemManager[675]:   error: couldn't get 
current settings: Cannot send message: QMI service 'wds' version '1.2' 
required, got version '1.1'
  Jun 14 19:26:15 Latitude-E5440 ModemManager[675]:   Modem 
/org/freedesktop/ModemManager1/Modem/2: state changed (connecting -> connected)
  Jun 14 19:26:15 Latitude-E5440 ModemManager[675]:   Simple connect 
state (8/8): All done
  Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]:   [1465928775.2418] 
(cdc-wdm1): failed to connect modem: invalid bearer IP configuration
  Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]:   [1465928775.2419] 
device (cdc-wdm1): state change: prepare -> failed (reason 'config-failed') [40 
120 4]
  Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]:   [1465928775.2421] 
policy: disabling autoconnect for connection 'Tunisie Télécom / TUNTEL WEB 
DATA'.
  Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]:   [1465928775.2423] 
device (cdc-wdm1): Activation: failed for connection 'Tunisie Télécom / TUNTEL 
WEB DATA'
  Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]:   [1465928775.2428] 
device (cdc-wdm1): state change: failed -> disconnected (reason 'none') [120 30 
0]
  Jun 14 19:26:15 Latitude-E5440 ModemManager[675]:   Modem 
/org/freedesktop/ModemManager1/Modem/2: state changed (connected -> 
disconnecting)
  Jun 14 19:26:15 Latitude-E5440 ModemManager[675]:   Modem 
/org/freedesktop/ModemManager1/Modem/2: state changed (disconnecting -> 
registered)

  i managed to make it work using this shell script

  #!/bin/bash
  mmcli -m 0 -b $1 --connect
  ifconfig wwp0s29u1u8u3i3 up
  mmcli -m 0 -b $1
  dhclient -d wwp0s29u1u8u3i3 &
  echo "nameserver 8.8.8.8" >> /etc/resolv.conf

  i also disabled ipv6 with gui

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592514/+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 1588395] [NEW] 70gconfd_path-on-session doesn't quote DESKTOP_SESSION and fails if it contains a space

2016-06-02 Thread Boris Gjenero
Public bug reported:

In /etc/X11/Xsession.d/70gconfd_path-on-session these lines fail if
there is a space in ${DESKTOP_SESSION}:

  export MANDATORY_PATH=${GCONF_PREFIX}/${DESKTOP_SESSION}.mandatory.path
  export DEFAULTS_PATH=${GCONF_PREFIX}/${DESKTOP_SESSION}.default.path

The error output to ~/.xsession-errors is:

/etc/X11/Xsession: 6: export: Session.mandatory.path: bad variable name

I'm not sure why the error is pointing to the wrong file. Adding quotes around 
the variables in those lines makes the error go away. This error totally 
prevents logging into X. It happens when using LXDM to start Xfce, because LXDM 
sets DESKTOP_SESSION to Name from /usr/share/xsessions/xfce.desktop :
Name=Xfce Session

These LXDM bugs relate to the problem, but I guess the lack of quoting
here is the root cause. I'm not sure if setting DESKTOP_SESSION to the
Name from the .desktop file and having a space in it is wise, but
everything seems to work after fixing the quoting. Proper quoting is
used elsewhere.

https://sourceforge.net/p/lxde/bugs/420/

https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/875991

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gconf2-common 3.2.6-3ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jun  2 10:16:46 2016
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: gconf
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  70gconfd_path-on-session doesn't quote DESKTOP_SESSION and fails if it
  contains a space

Status in gconf package in Ubuntu:
  New

Bug description:
  In /etc/X11/Xsession.d/70gconfd_path-on-session these lines fail if
  there is a space in ${DESKTOP_SESSION}:

export MANDATORY_PATH=${GCONF_PREFIX}/${DESKTOP_SESSION}.mandatory.path
export DEFAULTS_PATH=${GCONF_PREFIX}/${DESKTOP_SESSION}.default.path

  The error output to ~/.xsession-errors is:

  /etc/X11/Xsession: 6: export: Session.mandatory.path: bad variable
  name

  I'm not sure why the error is pointing to the wrong file. Adding quotes 
around the variables in those lines makes the error go away. This error totally 
prevents logging into X. It happens when using LXDM to start Xfce, because LXDM 
sets DESKTOP_SESSION to Name from /usr/share/xsessions/xfce.desktop :
  Name=Xfce Session

  These LXDM bugs relate to the problem, but I guess the lack of quoting
  here is the root cause. I'm not sure if setting DESKTOP_SESSION to the
  Name from the .desktop file and having a space in it is wise, but
  everything seems to work after fixing the quoting. Proper quoting is
  used elsewhere.

  https://sourceforge.net/p/lxde/bugs/420/

  https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/875991

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gconf2-common 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jun  2 10:16:46 2016
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gconf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1588395/+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 985116] Re: A2DP headset does not appear in sound settings output list.

2016-05-17 Thread Boris Hollas
"systemctl restart bluetooth" helps.

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

Title:
  A2DP headset does not appear in sound settings output list.

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  This is a regression from Oneiric:

  Steps:
  - Pair Nokia BH-503 stereo BT headset to the laptop.
  - Verify headset is connected:  Headset LED slow-blinks blue, device appears 
as connected under BT settings.
  - Open sound settings.
  - Sources listed:  Digital SPDIF out, Analog out(selected).

  The connected headset's A2DP and headset profiles no longer appear as
  outputs/sinks; they both used to, in oneiric and natty before that.  I
  used the A2DP output fairly often without issues.

  FWIW, the same headset also works as a A2DP sink on a different
  Thinkpad that still runs Lucid.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio-module-bluetooth 1:1.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d  1854 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xee24 irq 47'
 Mixer name : 'Analog Devices AD1981'
 Components : 'HDA:11d41981,17aa2025,00100200'
 Controls  : 20
 Simple ctrls  : 11
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
7BHT40WW-1.13'
 Mixer name : 'ThinkPad EC 7BHT40WW-1.13'
 Components : ''
 Controls  : 2
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
 Playback channels: Mono
 Limits: Playback 0 - 14
 Mono: Playback 7 [50%] [on]
  Date: Wed Apr 18 10:56:10 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110201.2)
  ProcEnviron:
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to precise on 2012-02-04 (74 days ago)
  dmi.bios.date: 10/04/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7BETD3WW (2.14 )
  dmi.board.name: 1709CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7BETD3WW(2.14):bd10/04/2007:svnLENOVO:pn1709CTO:pvrThinkPadX60:rvnLENOVO:rn1709CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 1709CTO
  dmi.product.version: ThinkPad X60
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/985116/+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 985116] Re: A2DP headset does not appear in sound settings output list.

2016-05-09 Thread Boris Hollas
Same problem with 16.04 LTS. My Philips A2DP Headset sometimes isn't
listed as audio output device when it is successfully connected.
Sometimes it helps to switch bluetooth off an on again, sometimes I have
to remove the device and set it up again. It doesn't work reliably.

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

Title:
  A2DP headset does not appear in sound settings output list.

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  This is a regression from Oneiric:

  Steps:
  - Pair Nokia BH-503 stereo BT headset to the laptop.
  - Verify headset is connected:  Headset LED slow-blinks blue, device appears 
as connected under BT settings.
  - Open sound settings.
  - Sources listed:  Digital SPDIF out, Analog out(selected).

  The connected headset's A2DP and headset profiles no longer appear as
  outputs/sinks; they both used to, in oneiric and natty before that.  I
  used the A2DP output fairly often without issues.

  FWIW, the same headset also works as a A2DP sink on a different
  Thinkpad that still runs Lucid.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio-module-bluetooth 1:1.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d  1854 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xee24 irq 47'
 Mixer name : 'Analog Devices AD1981'
 Components : 'HDA:11d41981,17aa2025,00100200'
 Controls  : 20
 Simple ctrls  : 11
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
7BHT40WW-1.13'
 Mixer name : 'ThinkPad EC 7BHT40WW-1.13'
 Components : ''
 Controls  : 2
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
 Playback channels: Mono
 Limits: Playback 0 - 14
 Mono: Playback 7 [50%] [on]
  Date: Wed Apr 18 10:56:10 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110201.2)
  ProcEnviron:
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to precise on 2012-02-04 (74 days ago)
  dmi.bios.date: 10/04/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7BETD3WW (2.14 )
  dmi.board.name: 1709CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7BETD3WW(2.14):bd10/04/2007:svnLENOVO:pn1709CTO:pvrThinkPadX60:rvnLENOVO:rn1709CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 1709CTO
  dmi.product.version: ThinkPad X60
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/985116/+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 1522922] Re: Screen flickering in Intel i915 driver

2016-05-07 Thread Boris Erdmann
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613

Update: Now this bug is fixed for me in http://kernel.ubuntu.com
/~kernel-ppa/mainline/v4.4.9-xenial/ as well.

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

Title:
  Screen flickering in Intel i915 driver

Status in Nouveau Xorg driver:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Triaged

Bug description:
  There's an upstream bug reported here
  https://bugs.freedesktop.org/show_bug.cgi?id=91393 that causes screen
  flickering when using the Intel i915 builtin driver (at resolutions
  lower than the maximal one).

  I think that it will be fixed in newer kernel versions, but for the
  time being, as reported here
  https://bugs.freedesktop.org/show_bug.cgi?id=91393#c25 (and as
  personally tested) reverting those two commits fixes the problem.

  Would that be possible to release a fixed version for the 4.2.0
  stream?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bettini1378 F pulseaudio
   /dev/snd/controlC1:  bettini1378 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Dec  4 19:01:00 2015
  HibernationDevice: RESUME=UUID=7ddbc972-3ad6-40de-9313-2bb9395145f9
  InstallationDate: Installed on 2015-05-08 (210 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Dell Precision M3800
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=dd2c7064-53b9-4720-96ab-5e8a3f2db3ea ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-07 (26 days ago)
  dmi.bios.date: 08/17/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/17/2015:svnDellInc.:pnDellPrecisionM3800:pvrA10:rvnDellInc.:rnDellPrecisionM3800:rvrA10:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nouveau/+bug/1522922/+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 1522922] Re: Screen flickering in Intel i915 driver

2016-04-30 Thread Boris Erdmann
I am affected by this bug on dell xps 13 9350 both on FHD and QHD.
Running kernel 4.6rc5 from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.6-rc5-wily/ helps as a work-around.

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

Title:
  Screen flickering in Intel i915 driver

Status in Nouveau Xorg driver:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Triaged

Bug description:
  There's an upstream bug reported here
  https://bugs.freedesktop.org/show_bug.cgi?id=91393 that causes screen
  flickering when using the Intel i915 builtin driver (at resolutions
  lower than the maximal one).

  I think that it will be fixed in newer kernel versions, but for the
  time being, as reported here
  https://bugs.freedesktop.org/show_bug.cgi?id=91393#c25 (and as
  personally tested) reverting those two commits fixes the problem.

  Would that be possible to release a fixed version for the 4.2.0
  stream?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bettini1378 F pulseaudio
   /dev/snd/controlC1:  bettini1378 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Dec  4 19:01:00 2015
  HibernationDevice: RESUME=UUID=7ddbc972-3ad6-40de-9313-2bb9395145f9
  InstallationDate: Installed on 2015-05-08 (210 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Dell Precision M3800
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=dd2c7064-53b9-4720-96ab-5e8a3f2db3ea ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-07 (26 days ago)
  dmi.bios.date: 08/17/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/17/2015:svnDellInc.:pnDellPrecisionM3800:pvrA10:rvnDellInc.:rnDellPrecisionM3800:rvrA10:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nouveau/+bug/1522922/+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 539630] Re: Xorg display corruption, Dell Inspiron 6400, Lucid Beta ISO test

2016-03-14 Thread Boris Gjenero
I'm getting a similar bug in 16.04 on my Inspiron 6400 with X1300 and a
1680x1050 display. I have disabled graphical overlays during boot
because I prefer to see boot text. Corruption starts after the switch
from ordinary VGA text mode to a high resolution text mode which I
assume is implemented using a graphics mode. In that text mode,
corruption is mostly flashing long vertical bright bars rising from the
bottom. In X, corruption is mostly short horizontal lines on a dark area
to the right of a bright area, and the long vertical bars seen in text
mode rarely appear.

The corruption never propagates via screen operations like scrolling, so
it doesn't seem to be in memory. It's as if there is something wrong
with the video mode or LVDS communication with the display. I made the
corruption go away in X by first switching to a lower resolution via
"xrandr --output LVDS --mode 1400x1050"  and then going back to the
native resolution via "xrandr --output LVDS --mode 1680x1050". I'm not
getting any corruption in Windows 7, so I don't think this is a hardware
problem.

** Attachment added: "Vertical bar corruption in text mode"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/539630/+attachment/4599344/+files/P3140013.JPG

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

Title:
  Xorg display corruption, Dell Inspiron 6400, Lucid Beta ISO test

Status in xserver-xorg-video-ati package in Ubuntu:
  Fix Released

Bug description:
  ISO testing, AMD64 test: ISO image http://cdimage.ubuntu.com/daily-
  live/20100316/lucid-desktop-amd64.iso

  Test: http://iso.qa.ubuntu.com/qatracker/result/3764/6

  Hardware: Dell Inspirion 6400, Video: ATI Technologies Inc M52
  [Mobility Radeon X1300]

  During installation while ubiquity is asking for configuration
  settings, the Xorg display is showing small amounts of random noise
  across the screen.  This is approximately 16 pixels wide, 1 pixel
  high, very light in colour and only shows up against the darker parts
  of the background.  It is a minor irritation.

  However, this problem goes once Lucid is installed and one boots into
  the system.

  I tried to report the bug using apport-bug against xorg, but this tool
  informs me that "This is not a genuine Ubuntu package".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/539630/+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 1509139] Re: Shows "Chromium isn't your default browser" since 15.10.

2016-01-05 Thread Boris Aranovich
Happens on 14.04.01 as well, and has been happening for a while.

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

Title:
  Shows "Chromium isn't your default browser" since 15.10.

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in google-chrome package in Ubuntu:
  Confirmed
Status in xdg-utils package in Ubuntu:
  Confirmed

Bug description:
  Since the 15.10.  upgrade Chromium shows on every launch "Chromium
  isn't your default browser", even when i select "Set as default" or
  "Don't ask again".

  Chromium is set as default application for "Web" at System Settings ->
  Details -> Default Applications.

  Version 45.0.2454.101 Ubuntu 15.10 (64-bit)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1509139/+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 1509846] Re: lightdm crashes on window open in Ubuntu 15.10 intel

2015-11-15 Thread Boris Dalstein
I am experiencing the same issue, but on Kubuntu 15.04. I experience a
crash that logs me out every few hours or so, for seemingly random
actions, but it might indeed be when a new window is created. Last crash
was when doing "Ctrl+T" on Google Chrome to open a new tab. Attached is
the corresponding Xorg log.

** Attachment added: "Xorg.0.log.old"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509846/+attachment/4519815/+files/Xorg.0.log.old

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

Title:
  lightdm crashes on window open in Ubuntu 15.10 intel

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Symptom: xorg crashes on windows creation

  How to reproduce: No 100% reproducibility, however intensively using
  2D/3D acceleration triggers the bug (e.g. by opening several new
  windows and/or menus in a Unity desktop environment)

  Affected hardware: Intel HD Graphics 4400/5000 etc
  Affected software:
  - kernel 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64
  - Ubuntu 15.10 with Unity (because of compiz 2D/3D acceleration)
  - any other software using direct rendering (e.g. VLC)

  Workaround:
  - Disable window animations in Compiz reduces the frequency of the crashes.
  Use compizconfig-settings-manager for this tweak (sudo apt-get install 
compizconfig-settings-manager)

  
  [original description below]

  I get crashes, when I open a new window in an already started
  application. It happens irregularely, but I can force the crash if I
  open several new message windows in thunderbird. But it also happens
  in other applilcations, for example a new terminal window.

  This is the output during the crash in /var/log/Xorg.0.log
  [   253.500] (EE)
  [   253.500] (EE) Backtrace:
  [   253.500] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55f09075b62e]
  [   253.500] (EE) 1: /usr/bin/X (0x55f0905a7000+0x1b8999) [0x55f09075f999]
  [   253.500] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f44130a8000+0x352f0) 
[0x7f44130dd2f0]
  [   253.500] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x24f18) [0x7f440f4a3f18]
  [   253.500] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x26157) [0x7f440f4a5157]
  [   253.500] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x2b4b1) [0x7f440f4aa4b1]
  [   253.500] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x804e4) [0x7f440f4ff4e4]
  [   253.501] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x80e2c) [0x7f440f4ffe2c]
  [   253.501] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x82e1a) [0x7f440f501e1a]
  [   253.501] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x4197c) [0x7f440f4c097c]
  [   253.501] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x59906) [0x7f440f4d8906]
  [   253.501] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55f090604654]
  [   253.501] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55f09075f274]
  [   253.501] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55f09060a502]
  [   253.501] (EE) 14: /usr/bin/X (0x55f0905a7000+0xf495a) [0x55f09069b95a]
  [   253.501] (EE) 15: /usr/bin/X (0x55f0905a7000+0xf5ef5) [0x55f09069cef5]
  [   253.501] (EE) 16: /usr/bin/X (0x55f0905a7000+0x5818f) [0x55f0905ff18f]
  [   253.501] (EE) 17: /usr/bin/X (0x55f0905a7000+0x5c34b) [0x55f09060334b]
  [   253.501] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f44130c8a40]
  [   253.501] (EE) 19: /usr/bin/X (_start+0x29) [0x55f0905ed6c9]
  [   253.501] (EE)
  [   253.501] (EE) Segmentation fault at address 0x0
  [   253.501] (EE)
  Fatal server error:
  [   253.501] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [   253.501] (EE)
  [   253.501] (EE)
  Please consult the The X.Org Foundation support
   at http://wiki.x.org
   for help.
  [   253.501] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [   253.502] (EE)
  [   253.502] (II) AIGLX: Suspending AIGLX clients for VT switch
  [   253.588] (EE) Server terminated with error (1). Closing log file.
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu3
  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
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-11-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
    

[Desktop-packages] [Bug 1509846] Re: lightdm crashes on window open in Ubuntu 15.10 intel

2015-11-15 Thread Boris Dalstein
Sorry, I meant Kubuntu 15.10.

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

Title:
  lightdm crashes on window open in Ubuntu 15.10 intel

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Symptom: xorg crashes on windows creation

  How to reproduce: No 100% reproducibility, however intensively using
  2D/3D acceleration triggers the bug (e.g. by opening several new
  windows and/or menus in a Unity desktop environment)

  Affected hardware: Intel HD Graphics 4400/5000 etc
  Affected software:
  - kernel 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64
  - Ubuntu 15.10 with Unity (because of compiz 2D/3D acceleration)
  - any other software using direct rendering (e.g. VLC)

  Workaround:
  - Disable window animations in Compiz reduces the frequency of the crashes.
  Use compizconfig-settings-manager for this tweak (sudo apt-get install 
compizconfig-settings-manager)

  
  [original description below]

  I get crashes, when I open a new window in an already started
  application. It happens irregularely, but I can force the crash if I
  open several new message windows in thunderbird. But it also happens
  in other applilcations, for example a new terminal window.

  This is the output during the crash in /var/log/Xorg.0.log
  [   253.500] (EE)
  [   253.500] (EE) Backtrace:
  [   253.500] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55f09075b62e]
  [   253.500] (EE) 1: /usr/bin/X (0x55f0905a7000+0x1b8999) [0x55f09075f999]
  [   253.500] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f44130a8000+0x352f0) 
[0x7f44130dd2f0]
  [   253.500] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x24f18) [0x7f440f4a3f18]
  [   253.500] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x26157) [0x7f440f4a5157]
  [   253.500] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x2b4b1) [0x7f440f4aa4b1]
  [   253.500] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x804e4) [0x7f440f4ff4e4]
  [   253.501] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x80e2c) [0x7f440f4ffe2c]
  [   253.501] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x82e1a) [0x7f440f501e1a]
  [   253.501] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x4197c) [0x7f440f4c097c]
  [   253.501] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f440f47f000+0x59906) [0x7f440f4d8906]
  [   253.501] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55f090604654]
  [   253.501] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55f09075f274]
  [   253.501] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55f09060a502]
  [   253.501] (EE) 14: /usr/bin/X (0x55f0905a7000+0xf495a) [0x55f09069b95a]
  [   253.501] (EE) 15: /usr/bin/X (0x55f0905a7000+0xf5ef5) [0x55f09069cef5]
  [   253.501] (EE) 16: /usr/bin/X (0x55f0905a7000+0x5818f) [0x55f0905ff18f]
  [   253.501] (EE) 17: /usr/bin/X (0x55f0905a7000+0x5c34b) [0x55f09060334b]
  [   253.501] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f44130c8a40]
  [   253.501] (EE) 19: /usr/bin/X (_start+0x29) [0x55f0905ed6c9]
  [   253.501] (EE)
  [   253.501] (EE) Segmentation fault at address 0x0
  [   253.501] (EE)
  Fatal server error:
  [   253.501] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [   253.501] (EE)
  [   253.501] (EE)
  Please consult the The X.Org Foundation support
   at http://wiki.x.org
   for help.
  [   253.501] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [   253.502] (EE)
  [   253.502] (II) AIGLX: Suspending AIGLX clients for VT switch
  [   253.588] (EE) Server terminated with error (1). Closing log file.
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu3
  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
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-11-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2015-10-20 (6 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  MachineType: LENOVO 20266
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: 

[Desktop-packages] [Bug 1499079] [NEW] gnome-power-statistics shows data for 7 days while combobox's value is set to "6 hours"

2015-09-23 Thread Boris
Public bug reported:

When I start gnome-power-statistics, it shows data for 7 days on
the chart, while combobox's value is set to "6 hours".

Screenshot: http://i.imgur.com/I9LslvB.png

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


** Tags: gnome-power-statistics

** Attachment added: "Screenshot illustrating the problem"
   
https://bugs.launchpad.net/bugs/1499079/+attachment/4472679/+files/gnome-power-statistics.png

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

Title:
  gnome-power-statistics shows data for 7 days while combobox's value is
  set to "6 hours"

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  When I start gnome-power-statistics, it shows data for 7 days on
  the chart, while combobox's value is set to "6 hours".

  Screenshot: http://i.imgur.com/I9LslvB.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1499079/+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 1184699] Re: Canon LIDE 110 can only scan once, then I need to replug the usb cable

2015-06-11 Thread Boris Boutkov
Version 1.025-git does not fix the issue for me. ubuntu 14.04

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

Title:
  Canon LIDE 110 can only scan once, then I need to replug the usb cable

Status in Simple Scan:
  New
Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  I have a Canon LIDE 110 scanner which works by default on ubuntu 13.04. 
  The problem is after first scan, I can not scan for second time. I need to 
reconnect the USB cable to use the scanner again.

  # TEST 1 : without reconnecting the usb cable
  francois@pc:~$ scanimage -v  test1.jpg # success
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total
  # I don't unplug plug the usb cable.
  francois@pc:~$ scanimage -v  test2.jpg # FAIL
  scanimage: no SANE devices found

  # TEST 2 : reconnect usb cable between scan attempts
  francois@pc:~$ scanimage -v  test1.jpg # success
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total
  # I unplug and replug the usb cable.
  francois@pc:~$ scanimage -v  test2.jpg # SUCCESS
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total

  francois@pc:~$ dmesg # extract
  [  829.365158] usb 3-1: USB disconnect, device number 2
  [  834.935000] usb 3-1: new high-speed USB device number 4 using xhci_hcd
  [  834.952515] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909
  [  834.952519] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [  834.952522] usb 3-1: Product: CanoScan
  [  834.952524] usb 3-1: Manufacturer: Canon
  [ 1623.738811] usb 3-1: USB disconnect, device number 4
  [ 1623.739072] xhci_hcd :00:14.0: Slot 3 endpoint 6 not removed from BW 
list!
  [ 1625.528827] usb 3-1: new high-speed USB device number 5 using xhci_hcd
  [ 1625.546327] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909
  [ 1625.546331] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 1625.546334] usb 3-1: Product: CanoScan
  [ 1625.546336] usb 3-1: Manufacturer: Canon

  francois@pc:~$ uname -a  cat /etc/issue
  Linux pc 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux
  Ubuntu 13.04 \n \l

  The problem was reported here by someone else :
  http://askubuntu.com/questions/278473/canon-lide-110-should-reconnect-
  usb-for-each-scan

  Thanks
  François

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/1184699/+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 1261666] Re: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed.

2015-04-09 Thread Boris Hollas
So what can I do to fix this problem on 14.04?

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

Title:
  [pulseaudio] module.c: Failed to load module module-echo-cancel
  (argument: aec_method=webrtc): initia lization failed.

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Hello! 
  13.10.
  Trying to load module-echo-cancel with webrtc and get:

  [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: 
aec_method=webrtc): initia
  lization failed.

  I guess this is wrong...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1261666/+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 1261666] Re: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed.

2015-04-08 Thread Boris Hollas
Will there be an update for 14.04 as well?

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

Title:
  [pulseaudio] module.c: Failed to load module module-echo-cancel
  (argument: aec_method=webrtc): initia lization failed.

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Hello! 
  13.10.
  Trying to load module-echo-cancel with webrtc and get:

  [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: 
aec_method=webrtc): initia
  lization failed.

  I guess this is wrong...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1261666/+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 1261666] Re: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed.

2015-04-07 Thread Boris Hollas
Same problem with 14.04:

~$ pactl load-module module-echo-cancel source_name=echosource aec_method=webrtc
Failure: Module initialization failed

From the syslog:
pulseaudio[7477]: [pulseaudio] module-echo-cancel.c: Invalid echo canceller 
implementation 'webrtc'

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

Title:
  [pulseaudio] module.c: Failed to load module module-echo-cancel
  (argument: aec_method=webrtc): initia lization failed.

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Hello! 
  13.10.
  Trying to load module-echo-cancel with webrtc and get:

  [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: 
aec_method=webrtc): initia
  lization failed.

  I guess this is wrong...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1261666/+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 1410103] [NEW] Right click on application icon doesn't work on tiling display

2015-01-13 Thread Boris
Public bug reported:

When clicking an application icon, Ubuntu tiles it's windows as expected.
But, if when on tile display, I right click the application icon, to close all 
windows for example, the right click menu opens up, but I can't choose anything 
from it.
The right click menu is then stuck, and is not highlighted when I hover over it 
with the mouse. This is until I right click again
An example use-case that happens to me a lot is if I want to tile all my 
gnome-terminal windows to see if there's anything important running, and after 
I see there's nothing important, I want to close all windows, so I right click 
the gnome-terminal icon.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu8
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
CurrentDesktop: Unity
Date: Tue Jan 13 10:17:53 2015
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.18, 3.16.0-25-generic, x86_64: installed
 virtualbox, 4.3.18, 3.16.0-28-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
InstallationDate: Installed on 2014-11-10 (63 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
MachineType: Gigabyte Technology Co., Ltd. H87-D3H
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=f268972b-9648-446d-b653-0cb80aa97b71 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/17/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87-D3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd01/17/2014:svnGigabyteTechnologyCo.,Ltd.:pnH87-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87-D3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: H87-D3H
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Wed Jan  7 15:39:13 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVideo BusKEYBOARD, id 7
 inputPower Button KEYBOARD, id 8
 inputPixArt USB Optical Mouse MOUSE, id 9
 inputAT Raw Set 2 keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id6613 
 vendor ACI
xserver.version: 2:1.16.0-1ubuntu1.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic

** Attachment added: A picture to show that the right click menu is not 
highlighted when hovering over it with the mouse - its just stuck
   
https://bugs.launchpad.net/bugs/1410103/+attachment/4297038/+files/Screenshot%20from%202015-01-13%2010%3A31%3A25.png

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

Title:
  Right click on application icon doesn't work on tiling display

Status in xorg package in Ubuntu:
  New

Bug description:
  When clicking an application icon, Ubuntu tiles it's windows as expected.
  But, if when on tile display, I right click the application icon, to close 
all windows for example, the right click menu opens up, but I can't choose 
anything 

[Desktop-packages] [Bug 1410103] Re: Right click on application icon doesn't work on tiling display

2015-01-13 Thread Boris
A picture to show that the right click menu is not highlighted when
hovering over it with the mouse - its just stuck

** Attachment removed: A picture to show that the right click menu is not 
highlighted when hovering over it with the mouse - its just stuck
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1410103/+attachment/4297038/+files/Screenshot%20from%202015-01-13%2010%3A31%3A25.png

** Attachment added: A picture to show that the right click menu is not 
highlighted when hovering over it with the mouse - its just stuck
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1410103/+attachment/4297063/+files/Screenshot%20from%202015-01-13%2010%3A40%3A29.png

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

Title:
  Right click on application icon doesn't work on tiling display

Status in xorg package in Ubuntu:
  New

Bug description:
  When clicking an application icon, Ubuntu tiles it's windows as expected.
  But, if when on tile display, I right click the application icon, to close 
all windows for example, the right click menu opens up, but I can't choose 
anything from it.
  The right click menu is then stuck, and is not highlighted when I hover over 
it with the mouse. This is until I right click again
  An example use-case that happens to me a lot is if I want to tile all my 
gnome-terminal windows to see if there's anything important running, and after 
I see there's nothing important, I want to close all windows, so I right click 
the gnome-terminal icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8
  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
  CurrentDesktop: Unity
  Date: Tue Jan 13 10:17:53 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.18, 3.16.0-25-generic, x86_64: installed
   virtualbox, 4.3.18, 3.16.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2014-11-10 (63 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: Gigabyte Technology Co., Ltd. H87-D3H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=f268972b-9648-446d-b653-0cb80aa97b71 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87-D3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd01/17/2014:svnGigabyteTechnologyCo.,Ltd.:pnH87-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87-D3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: H87-D3H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Wed Jan  7 15:39:13 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputPixArt USB Optical Mouse MOUSE, id 9
   inputAT Raw Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   
  

[Desktop-packages] [Bug 1366556] Re: PPC: libgl1-mesa-dri doesn't provide 3D acceleration

2014-10-20 Thread Boris Reinhard
Same on my 12inch iBook G4, on Lubuntu 14.10 daily as well as 14.04.1 LTS,
it also does not seem to detect/ recognize my graphic chip correctly.

Id: PowerBook6,5
CPU type: G4 (version 1.1) 1,2 Ghz
Boot Rom Version: 4.8.7f1
768 MB RAM

GPU: RV 280 M9+ (variant of Radeon 9200 with 4x AGP, tho AGP not working stable 
causing freezes so having to use radeon.agpmode=-1)
GPU-ID: 0x5c63

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

Title:
  PPC: libgl1-mesa-dri doesn't provide 3D acceleration

Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  libgl1-mesa-dri doesn't provide 3D acceleration.

  Package: libgl1-mesa-dri 10.2.6-1ubuntu3 (Lubuntu 14.10 beta PowerPC)
  System specification: http://www.xenosoft.de/pastebin_AmigaOne_X1000
  Tested graphics cards: AMD CYPRESS, and AMD BARTS

  Preliminary solution: http://forum.hyperion-
  entertainment.biz/viewtopic.php?f=35t=2614

  LIBGL_DEBUG=verbose glxinfo

  name of display: :0
  libGL: screen 0 does not appear to be DRI3 capable
  libGL: pci id for fd 4: 1002:6738, driver r600
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r600_dri.so
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r600_dri.so
  libGL: driver does not expose __driDriverGetExtensions_r600(): 
/usr/lib/powerpc-linux-gnu/dri/r600_dri.so: undefined symbol: 
__driDriverGetExtensions_r600
  libGL: Can't open configuration file /home/christian/.drirc: No such file or 
directory.
  libGL: Can't open configuration file /home/christian/.drirc: No such file or 
directory.
  libGL error: failed to load driver: r600
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so
  libGL: Can't open configuration file /home/christian/.drirc: No such file or 
directory.
  libGL error: failed to load driver: swrast
  Error: couldn't find RGB GLX visual or fbconfig

  dmesg | grep radeon

  [0.620345] [drm] radeon kernel modesetting enabled.
  [0.789281] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
  [0.789296] radeon :01:00.0: GTT: 1024M 0x4000 - 
0x7FFF
  [0.789440] [drm] radeon: 1024M of VRAM memory ready
  [0.789448] [drm] radeon: 1024M of GTT memory ready.
  [0.820700] radeon :01:00.0: WB enabled
  [0.820712] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0xc00276ab2c00
  [0.820728] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0xc00276ab2c0c
  [0.834239] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00072118 and cpu addr 0xd800901b2118
  [0.834318] radeon :01:00.0: radeon: using MSI.
  [0.834362] [drm] radeon: irq initialized.
  [1.191354] [drm] radeon: power management initialized
  [1.561110] radeon :01:00.0: fb0: radeondrmfb frame buffer device
  [1.561516] radeon :01:00.0: registered panic notifier
  [1.561844] [drm] Initialized radeon 2.36.0 20080528 for :01:00.0 
on minor 0

  dmesg | grep drm

  [0.620278] [drm] Initialized drm 1.1.0 20060810
  [0.620345] [drm] radeon kernel modesetting enabled.
  [0.620786] [drm] initializing kernel modesetting (BARTS 0x1002:0x6738 
0x1682:0x3107).
  [0.620806] [drm] register mmio base: 0xA002
  [0.620812] [drm] register mmio size: 131072
  [0.789305] [drm] Detected VRAM RAM=1024M, BAR=256M
  [0.789312] [drm] RAM width 256bits DDR
  [0.789440] [drm] radeon: 1024M of VRAM memory ready
  [0.789448] [drm] radeon: 1024M of GTT memory ready.
  [0.789472] [drm] Loading BARTS Microcode
  [0.789566] [drm] GART: num cpu pages 262144, num gpu pages 262144
  [0.820556] [drm] PCIE GART of 1024M enabled (table at 
0x00273000).
  [0.834254] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [0.834261] [drm] Driver supports precise vblank timestamp query.
  [0.834362] [drm] radeon: irq initialized.
  [0.851016] [drm] ring test on 0 succeeded in 3 usecs
  [0.851092] [drm] ring test on 3 succeeded in 2 usecs
  [1.036506] [drm] ring test on 5 succeeded in 2 usecs
  [1.036518] [drm] UVD initialized successfully.
  [1.036876] [drm] Enabling audio 0 support
  [1.036938] [drm] ib test on ring 0 succeeded in 0 usecs
  [1.036995] [drm] ib test on ring 3 succeeded in 0 usecs
  [1.187983] [drm] ib test on ring 5 succeeded
  [1.190274] [drm] Radeon Display Connectors
  [1.190283] [drm] Connector 0:
  [1.190289] [drm]   DP-1
  [1.190293] [drm]   HPD4
  [1.190300] [drm]   

[Desktop-packages] [Bug 1371019] [NEW] nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build

2014-09-18 Thread Boris
Public bug reported:

encountered while upgrading to kernel 3.16.0-16

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331-updates 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
Uname: Linux 3.16.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
DKMSKernelVersion: 3.16.0-16-generic
Date: Thu Sep 18 11:42:24 2014
InstallationDate: Installed on 2014-09-07 (11 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140905)
PackageVersion: 331.89-0ubuntu5
SourcePackage: nvidia-graphics-drivers-331-updates
Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package third-party-packages utopic

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

Title:
  nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module
  failed to build

Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  New

Bug description:
  encountered while upgrading to kernel 3.16.0-16

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-16-generic
  Date: Thu Sep 18 11:42:24 2014
  InstallationDate: Installed on 2014-09-07 (11 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140905)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1371019/+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 1307163] Re: not work gnome-screensaver-command -d

2014-09-08 Thread Boris Boruchovich
I too am affect by this.  gnome-screensaver-command -d was working with
Ubuntu version 12.04. It is not working with Ubuntu 14.04. Is there a
recommended way to unlock the screensaver programmatically?

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

Title:
  not work gnome-screensaver-command -d

Status in “blueproximity” package in Ubuntu:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Confirmed

Bug description:
  After the upgrade not work gnome-screensaver-command --deactivate
  jwm + gnome-screensaver impossible to see video because not working 
gnome-screensaver-command -d

  not works:
  gnome-screensaver-command -a
  gnome-screensaver-command -d
  gnome-screensaver-command -l

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 13 18:47:32 2014
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 0
  InstallationDate: Installed on 2014-04-11 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140410)
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueproximity/+bug/1307163/+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 1363598] [NEW] Xorg freeze

2014-08-31 Thread Boris Hugo
Public bug reported:

In Lubuntu 14.04.01, the display freezes after mere minutes\hours of use.
In Ubuntu 14.04.01 BTW, the system doesn't even boots after installation (all I 
get is a black screen)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Aug 31 11:38:08 2014
InstallationDate: Installed on 2014-08-28 (2 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723)
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug freeze trusty

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

Title:
  Xorg freeze

Status in “xorg” package in Ubuntu:
  New

Bug description:
  In Lubuntu 14.04.01, the display freezes after mere minutes\hours of use.
  In Ubuntu 14.04.01 BTW, the system doesn't even boots after installation (all 
I get is a black screen)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 31 11:38:08 2014
  InstallationDate: Installed on 2014-08-28 (2 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140723)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2014-08-31 Thread Boris Hugo
I meant Xubuntu, not Lubuntu

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

Title:
  Xorg freeze

Status in “xorg” package in Ubuntu:
  New

Bug description:
  In Lubuntu 14.04.01, the display freezes after mere minutes\hours of use.
  In Ubuntu 14.04.01 BTW, the system doesn't even boots after installation (all 
I get is a black screen)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 31 11:38:08 2014
  InstallationDate: Installed on 2014-08-28 (2 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140723)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


  1   2   >