[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Disco that was purported to
fix this bug report has been removed because one or more bugs that were
to be fixed by the upload have failed verification and been in this
state for more than 10 days.

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Disco that was purported to
fix this bug report has been removed because one or more bugs that were
to be fixed by the upload have failed verification and been in this
state for more than 10 days.

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Disco that was purported to
fix this bug report has been removed because one or more bugs that were
to be fixed by the upload have failed verification and been in this
state for more than 10 days.

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Disco that was purported to
fix this bug report has been removed because one or more bugs that were
to be fixed by the upload have failed verification and been in this
state for more than 10 days.

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Bionic that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Bionic that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Bionic that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Bionic that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

** Changed in: kbd (Ubuntu Bionic)
   Status: Fix Committed => Won't Fix

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Bionic that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Xenial that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Bionic that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Xenial that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Xenial that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Xenial that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Xenial that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

** Changed in: kbd (Ubuntu Xenial)
   Status: Fix Committed => Won't Fix

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 520546] Proposed package removed from archive

[Steve Langasek]

The version of kbd in the proposed pocket of Xenial that was purported
to fix this bug report has been removed because one or more bugs that
were to be fixed by the upload have failed verification and been in this
state for more than 10 days.

-- 
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:
  Fix Committed
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 

[Desktop-packages] [Bug 1547589] Re: rtkit-daemon flooding syslog

[Kai Kasurinen]

** Bug watch added: Debian Bug tracker #939615
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939615

** Also affects: rtkit (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939615
   Importance: Unknown
   Status: Unknown

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

Title:
  rtkit-daemon flooding syslog

Status in rtkit package in Ubuntu:
  Confirmed
Status in rtkit package in Debian:
  Unknown

Bug description:
  rtkit is flooding syslog with the following:

  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.

  This may be related to but #1547585

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rtkit 0.11-4
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:42:58 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: rtkit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1623639] Re: netpbm: "anytopnm" doesn't recognize some file types

[Ubuntu Foundations Team Bug Bot]

The attachment "anytopnm.diff" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  netpbm: "anytopnm" doesn't recognize some file types

Status in netpbm-free package in Ubuntu:
  Confirmed

Bug description:
  /usr/bin/anytopnm uses the output of "file" to recognize the image format of 
the input file.
  Apparently the output of "file" has changed, and therefore it is no longer 
correctly recognized by anytopnm. Example:

  $ file /tmp/x.ppm
  /tmp/x.ppm: Netpbm image data, size = 5100 x 6600, rawbits, pixmap

  However, /usr/bin/anytopnm (line 64) looks for the strings *PBM* |
  *PGM* | *PPM* )

  For example:

  $ cat /tmp/x.ppm | anytopnm
  /usr/bin/anytopnm: unknown file type:  Netpbm image data, size = 5100 x 6600, 
rawbits, pixmap

  Suggested fix: update /usr/bin/anytopnm to recognize the string
  "Netpbm" in addition to PBM, PGM, PPM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netpbm-free/+bug/1623639/+subscriptions

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

[Desktop-packages] [Bug 1577527] Re: Calendar Theme Issue

[Launchpad Bug Tracker]

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

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

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

Title:
  Calendar Theme Issue

Status in gnome-calendar package in Ubuntu:
  Expired

Bug description:
  
  When search for Calendar in Dash and then open Calendar there are little 
white edges at the egde of the calendar with
  Ambiance theme enabled? But when change the theme to Radiance or a community 
created theme the white edges are gone?

  This issue is in Ubuntu 16.04 x64. I dont know if its only me or
  someone else has this issue?

  /Martin.

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

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

[Desktop-packages] [Bug 1836804] Re: Unable to locate mail spool file.

[Launchpad Bug Tracker]

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

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

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

Title:
  Unable to locate mail spool file.

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  If i launch Thunderbird I will get this error

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:60.8.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  artem  1115 F pulseaudio
  BuildID: 20190705213317
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 16 23:31:05 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2019-07-14 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190712)
  IpRoute:
   default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.104 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Prefs:
   extensions.lastAppVersion: "60.8.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   network.predictor.cleaned-up: true (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=60.8.0/20190705213317
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832E
  dmi.board.vendor: HP
  dmi.board.version: 26.34
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.40:bd05/17/2018:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832E:rvr26.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 250 G6 Notebook PC
  dmi.product.sku: 3DN65ES#ACB
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1834375] Re: Gaia.com videos unsupported

[Launchpad Bug Tracker]

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

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

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

Title:
  Gaia.com videos unsupported

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Firefox could not play videos on Gaia.com.  The error message blamed
  the browser.  So I downloaded and installed the browser Opera, with
  the same results and message.  Both browsers would play Youtube
  videos.

  Please enable Gaia.com videos.

  Thanks.

  I downloaded the latest Ubuntu release today.  18.04...something

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jun 26 17:57:24 2019
  DistUpgraded: 2019-06-26 11:14:51,559 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
  InstallationDate: Installed on 2019-06-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=dfa2862a-4da8-414d-9f41-cecde30f67c6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-06-26 (0 days ago)
  dmi.bios.date: 06/23/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G2 v02.02
  dmi.board.name: 3048h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G2v02.02:bd06/23/2011:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Jun 26 10:11:57 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1791574] Re: gnome-shell crashed with SIGABRT: assertion failed "window->display->focus_window != window" in meta_window_unmanage

[Steve Langasek]

Hello Rocko, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.4-0ubuntu18.04.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mutter (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  gnome-shell crashed with SIGABRT: assertion failed
  "window->display->focus_window != window" in meta_window_unmanage

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed
Status in mutter source package in Disco:
  Fix Released

Bug description:
  [ Description ]

  GNOME Shell crashes when interacting with some "take-input" windows
  such as the jetbrains products (you can snap install the 2008 versions
  which are affected), see
  https://gitlab.gnome.org/GNOME/mutter/issues/308

  [ Test case ]
   Run this script:
   $ wget -O - https://gitlab.gnome.org/3v1n0/mutter/snippets/453/raw | python3

   - The shell should not crash when the windows are closed.

  [ Regression potential ]

  The patch introduces changes to the window focus handling, so a window
  might not be properly focused in some cases.

  [ Notes to the SRU team ]

  This fix is still in process of being released to eoan / disco too.


  

  https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5
  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/308

  Originally reported as bug 1422253 and fixed in 18.04, but that crash
  (fixed) was due to a different condition.

  Test case: https://gitlab.gnome.org/3v1n0/mutter/snippets/453

  ---

  gnome-shell crashed and restarted while I was using it.

  ProblemType: CrashDistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-1ubuntu1
  Uname: Linux 4.19.0-041900rc3-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 10 12:39:16 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1536081658
  InstallationDate: Installed on 2017-08-16 (389 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/rocko
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bashSignal: 6SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   meta_window_unmanage () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-08-15 (25 days ago)
  UserGroups: adm bumblebee cdrom dip kvm lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1827401] Re: gnome-shell crashed in meta_workspace_index -> meta_workspace_activate_with_focus -> meta_window_activate_full

[Steve Langasek]

Hello errors.ubuntu.com, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.4-0ubuntu18.04.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mutter (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  gnome-shell crashed in meta_workspace_index ->
  meta_workspace_activate_with_focus -> meta_window_activate_full

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed
Status in mutter source package in Disco:
  Fix Released

Bug description:
  [ Description ]

  Shell crashes on meta_workspace_index

  [ Test case ]

  No clear way to reproduce this, although we consider fixed monitoring
  the presence of automatic reports at:

  https://errors.ubuntu.com/problem/f98d5edcc7588c443201f119bc2c4b586a897cfd

  [ Regression potential ]

  None, a window might not be focused although it's an unmanaging one
  so, not really a regression.

  ---

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

  ---

  The gjs part of this is actually the same of bug #1812527

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

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

[Desktop-packages] [Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()

[Steve Langasek]

Hello errors.ubuntu.com, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.4-0ubuntu18.04.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mutter (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  gnome-shell crashed with SIGSEGV in g_hash_table_iter_next →
  meta_display_list_windows → meta_workspace_list_windows →
  ffi_call_SYSV → ffi_call()

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Won't Fix
Status in mutter source package in Bionic:
  Fix Committed
Status in mutter source package in Disco:
  Won't Fix

Bug description:
  [ Description ]

  GNOME shell crashes on restart when some window actors are opened

  [ Test case ]

  - Run gnome-shell in Xorg, start some windows
  - Hit Alt+F2
  - Write 'r' and press Enter

  - The shell should restart without crashing in
  meta_workspace_list_windows

  [ Regression potential ]

  Javascript errors might be emitted when trying to access to
  invalidated data, but nothing really harmful.

  [ Note ]

  This crash doesn't affect versions after 3.28 for various reasons: 
   - The JS code triggering it isn't there anymore
   - MetaScreen doesn't exist anymore.

  Similar crashes might happen in newer versions, but as per different
  code paths, and so to be reported as different bugs.

  ---

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

  https://errors.ubuntu.com/problem/ac8df0b1e2d67e423c634fde1a3acecd3c381d58
  https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64
  https://errors.ubuntu.com/problem/1e69eadeb69f4e2b8aa933205d2be3a8db4af36c
  https://errors.ubuntu.com/problem/6f7810166a3ae02cc8025514d6ffbbde10063e76
  https://errors.ubuntu.com/problem/1bfbc00c70cfe6f4f2b66b4efc86f5c089c28680

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

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

[Desktop-packages] [Bug 1823448] Re: cogl ftbfs in disco (i386 only)

[Steve Langasek]

Hello Matthias, or anyone else affected,

Accepted cogl into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/cogl/1.22.2-6ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: block-proposed-disco

** Tags added: verification-needed verification-needed-disco

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

Title:
  cogl ftbfs in disco (i386 only)

Status in cogl package in Ubuntu:
  Fix Released
Status in cogl source package in Disco:
  Fix Committed

Bug description:
  * Impact
  It fails to build on i386 (hanging in tests)

  * Test case
  The i386 build should work

  * Regression potential
  There is no change to the code, just test that GNOME and the video player 
(cogl users) still work correctly

  

  
  
https://launchpadlibrarian.net/417939758/buildlog_ubuntu-disco-i386.cogl_1.22.2-6_BUILDING.txt.gz

  make  check-local
  make[5]: Entering directory '/<>/tests'
  ( cd ./conform && make  test ) || exit $?
  make[6]: Entering directory '/<>/tests/conform'
  Key:
  ok = Test passed
  n/a = Driver is missing a feature required for the test
  FAIL = Unexpected failure
  FIXME = Test failed, but it was an expected failure
  PASS! = Unexpected pass

     Test  GL+FF GL+ARBFP GL+GLSL GL-NPT
  GL3ES2 ES2-NPT

   test_pipeline_user_matrix: ok   ok  ok ok ok 
ok  ok
  test_blend_strings: ok   ok  ok ok ok 
ok  ok
  test_blend: ok   ok  ok ok ok 
ok  ok
    test_premult:  FIXMEFIXME   FIXME  FIXME  FIXME  
FIXME   FIXME
   test_path: ok   ok  ok ok ok 
ok  ok
  test_path_clip: ok   ok  ok ok ok 
ok  ok
     test_depth_test: ok   ok  ok ok ok 
ok  ok
     test_color_mask: ok   ok  ok ok ok 
ok  ok
  make[6]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[6]: *** Waiting for unfinished jobs
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
  make[6]: *** wait: No child processes.  Stop.
  make[2]: *** wait: No child processes.  Stop.
  make[2]: *** Waiting for unfinished jobs
  make[5]: *** [Makefile:875: test] Terminated
  make[2]: *** wait: No child processes.  Stop.
  E: Caught signal ‘Terminated’: terminating immediately
  make[4]: *** [Makefile:750: check-am] Terminated
  make: *** [debian/rules:7: build-arch] Terminated
  make[1]: [debian/rules:60: override_dh_auto_test] Terminated (ignored)
  Build killed with signal TERM after 150 minutes of inactivity

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

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

[Desktop-packages] [Bug 183366] Re: Bit Torrent T-0.3.13 (BitTornado) crashes when encountering Japanese character

[Bug Watch Updater]

** Changed in: bittornado (Debian)
   Status: New => Fix Released

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

Title:
  Bit Torrent T-0.3.13 (BitTornado) crashes when encountering Japanese
  character

Status in bittornado package in Ubuntu:
  Confirmed
Status in bittornado package in Debian:
  Fix Released

Bug description:
  Binary package hint: bittornado

  BitTorrent T-0.3.13 (BitTornado)
  OS: linux2
  Python version: 2.4.3 (#2, Oct  6 2006, 07:52:30) 
  [GCC 4.0.3 (Ubuntu 4.0.3-1ubuntu5)]
  wxWindows version: 2.6.1.2pre

  Traceback (most recent call last):
File "/usr/bin/btdownloadgui", line 476, in onInvoke
  apply(event.func, event.args, event.kwargs)
File "/usr/bin/btdownloadgui", line 2019, in onChooseFile
  if d2 == default:
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xa1 in position 0: 
ordinal not in range(128)

  BitTornado and Bittorrent read .torrent file but does not see
  :pathl32: or :path.utf8: to choose which file information according to
  locale (utf32-like or utf8). instead, assumes utf8 western europe.

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

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

[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes

[Ben Bromley]

I also hit Fn-A, which I saw somewhere (sorry to not have the link) that
would disable adaptive brightness.

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

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

Bug description:
  Hello,

  I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu
  edition from Dell which came with 18.04, but I've since wiped it and
  installed 19.04 from a fresh ISO download. This is the non-touch non-
  4K version (13-inch 1080p).

  Every so often (maybe a couple of times per minute), the screen
  flashes brighter, as if the brightness has been turned up momentarily
  and then back down again.

  I previously had an issue with the brightness / colours changing
  slightly when I opened menus or if the screen content changed
  slightly, but I fixed that by disabling Dynamic Brightness in the
  BIOS. It is definitely a better experience with that turned off.

  However the screen flashing still persists.

  I booted a live image of Fedora 30 now that it has been released, and
  so far I have not seen the screen flashing, so I do not think the
  hardware is faulty.

  I ran apport-bug, so hopefully the collected information has been
  attached.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  5 15:59:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2019-04-28 (6 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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-settings-daemon/+bug/1827790/+subscriptions

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

[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes

[Ben Bromley]

Alright, here we go.

I have the kernel listed above installed: Linux shadeball
5.2.0-9-generic #10~bfo110511 SMP Tue Jul 16 13:17:28 CST 2019 x86_64
x86_64 x86_64 GNU/Linux

I then went into the Power settings and turned Dim Screen When Inactive
to off, Blank Screen to Never and so far there have been basically no
flickers. There may have been one or two, but I can't confirm that I saw
them and cannot reproduce them.

I have tried it both on AC power and on battery, and with success on
both.

Thank you so much!

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

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

Bug description:
  Hello,

  I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu
  edition from Dell which came with 18.04, but I've since wiped it and
  installed 19.04 from a fresh ISO download. This is the non-touch non-
  4K version (13-inch 1080p).

  Every so often (maybe a couple of times per minute), the screen
  flashes brighter, as if the brightness has been turned up momentarily
  and then back down again.

  I previously had an issue with the brightness / colours changing
  slightly when I opened menus or if the screen content changed
  slightly, but I fixed that by disabling Dynamic Brightness in the
  BIOS. It is definitely a better experience with that turned off.

  However the screen flashing still persists.

  I booted a live image of Fedora 30 now that it has been released, and
  so far I have not seen the screen flashing, so I do not think the
  hardware is faulty.

  I ran apport-bug, so hopefully the collected information has been
  attached.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  5 15:59:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2019-04-28 (6 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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-settings-daemon/+bug/1827790/+subscriptions

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

[Desktop-packages] [Bug 1743247] Re: B2 Python APIs are missing

[Andrew Berry]

This bug report was originally against the PPA package
(0.7.16-0ubuntu1ppa1347~ubuntu16.04.1) and not those included in
Ubuntu's repositories.

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

Title:
  B2 Python APIs are missing

Status in Duplicity:
  Won't Fix
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  When I try to use the B2 backend with
  0.7.16-0ubuntu1ppa1347~ubuntu16.04.1, I get the following error:

  > BackendException: B2 backend requires B2 Python APIs (pip install
  b2)

  It seems odd to me that the library would be installed outside of apt.
  I had an old package from trusty
  (duplicity_0.7.14-0ubuntu0ppa1316~ubuntu14.04.1_amd64.deb) with 0.7.14
  which works fine on 16.04, which makes me think this regression was in
  0.7.15 or 0.7.16.

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

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

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

[Tom Reynolds]

** Tags added: disco

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

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

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

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

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

  journalctl output during the issue:

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

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

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

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

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

[Angel D. Segarra]

Getting this on 19.04

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

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

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

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

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

  journalctl output during the issue:

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

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

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

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

[Desktop-packages] [Bug 1623639] Re: netpbm: "anytopnm" doesn't recognize some file types

[Peter Selinger]

I second the request to fix this bug, no matter how old the software.
Because it is easy to fix and useful. I am attaching a patch.

** Patch added: "anytopnm.diff"
   
https://bugs.launchpad.net/ubuntu/+source/netpbm-free/+bug/1623639/+attachment/5289100/+files/anytopnm.diff

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

Title:
  netpbm: "anytopnm" doesn't recognize some file types

Status in netpbm-free package in Ubuntu:
  Confirmed

Bug description:
  /usr/bin/anytopnm uses the output of "file" to recognize the image format of 
the input file.
  Apparently the output of "file" has changed, and therefore it is no longer 
correctly recognized by anytopnm. Example:

  $ file /tmp/x.ppm
  /tmp/x.ppm: Netpbm image data, size = 5100 x 6600, rawbits, pixmap

  However, /usr/bin/anytopnm (line 64) looks for the strings *PBM* |
  *PGM* | *PPM* )

  For example:

  $ cat /tmp/x.ppm | anytopnm
  /usr/bin/anytopnm: unknown file type:  Netpbm image data, size = 5100 x 6600, 
rawbits, pixmap

  Suggested fix: update /usr/bin/anytopnm to recognize the string
  "Netpbm" in addition to PBM, PGM, PPM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netpbm-free/+bug/1623639/+subscriptions

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

[Desktop-packages] [Bug 87254] Re: bittornado / wxpython string decoding error

[Bug Watch Updater]

** Changed in: bittornado (Debian)
   Status: New => Fix Released

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

Title:
  bittornado / wxpython string decoding error

Status in bittornado package in Ubuntu:
  Confirmed
Status in bittornado package in Debian:
  Fix Released

Bug description:
  Binary package hint: bittornado

  Greetings

  The interaction between the choose-file dialog from wxpython and
  bittornado's btdownloadgui.py seems to have a bug.

  Some version information:

  bittornado: 0.3.15-2ubuntu1 (bug also confirmed on 0.3.17 from original 
provider)
  python-wxgtk2.6: 2.6.3.2.1.5
  libwxgtk2.6-0: 2.6.3.2.1.5

  How to reproduce:

  * Find a torrent that saves to a directory where the directory's name 
includes an umlauted 'U'. For instance, on mininova.org, search for "neubauten" 
and grab one of the umlauted Einsturzende Neubauten's torrents.
  * Open the torrent with btdownloadgui.bittornado.
  * Select your $HOME as target area for downloading

  ==> Error
  "UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 5: 
ordinal not in range (128)"

  The Traceback leads to line 2018, in on ChooseFile, 'if d2 == default'

  Other Information:

  default's type is a string, while d2, which comes from the Wx File
  Dialog, is a unicode object. I tried to get wxpython to use ascii
  encoding with wx.SetDefaultPyEncoding but only met exceptions, and
  tried to use wxversion to switch to wxpython in ascii mode, but that
  didn't help either.

  A Workaround:

  use --saveas $HOME to prevent the WX File Dialog interaction
  completely. However, this leads to strange windowing behavior; the
  titlebar of the main window has no text and nothing happens when you
  press on "Details". (should I submit another bug, or is this
  sufficient?)

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

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

Re: [Desktop-packages] [Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent

[Per-Inge]

Test case
Start Text Editor, Minimize and right click Text Editor in the Dock works
fine.

Den mån 16 sep. 2019 kl 17:50 skrev Launchpad Bug Tracker <
1843...@bugs.launchpad.net>:

> This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
> 66ubuntu19.10.2
>
> ---
> gnome-shell-extension-ubuntu-dock (66ubuntu19.10.2) eoan; urgency=medium
>
>   [ Marco Trevisan (Treviño) ]
>   * windowPreview: Use the window actor as Clone source (LP: #1843520)
>   * appIcons: Don't warn if variable is undefined
>   * appIcons: Enable scroll handler if enabled on construction
>   * docking: Don't warn if variable is undefined
>   * ubuntu-gschema.override: Enable fixed transparency with opacity at 70%
>
>  -- Marco Trevisan (Treviño)   Mon, 16 Sep 2019
> 14:28:09 +0200
>
> ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
>Status: In Progress => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1843520
>
> Title:
>   ubuntu-dock right-click menu appears at the top-left corner of the
>   desktop (which in some cases is the wrong monitor) and is permanent
>
> Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
>   Fix Released
>
> Bug description:
>   Very recently the ubuntu-dock has started displaying some right-click
>   menus for pinned apps on the wrong monitor. It doesn't happen for all
>   the apps, but when it does, the menu is permanent but you can't click
>   on it and you have to restart gnome-shell with ALT-F2 'r' (which now
>   always kills some apps like firefox).
>
>   See attached screenshot where the menu for gnome-tweaks has appeared
>   at the top left of the top monitor.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.1
>   Uname: Linux 5.3.0-050300rc8-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu7
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Sep 11 11:42:07 2019
>   InstallationDate: Installed on 2019-07-01 (71 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
>   PackageArchitecture: all
>   SourcePackage: gnome-shell-extension-ubuntu-dock
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1843520/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  ubuntu-dock right-click menu appears at the top-left corner of the
  desktop (which in some cases is the wrong monitor) and is permanent

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  Very recently the ubuntu-dock has started displaying some right-click
  menus for pinned apps on the wrong monitor. It doesn't happen for all
  the apps, but when it does, the menu is permanent but you can't click
  on it and you have to restart gnome-shell with ALT-F2 'r' (which now
  always kills some apps like firefox).

  See attached screenshot where the menu for gnome-tweaks has appeared
  at the top left of the top monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.1
  Uname: Linux 5.3.0-050300rc8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 11:42:07 2019
  InstallationDate: Installed on 2019-07-01 (71 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 332646] Re: sftp does not set timestamps

[Michael Dooley]

I note that this issue does not exist in Ubuntu-MATE 19.10 alpha
(September 16, 2019) using gvfs 1.42.0-1ubuntu1 and Caja to SFTP both to
and from a server. Files can be copied without changing their
timestamps.

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

Title:
  sftp does not set timestamps

Status in gvfs:
  Expired
Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gvfs

  when copying or moving files to a directory mounted over sftp, the
  time stamps are not preserved.

  this affects both hardy and intrepid (in hardy, it was tested with a
  patched version of nautilus hence that version used to forget
  timestamps on copy anyway). in both cases, i tested it locally and
  everything was preserved as it should be.

  moreover, when moving, nautilus first displays the correct time stamp
  and only on refreshing shows the wrong updated one.

  as timestamps can be considered considered important information, i
  suggest this bug be treated as "losing data without notice".

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

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

[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector

[Russ Dill]

This is really frustrating and 19.10 is coming up fast which I
understand will switch everyone over to snap based chromium making
extensions.gnome.org unusable for everyone. Any chance of switching back
to non-snap based chromium if this issue isn't resolved before then?

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

Title:
  [snap] chrome-gnome-shell extension fails to detect native host
  connector

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chrome-gnome-
  shell-does-not-work-with-chromium-snap/3377)

  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+subscriptions

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

[Desktop-packages] [Bug 1843952] Re: Artifacts appear when I un-maximize Chromium or Firefox windows [Intel N3350]

[Artyom Pozharov]

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

Daniel, I think it isn't duplicate of other bug, because this problem
with Firefox or Chromium appears only with Wayland session. And it is
not windows flickering to black when resizing.

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

Title:
  Artifacts appear when I un-maximize Chromium or Firefox windows [Intel
  N3350]

Status in mutter package in Ubuntu:
  New

Bug description:
  It's GNOME on Wayland bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: mutter 3.34.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 00:13:57 2019
  InstallationDate: Installed on 2019-09-09 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1813471] Re: Thunderbird crashes with GTK_USE_PORTAL environment variable.

[Bug Watch Updater]

** Changed in: thunderbird
   Status: Confirmed => Fix Released

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

Title:
  Thunderbird crashes with GTK_USE_PORTAL environment variable.

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Crash happens at startup, even for a new profile, as long as any
  e-mail accounts are configured.

  In profile creation mode, the crash happens as soon as an e-mail
  account is added.

  If all e-mail accounts are removed from prefs.js, then Thunderbird
  doesn't crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2619 F pulseaudio
   /dev/snd/controlC0:  vectro 2619 F pulseaudio
  BuildID: 20190116085154
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jan 27 06:55:37 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-23 (309 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 172.20.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600
  MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "60.4.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=60.4.0/20190116085154
   Profile1 - LastVersion=60.4.0/20190116085154
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1813471]

[Y-benjamin]

So it seems this has been in the code a LONG time. So if it is a
regression I haven't found it yet. I still find it odd that Firefox
doesn't suffer from the same issue given we share so much of the code
base.

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

Title:
  Thunderbird crashes with GTK_USE_PORTAL environment variable.

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Crash happens at startup, even for a new profile, as long as any
  e-mail accounts are configured.

  In profile creation mode, the crash happens as soon as an e-mail
  account is added.

  If all e-mail accounts are removed from prefs.js, then Thunderbird
  doesn't crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2619 F pulseaudio
   /dev/snd/controlC0:  vectro 2619 F pulseaudio
  BuildID: 20190116085154
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jan 27 06:55:37 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-23 (309 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 172.20.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600
  MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "60.4.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=60.4.0/20190116085154
   Profile1 - LastVersion=60.4.0/20190116085154
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1813471]

[Murz]

Seems fixed, `GTK_USE_PORTAL=1 thunderbird` goes to work well on Ubuntu 19.04 
with `thunderbird-mozilla-build_68.0-0ubuntu1_amd64.deb`!
With `thunderbird-mozilla-build_60.8.0-0ubuntu1_amd64.deb` now there are no 
crash, but dialog is still GTK.
Can any of other subscribers confirm, that this is fixed too?

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

Title:
  Thunderbird crashes with GTK_USE_PORTAL environment variable.

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Crash happens at startup, even for a new profile, as long as any
  e-mail accounts are configured.

  In profile creation mode, the crash happens as soon as an e-mail
  account is added.

  If all e-mail accounts are removed from prefs.js, then Thunderbird
  doesn't crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2619 F pulseaudio
   /dev/snd/controlC0:  vectro 2619 F pulseaudio
  BuildID: 20190116085154
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jan 27 06:55:37 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-23 (309 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 172.20.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600
  MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "60.4.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=60.4.0/20190116085154
   Profile1 - LastVersion=60.4.0/20190116085154
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1813471]

[Pulsebot]

Pushed by mozi...@jorgk.com:
https://hg.mozilla.org/comm-central/rev/aa6de4b5b0db
fix Thunderbird startup crash when GTK_USE_PORTAL=1 is set. r=jorgk

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

Title:
  Thunderbird crashes with GTK_USE_PORTAL environment variable.

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Crash happens at startup, even for a new profile, as long as any
  e-mail accounts are configured.

  In profile creation mode, the crash happens as soon as an e-mail
  account is added.

  If all e-mail accounts are removed from prefs.js, then Thunderbird
  doesn't crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2619 F pulseaudio
   /dev/snd/controlC0:  vectro 2619 F pulseaudio
  BuildID: 20190116085154
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jan 27 06:55:37 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-23 (309 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 172.20.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600
  MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "60.4.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=60.4.0/20190116085154
   Profile1 - LastVersion=60.4.0/20190116085154
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1813471]

[Mkmelin+mozilla]

Comment on attachment 9091741
bug1514605_GTK_USE_PORTAL.patch

Shouldn't hurt.

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

Title:
  Thunderbird crashes with GTK_USE_PORTAL environment variable.

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Crash happens at startup, even for a new profile, as long as any
  e-mail accounts are configured.

  In profile creation mode, the crash happens as soon as an e-mail
  account is added.

  If all e-mail accounts are removed from prefs.js, then Thunderbird
  doesn't crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2619 F pulseaudio
   /dev/snd/controlC0:  vectro 2619 F pulseaudio
  BuildID: 20190116085154
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jan 27 06:55:37 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-23 (309 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 172.20.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600
  MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "60.4.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=60.4.0/20190116085154
   Profile1 - LastVersion=60.4.0/20190116085154
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1813471]

[Jorg K]

TB 68.1.1 or TB 68.2:
https://hg.mozilla.org/releases/comm-esr68/rev/d741c4f6b95c5f3e063738d171b2fccea3695263

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

Title:
  Thunderbird crashes with GTK_USE_PORTAL environment variable.

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Crash happens at startup, even for a new profile, as long as any
  e-mail accounts are configured.

  In profile creation mode, the crash happens as soon as an e-mail
  account is added.

  If all e-mail accounts are removed from prefs.js, then Thunderbird
  doesn't crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2619 F pulseaudio
   /dev/snd/controlC0:  vectro 2619 F pulseaudio
  BuildID: 20190116085154
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jan 27 06:55:37 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-23 (309 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 172.20.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600
  MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "60.4.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=60.4.0/20190116085154
   Profile1 - LastVersion=60.4.0/20190116085154
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1740180]

[Simona-marcu]

Mozilla/5.0 (X11; Linux i686; rv:71.0) Gecko/20100101 Firefox/71.0 - Build ID: 
20190911215306.
This issues is still reproducible on the latest Nightly 71.0a1 on Ubuntu 16.04 
i686.

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

Title:
  Firefox stops loading Farmville 2 and hangs.

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

Bug description:
  STR: Start Firefox (56 or 57), go to Facebook. Start Farmville 2. 
   Farmville 2 hangs while loading. Never plays. 

  The Adobe Flash Player is properly installed. Has also been re-
  installed. Ditto for FireFox.

  Does not matter if using Ubuntu 16.04 or 17.10.

  Farmville 2 via Facebook in Firefox hangs. Also will not work if run
  from the Zynga URL (the makers of Farmville 2. Other Facebook games
  work well. Try "Pearl's Perils."

  Happy to help with testing if you like. This has been tested on both
  desktops and laptops.

  Thanks,

  Ken Wagner

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Dec 26 15:59:05 2017
  InstallationDate: Installed on 2017-03-06 (295 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ken2466 F pulseaudio
   /dev/snd/pcmC0D0p:   ken2466 F...m pulseaudio
   /dev/snd/controlC0:  ken2466 F pulseaudio
   /dev/snd/controlC2:  ken2466 F pulseaudio
  BuildID: 20180614184508
  Channel: beta
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-03-28 (94 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.0.1 dev enp2s0  proto static  metric 100 
   default via 192.168.1.1 dev wlx7cdd908b43ea  proto static  metric 600 
   169.254.0.0/16 dev wlx7cdd908b43ea  scope link  metric 1000 
   192.168.0.0/24 dev enp2s0  proto kernel  scope link  src 192.168.0.10  
metric 100 
   192.168.1.0/24 dev wlx7cdd908b43ea  proto kernel  scope link  src 
192.168.1.2  metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-61ed5f93-fc76-48cc-8c5e-05d080180530
  Package: firefox 61.0~b14+build1-0ubuntu0.16.04.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  PackageArchitecture: amd64
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
   prefs.js
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Profiles: Profile0 (Default) - LastVersion=61.0/20180614184508 (In use)
  RunningIncompatibleAddons: False
  SubmittedCrashIDs:
   bp-61ed5f93-fc76-48cc-8c5e-05d080180530
   bp-481cf9ec-efcd-4900-93aa-4e8940180512
   bp-ad49167e-7776-4ff5-8acc-5adb50180421
   bp-08f026d0-e273-45fb-b355-c70ae0180402
  Tags: xenial third-party-packages beta-channel
  Themes: extensions.sqlite corrupt or missing
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  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.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  --- 
  

[Desktop-packages] [Bug 1813471]

[Jorg K]

TB 70 beta 2:
https://hg.mozilla.org/releases/comm-beta/rev/366991cd4304a6d424f25a10d8899b83e2ae8469

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

Title:
  Thunderbird crashes with GTK_USE_PORTAL environment variable.

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Crash happens at startup, even for a new profile, as long as any
  e-mail accounts are configured.

  In profile creation mode, the crash happens as soon as an e-mail
  account is added.

  If all e-mail accounts are removed from prefs.js, then Thunderbird
  doesn't crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2619 F pulseaudio
   /dev/snd/controlC0:  vectro 2619 F pulseaudio
  BuildID: 20190116085154
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jan 27 06:55:37 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-23 (309 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 172.20.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600
  MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "60.4.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=60.4.0/20190116085154
   Profile1 - LastVersion=60.4.0/20190116085154
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1813471]

[Jorg K]

Comment on attachment 9091741
bug1514605_GTK_USE_PORTAL.patch

Typically for a QI, a bad status and returning null are synonymous. I
wouldn't check both, but there's no harm done.

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

Title:
  Thunderbird crashes with GTK_USE_PORTAL environment variable.

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Crash happens at startup, even for a new profile, as long as any
  e-mail accounts are configured.

  In profile creation mode, the crash happens as soon as an e-mail
  account is added.

  If all e-mail accounts are removed from prefs.js, then Thunderbird
  doesn't crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2619 F pulseaudio
   /dev/snd/controlC0:  vectro 2619 F pulseaudio
  BuildID: 20190116085154
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jan 27 06:55:37 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-23 (309 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 172.20.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600
  MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "60.4.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=60.4.0/20190116085154
   Profile1 - LastVersion=60.4.0/20190116085154
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1813471]

[Mkmelin+mozilla]

Created attachment 9091741
bug1514605_GTK_USE_PORTAL.patch

Can't reproduce at least on trunk. But if the crash report numbers are
correct, this would be the issue.

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

Title:
  Thunderbird crashes with GTK_USE_PORTAL environment variable.

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Crash happens at startup, even for a new profile, as long as any
  e-mail accounts are configured.

  In profile creation mode, the crash happens as soon as an e-mail
  account is added.

  If all e-mail accounts are removed from prefs.js, then Thunderbird
  doesn't crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2619 F pulseaudio
   /dev/snd/controlC0:  vectro 2619 F pulseaudio
  BuildID: 20190116085154
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jan 27 06:55:37 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-23 (309 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 172.20.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600
  MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "60.4.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=60.4.0/20190116085154
   Profile1 - LastVersion=60.4.0/20190116085154
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME

[Malte Deiseroth]

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

I also have nvidia-430 and am affected by this bug. However judging from
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859 this
is sadly just one more bug on the pile of wont-fix.

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

Title:
  Resuming from sleep breaks desktop and lock screen background in GNOME

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  CPU: AMD Ryzen 5 1600
  MOBO: MSI B350M MORTAR
  GPU: NVIDIA GTX 1060

  Ubuntu version: 19.04
  Nvidia driver version: 418.56

  
  The system is updated with the latest updates as today, 28 March 2019

  As the title says, in Ubuntu 19.04 the GNOME lockscreen gets
  corrupted, and the GNOME desktop has blank background after resuming
  from standby/sleep

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

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

[Desktop-packages] [Bug 1844170] [NEW] software page not updated after new search in Activities

[Yoann P]

Public bug reported:


1) Open Activities (windows key)
2) Search for an app not installed, i.e foobar2000
3) click on the result for ubuntu software
--> gnome-software opens on the foobar2000 page
4) Open Activities again
5) Search for another app, i.e. spotify
6) click on the result for ubuntu software
--> gnome software page does not change, still shows foobar2000 -> bug!

tried times and times with different apps, bug is really here.
I noticed this bug when I mistakenly installed an app that I previously 
searched for...

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.10
ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 16 18:58:09 2019
InstallationDate: Installed on 2019-09-15 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.10
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  software page not updated after new search in Activities

Status in gnome-software package in Ubuntu:
  New

Bug description:
  
  1) Open Activities (windows key)
  2) Search for an app not installed, i.e foobar2000
  3) click on the result for ubuntu software
  --> gnome-software opens on the foobar2000 page
  4) Open Activities again
  5) Search for another app, i.e. spotify
  6) click on the result for ubuntu software
  --> gnome software page does not change, still shows foobar2000 -> bug!

  tried times and times with different apps, bug is really here.
  I noticed this bug when I mistakenly installed an app that I previously 
searched for...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.10
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 16 18:58:09 2019
  InstallationDate: Installed on 2019-09-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.10
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1806697] Re: Status of interface connections not properly updated in the UI

[Efthimios Chaskaris]

Fix release for disco when?

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

Title:
  Status of interface connections not properly updated in the UI

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Fix Committed
Status in gnome-software source package in Eoan:
  Fix Released

Bug description:
  Steps to reproduce the problem:
  1. Go to the Chromium snap store page by e.g. right clicking on its icon and 
selecting Show details and then the specific app.
  2. Press the Permissions button.
  3. Press/slide the Read/write files on removable storage devices slider.
  4. Close the permissions and the store window.
  5. Reopen the windows.
  6. The permission should be enabled, but it isn't.

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

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

[Desktop-packages] [Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
66ubuntu19.10.2

---
gnome-shell-extension-ubuntu-dock (66ubuntu19.10.2) eoan; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * windowPreview: Use the window actor as Clone source (LP: #1843520)
  * appIcons: Don't warn if variable is undefined
  * appIcons: Enable scroll handler if enabled on construction
  * docking: Don't warn if variable is undefined
  * ubuntu-gschema.override: Enable fixed transparency with opacity at 70%

 -- Marco Trevisan (Treviño)   Mon, 16 Sep 2019
14:28:09 +0200

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  ubuntu-dock right-click menu appears at the top-left corner of the
  desktop (which in some cases is the wrong monitor) and is permanent

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  Very recently the ubuntu-dock has started displaying some right-click
  menus for pinned apps on the wrong monitor. It doesn't happen for all
  the apps, but when it does, the menu is permanent but you can't click
  on it and you have to restart gnome-shell with ALT-F2 'r' (which now
  always kills some apps like firefox).

  See attached screenshot where the menu for gnome-tweaks has appeared
  at the top left of the top monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.1
  Uname: Linux 5.3.0-050300rc8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 11:42:07 2019
  InstallationDate: Installed on 2019-07-01 (71 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1806697] Re: Status of interface connections not properly updated in the UI

[Robert Ancell]

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

Title:
  Status of interface connections not properly updated in the UI

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Fix Committed
Status in gnome-software source package in Eoan:
  Fix Released

Bug description:
  Steps to reproduce the problem:
  1. Go to the Chromium snap store page by e.g. right clicking on its icon and 
selecting Show details and then the specific app.
  2. Press the Permissions button.
  3. Press/slide the Read/write files on removable storage devices slider.
  4. Close the permissions and the store window.
  5. Reopen the windows.
  6. The permission should be enabled, but it isn't.

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

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

[Desktop-packages] [Bug 1844158] [NEW] FTBFS using vala-0.46.1

[Rex Dieter]

Public bug reported:

Trying to build on/for fedora 31+ fails with the following errors:

make[2]: Entering directory '/builddir/build/BUILD/libunity-7.1.4/src'
/usr/bin/valac -C -H unity.h -d . --gir=Unity-7.0.gir --library unity 
--internal-vapi=unity-internal.vapi --internal-header=unity-internal.h 
--target-glib=2.32 --thread --use-header --vapidir ../vapi --vapidir 
../protocol --vapidir . --pkg unity-protocol --pkg config --pkg unity-trace 
--pkg glib-2.0 --pkg gmodule-2.0 --pkg gobject-2.0 --pkg gio-2.0 --pkg 
gio-unix-2.0 --pkg dee-1.0 --pkg Dbusmenu-0.4  unity-appinfo-manager.vala 
unity-icon.vala unity-inspector.vala unity-io.vala unity-launcher.vala 
unity-category.vala unity-filters.vala unity-preferences-manager.vala 
unity-merge-strategy.vala unity-models.vala unity-search.vala 
unity-synchronizer.vala unity-previews.vala unity-result-activation.vala 
unity-scope-interface.vala unity-scope-dbus-connector.vala 
unity-scope-dbus-impl.vala unity-scope-channel.vala unity-deprecated-scope.vala 
unity-deprecated-scope-impl.vala unity-aggregator-scope.vala 
unity-aggregator-scope-private.vala unity-master-scope.vala 
unity-simple-scope.vala unity-scope-loader.vala unity-scope-tracker.vala 
unity-sound-menu.vala unity-sound-menu-mpris.vala unity-utils.vala
Command-line option `--thread` is deprecated and will be ignored
Compilation failed: 2 error(s), 0 warning(s)
BUILDSTDERR: unity-deprecated-scope.vala:64.3-64.28: error: Creation method of 
abstract class cannot be public.
BUILDSTDERR:   public DeprecatedScopeBase (string dbus_path_, string id_)
BUILDSTDERR:   ^^
BUILDSTDERR: unity-aggregator-scope.vala:54.3-54.24: error: Creation method of 
abstract class cannot be public.
BUILDSTDERR:   public AggregatorScope (string dbus_path_, string id_, MergeMode 
merge_mode = AggregatorScope.MergeMode.OWNER_SCOPE, bool proxy_filter_hints = 
false)
BUILDSTDERR:   ^^
BUILDSTDERR: make[2]: *** [Makefile:1389: libunity_la_vala.stamp] Error 1

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

** Affects: libunity (Fedora)
 Importance: Unknown
 Status: Unknown

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

** Also affects: libunity via
   https://bugzilla.redhat.com/show_bug.cgi?id=1736053
   Importance: Unknown
   Status: Unknown

** Also affects: libunity (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1736053
   Importance: Unknown
   Status: Unknown

** No longer affects: libunity

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

Title:
  FTBFS using vala-0.46.1

Status in libunity package in Ubuntu:
  New
Status in libunity package in Fedora:
  Unknown

Bug description:
  Trying to build on/for fedora 31+ fails with the following errors:

  make[2]: Entering directory '/builddir/build/BUILD/libunity-7.1.4/src'
  /usr/bin/valac -C -H unity.h -d . --gir=Unity-7.0.gir --library unity 
--internal-vapi=unity-internal.vapi --internal-header=unity-internal.h 
--target-glib=2.32 --thread --use-header --vapidir ../vapi --vapidir 
../protocol --vapidir . --pkg unity-protocol --pkg config --pkg unity-trace 
--pkg glib-2.0 --pkg gmodule-2.0 --pkg gobject-2.0 --pkg gio-2.0 --pkg 
gio-unix-2.0 --pkg dee-1.0 --pkg Dbusmenu-0.4  unity-appinfo-manager.vala 
unity-icon.vala unity-inspector.vala unity-io.vala unity-launcher.vala 
unity-category.vala unity-filters.vala unity-preferences-manager.vala 
unity-merge-strategy.vala unity-models.vala unity-search.vala 
unity-synchronizer.vala unity-previews.vala unity-result-activation.vala 
unity-scope-interface.vala unity-scope-dbus-connector.vala 
unity-scope-dbus-impl.vala unity-scope-channel.vala unity-deprecated-scope.vala 
unity-deprecated-scope-impl.vala unity-aggregator-scope.vala 
unity-aggregator-scope-private.vala unity-master-scope.vala 
unity-simple-scope.vala unity-scope-loader.vala unity-scope-tracker.vala 
unity-sound-menu.vala unity-sound-menu-mpris.vala unity-utils.vala
  Command-line option `--thread` is deprecated and will be ignored
  Compilation failed: 2 error(s), 0 warning(s)
  BUILDSTDERR: unity-deprecated-scope.vala:64.3-64.28: error: Creation method 
of abstract class cannot be public.
  BUILDSTDERR:   public DeprecatedScopeBase (string dbus_path_, string id_)
  BUILDSTDERR:   ^^
  BUILDSTDERR: unity-aggregator-scope.vala:54.3-54.24: error: Creation method 
of abstract class cannot be public.
  BUILDSTDERR:   public AggregatorScope (string dbus_path_, string id_, 
MergeMode merge_mode = AggregatorScope.MergeMode.OWNER_SCOPE, bool 
proxy_filter_hints = false)
  BUILDSTDERR:   ^^
  BUILDSTDERR: make[2]: *** [Makefile:1389: libunity_la_vala.stamp] Error 1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1818920] Re: Snap without icons use old asset

[Robert Ancell]

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Snap without icons use old asset

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  GNOME Software uses an outdated icon for snaps without icons.

  [Test Case]
  1. Open GNOME Software
  2. Look for a snap that has a default icon (e.g. youtube-dl)

  Expected behaviour:
  - The new icon is shown (grey circle with lines)

  Observed behaviour:
  - The old icon is shown (grey origami bird snapcraft logo)

  [Regression Potential]
  Low, this is just an asset change.

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

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

[Desktop-packages] [Bug 1785629] Re: [MIR] gupnp-av

[Sebastien Bacher]

** Changed in: gupnp-av (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] gupnp-av

Status in gupnp-av package in Ubuntu:
  Fix Released

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on rygel which depends on the gupnp
  libraries, including the gupnp-dlna one

  * Security

  No CVE/known security issue

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is not being used during build, we are going 
to look at changing that

  * Dependendies

  The package uses standard desktop libraries that are already in main
  (gstreamer, glib)

  * Standards compliance

  the package is using standard packaging (dh10), the standards-version
  is 3.9.8, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gupnp-av/+bug/1785629/+subscriptions

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

[Desktop-packages] [Bug 1785649] Re: [MIR] gupnp-dlna

[Sebastien Bacher]

** Changed in: gupnp-dlna (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] gupnp-dlna

Status in gupnp-dlna package in Ubuntu:
  Fix Released

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on rygel which depends on the gupnp
  libraries, including the gupnp-dlna one

  * Security

  No CVE/known security issue

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is not being used during build, we are going 
to look at changing that

  * Dependendies

  The package uses standard desktop libraries that are already in main
  (gstreamer, glib)

  * Standards compliance

  the package is using standard packaging (dh10), the standards-version
  is 3.9.8, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gupnp-dlna/+bug/1785649/+subscriptions

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

[Desktop-packages] [Bug 1836826] Re: Snaps not showing in categories due to store section name changes

[Robert Ancell]

** No longer affects: gnome-software (Ubuntu Xenial)

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

Title:
  Snaps not showing in categories due to store section name changes

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Disco:
  Fix Committed
Status in gnome-software source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  The Snap Store changed the names of some of the sections. This means that 
these are no longer mapped to the XDG categories used in GNOME Software. See 
https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/279

  [Test Case]
  1. Open GNOME Software
  2. Go to graphics categeory.

  Expected result:
  Snaps are shown

  Observer result:
  Only .debs are shown

  [Regression Potential]
  Fix is just to change the name mappings, should be low risk.

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

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

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

[Maxim Smih]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1842865/+attachment/5289034/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in gvfs:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I turn off the computer, it hangs on the logo. The light on the
  system unit continues to light. Does not respond to the keyboard.
  Kernel version 5.0.0-27. Here is the error:

  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  5 09:44:35 2019
  InstallationDate: Installed on 2019-08-09 (26 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1055 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-09 (37 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp0s25   no wireless extensions.
   
   enp7s4no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc5800 Microtower
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board.asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5800 Microtower
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[Maxim Smih]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1842865/+attachment/5289033/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in gvfs:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I turn off the computer, it hangs on the logo. The light on the
  system unit continues to light. Does not respond to the keyboard.
  Kernel version 5.0.0-27. Here is the error:

  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  5 09:44:35 2019
  InstallationDate: Installed on 2019-08-09 (26 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1055 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-09 (37 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp0s25   no wireless extensions.
   
   enp7s4no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc5800 Microtower
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board.asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5800 Microtower
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[Maxim Smih]

apport information

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in gvfs:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I turn off the computer, it hangs on the logo. The light on the
  system unit continues to light. Does not respond to the keyboard.
  Kernel version 5.0.0-27. Here is the error:

  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  5 09:44:35 2019
  InstallationDate: Installed on 2019-08-09 (26 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1055 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-09 (37 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp0s25   no wireless extensions.
   
   enp7s4no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc5800 Microtower
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board.asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5800 Microtower
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[Maxim Smih]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1842865/+attachment/5289038/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in gvfs:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I turn off the computer, it hangs on the logo. The light on the
  system unit continues to light. Does not respond to the keyboard.
  Kernel version 5.0.0-27. Here is the error:

  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  5 09:44:35 2019
  InstallationDate: Installed on 2019-08-09 (26 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1055 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-09 (37 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp0s25   no wireless extensions.
   
   enp7s4no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc5800 Microtower
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board.asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5800 Microtower
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[Maxim Smih]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1842865/+attachment/5289041/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in gvfs:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I turn off the computer, it hangs on the logo. The light on the
  system unit continues to light. Does not respond to the keyboard.
  Kernel version 5.0.0-27. Here is the error:

  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  5 09:44:35 2019
  InstallationDate: Installed on 2019-08-09 (26 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1055 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-09 (37 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp0s25   no wireless extensions.
   
   enp7s4no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc5800 Microtower
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board.asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5800 Microtower
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[Maxim Smih]

apport information

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in gvfs:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I turn off the computer, it hangs on the logo. The light on the
  system unit continues to light. Does not respond to the keyboard.
  Kernel version 5.0.0-27. Here is the error:

  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  5 09:44:35 2019
  InstallationDate: Installed on 2019-08-09 (26 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1055 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-09 (37 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp0s25   no wireless extensions.
   
   enp7s4no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc5800 Microtower
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board.asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5800 Microtower
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1842865] PulseList.txt

[Maxim Smih]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1842865/+attachment/5289040/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in gvfs:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I turn off the computer, it hangs on the logo. The light on the
  system unit continues to light. Does not respond to the keyboard.
  Kernel version 5.0.0-27. Here is the error:

  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  5 09:44:35 2019
  InstallationDate: Installed on 2019-08-09 (26 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1055 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-09 (37 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp0s25   no wireless extensions.
   
   enp7s4no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc5800 Microtower
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board.asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5800 Microtower
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1842865] WifiSyslog.txt

[Maxim Smih]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1842865/+attachment/5289042/+files/WifiSyslog.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in gvfs:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I turn off the computer, it hangs on the logo. The light on the
  system unit continues to light. Does not respond to the keyboard.
  Kernel version 5.0.0-27. Here is the error:

  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  5 09:44:35 2019
  InstallationDate: Installed on 2019-08-09 (26 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1055 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-09 (37 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp0s25   no wireless extensions.
   
   enp7s4no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc5800 Microtower
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board.asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5800 Microtower
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[Maxim Smih]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1842865/+attachment/5289039/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in gvfs:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I turn off the computer, it hangs on the logo. The light on the
  system unit continues to light. Does not respond to the keyboard.
  Kernel version 5.0.0-27. Here is the error:

  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  5 09:44:35 2019
  InstallationDate: Installed on 2019-08-09 (26 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1055 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-09 (37 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp0s25   no wireless extensions.
   
   enp7s4no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc5800 Microtower
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board.asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5800 Microtower
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[Maxim Smih]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1842865/+attachment/5289035/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in gvfs:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I turn off the computer, it hangs on the logo. The light on the
  system unit continues to light. Does not respond to the keyboard.
  Kernel version 5.0.0-27. Here is the error:

  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  5 09:44:35 2019
  InstallationDate: Installed on 2019-08-09 (26 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1055 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-09 (37 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp0s25   no wireless extensions.
   
   enp7s4no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc5800 Microtower
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board.asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5800 Microtower
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1842865] CRDA.txt

[Maxim Smih]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1842865/+attachment/5289031/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in gvfs:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I turn off the computer, it hangs on the logo. The light on the
  system unit continues to light. Does not respond to the keyboard.
  Kernel version 5.0.0-27. Here is the error:

  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  5 09:44:35 2019
  InstallationDate: Installed on 2019-08-09 (26 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1055 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-09 (37 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp0s25   no wireless extensions.
   
   enp7s4no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc5800 Microtower
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board.asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5800 Microtower
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1843982] Re: gnome-shell crashed with SIGSEGV in g_str_hash()

[Gunnar Hjalmarsson]

** Information type changed from Private to Public

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

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

Status in accountsservice package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo

[Maxim Smih]

apport information

** Tags added: apport-collected

** Description changed:

  When I turn off the computer, it hangs on the logo. The light on the
  system unit continues to light. Does not respond to the keyboard. Kernel
  version 5.0.0-27. Here is the error:
  
  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message
  
  https://ibb.co/PcYvDLq
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  5 09:44:35 2019
  InstallationDate: Installed on 2019-08-09 (26 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.7
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  max1055 F pulseaudio
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2019-08-09 (37 days ago)
+ InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
+ IwConfig:
+  enp0s25   no wireless extensions.
+  
+  enp7s4no wireless extensions.
+  
+  lono wireless extensions.
+ MachineType: Hewlett-Packard HP Compaq dc5800 Microtower
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-62-generic N/A
+  linux-backports-modules-4.15.0-62-generic  N/A
+  linux-firmware 1.173.9
+ RfKill:
+  
+ Tags:  bionic
+ Uname: Linux 4.15.0-62-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 10/26/2015
+ dmi.bios.vendor: Hewlett-Packard
+ dmi.bios.version: 786F2 v01.60
+ dmi.board.asset.tag: CZC8107S1Y
+ dmi.board.name: 2820h
+ dmi.board.vendor: Hewlett-Packard
+ dmi.chassis.asset.tag: CZC8107S1Y
+ dmi.chassis.type: 6
+ dmi.chassis.vendor: Hewlett-Packard
+ dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr:
+ dmi.product.family: 103C_53307F
+ dmi.product.name: HP Compaq dc5800 Microtower
+ dmi.sys.vendor: Hewlett-Packard

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1842865/+attachment/5289030/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in gvfs:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I turn off the computer, it hangs on the logo. The light on the
  system unit continues to light. Does not respond to the keyboard.
  Kernel version 5.0.0-27. Here is the error:

  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  5 09:44:35 2019
  InstallationDate: Installed on 2019-08-09 (26 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1055 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-09 (37 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp0s25   no wireless extensions.
   
   enp7s4no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP Compaq 

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

[Maxim Smih]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1842865/+attachment/5289032/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in gvfs:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I turn off the computer, it hangs on the logo. The light on the
  system unit continues to light. Does not respond to the keyboard.
  Kernel version 5.0.0-27. Here is the error:

  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  5 09:44:35 2019
  InstallationDate: Installed on 2019-08-09 (26 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1055 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-09 (37 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   enp0s25   no wireless extensions.
   
   enp7s4no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc5800 Microtower
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board.asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5800 Microtower
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

[Alkis Georgopoulos]

Hi Timo,

if I remember correctly, there were some schools that were affected by this 
issue, but I wasn't able to reproduce it in the office due to lack of similar 
hardware.
Unfortunately it's not easy to check which were those schools; but I can keep 
an eye on this issue, in case I hear about black screens in the near future

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

Title:
  [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in mesa source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

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

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

[Desktop-packages] [Bug 1844067] Re: Merge ibus 1.5.21-1~exp2 (main) from Debian experimental (main)

[Gunnar Hjalmarsson]

Not uploaded yet, and I have added a security fix to the proposed upload
in the PPA.

As regards the test failures I submitted an upstream issue:

https://github.com/ibus/ibus/issues/2135

** Bug watch added: github.com/ibus/ibus/issues #2135
   https://github.com/ibus/ibus/issues/2135

** Changed in: ibus (Ubuntu)
   Status: Fix Committed => In Progress

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

Title:
  Merge ibus 1.5.21-1~exp2 (main) from Debian experimental (main)

Status in ibus package in Ubuntu:
  In Progress

Bug description:
  Upstream released ibus 1.5.21 on 2019-08-23, and it's available in
  Debian experimental. It would be good if this could make it into eoan,
  so a recent IBus version gets 'tested' in 19.10 as a preparation for
  next LTS.

  Please see  for an overview of
  the changes in 1.5.20 and 1.5.21. They are both micro releases and
  don't introduce new features.

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

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

[Desktop-packages] [Bug 1836826] Re: Snaps not showing in categories due to store section name changes

[Robert Ancell]

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

Title:
  Snaps not showing in categories due to store section name changes

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Disco:
  Fix Committed
Status in gnome-software source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  The Snap Store changed the names of some of the sections. This means that 
these are no longer mapped to the XDG categories used in GNOME Software. See 
https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/279

  [Test Case]
  1. Open GNOME Software
  2. Go to graphics categeory.

  Expected result:
  Snaps are shown

  Observer result:
  Only .debs are shown

  [Regression Potential]
  Fix is just to change the name mappings, should be low risk.

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

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

[Desktop-packages] [Bug 1844126] Re: Update NVIDIA the 430 series and introduce the 435 series

[Steve Langasek]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-430 into bionic-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-430/430.50-0ubuntu0.18.04.1 in a few hours, and
then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: nvidia-graphics-drivers-430 (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  Update NVIDIA the 430 series and introduce the 435 series

Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-435 source package in Bionic:
  In Progress

Bug description:
  Update NVIDIA the 430 series and introduce the 435 series from 19.10.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  
  [Discussion]

  430.50:

    * New upstream release (LP: #1844126):
  - Fixed display color range handling on pre-Turing GPUs, such
    that when limited color range is selected through the display
    controls page in nvidia-settings, output pixel values will be
    correctly clamped to Consumer Technology Association (CTA)
    range.

  435.21:

    * New upstream release:
  - Fixed a bug that caused the X server to crash when using
    HardDPMS with an NVIDIA-driven GPU Screen.
  - Fixed a bug which caused the kernel to panic when exiting a
    single X server when multiple X servers were active and in an
    SLI configuration.
  - Fixed a regression introduced in the 430.* series of releases
    that caused a segmentation fault in libnvcuvid.so while using
    Video Codec SDK APIs on certain graphics boards.
  - Added initial experimental support for runtime D3 (RTD3) power
    management on Turing notebook GPUs.
  - Improved nvidia-bug-report.sh to collect runtime D3 (RTD3)
    power management information.
  - Improved nvidia-bug-report.sh to collect ACPI tables when the
    acpidump tool is available.
  - Added Vulkan and OpenGL+GLX support for PRIME render offload.
    Please see the PRIME Render Offload chapter in the README for
    system requirements and configuration details.
  - Added support for changing Digital Vibrance in the display
    controls section of nvidia-settings on Turing hardware.
  - Fixed the cuvidParseVideoData API in the NVCUVID driver to
    correctly propagate errors returned by the
    PFNVIDSEQUENCECALLBACK callback function to the application.
  - Fixed a bug that caused the NVIDIA X driver to behave
    incorrectly or crash when a client queried Xinerama information
    on X servers with a non-NVIDIA X screen as screen 0.
  - Fixed the "Image Settings" options in the "OpenGL Settings"
    page of nvidia-settings for Quadro GPUs.  Previously, OpenGL
    

[Desktop-packages] [Bug 1844137] [NEW] Battery icon in top bar looks "red" when battery is not low

[Will Cooke]

Public bug reported:

In Ubuntu 19.10 the battery icon in the top bar looks red (actually it's
orange rgb(245,121,62)) even when the battery is full, e.g. 99%.

The orange colour makes it look like a warning that the battery is low.

Logged upstream: https://github.com/ubuntu/yaru/issues/1531

** Affects: yaru
 Importance: Unknown
 Status: Unknown

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


** Tags: rls-ee-incoming

** Bug watch added: github.com/ubuntu/yaru/issues #1531
   https://github.com/ubuntu/yaru/issues/1531

** Also affects: yaru via
   https://github.com/ubuntu/yaru/issues/1531
   Importance: Unknown
   Status: Unknown

** Tags added: rls-ee-incoming

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

Title:
  Battery icon in top bar looks "red" when battery is not low

Status in Yaru Theme:
  Unknown
Status in yaru-theme package in Ubuntu:
  New

Bug description:
  In Ubuntu 19.10 the battery icon in the top bar looks red (actually
  it's orange rgb(245,121,62)) even when the battery is full, e.g. 99%.

  The orange colour makes it look like a warning that the battery is
  low.

  Logged upstream: https://github.com/ubuntu/yaru/issues/1531

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

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

[Desktop-packages] [Bug 1844126] Re: Update NVIDIA the 430 series and introduce the 435 series

[Alberto Milone]

** Description changed:

  Update NVIDIA the 430 series and introduce the 435 series from 19.10.
  
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.
  
  See the changelog entry below for a full list of changes and bugs.
  
  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates
  
- 
+ Certification test suite must pass on a range of hardware:
+ https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
  
  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.
  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.
  
- 
- 
  
  [Discussion]
  
  430.50:
  
-   * New upstream release (LP: #1844126):
- - Fixed display color range handling on pre-Turing GPUs, such
-   that when limited color range is selected through the display
-   controls page in nvidia-settings, output pixel values will be
-   correctly clamped to Consumer Technology Association (CTA)
-   range.
+   * New upstream release (LP: #1844126):
+ - Fixed display color range handling on pre-Turing GPUs, such
+   that when limited color range is selected through the display
+   controls page in nvidia-settings, output pixel values will be
+   correctly clamped to Consumer Technology Association (CTA)
+   range.
  
  435.21:
-   

   
-   * New upstream release: 

   
- - Fixed a bug that caused the X server to crash when using

   
-   HardDPMS with an NVIDIA-driven GPU Screen.  

   
- - Fixed a bug which caused the kernel to panic when exiting a 

   
-   single X server when multiple X servers were active and in an   

   
-   SLI configuration.  

   
- - Fixed a regression introduced in the 430.* series of releases   

   
-   that caused a segmentation fault in libnvcuvid.so while using   

   
-   Video Codec SDK APIs on certain graphics boards.

   
- - Added initial experimental support for runtime D3 (RTD3) power  

   
-   management on Turing notebook GPUs. 

   
- - Improved nvidia-bug-report.sh to collect runtime D3 (RTD3)  

   
-   power management information.   

   
- - Improved nvidia-bug-report.sh to collect ACPI tables when the   

   
-   acpidump tool is available. 
  

[Desktop-packages] [Bug 1843999] Re: Printing fails since last update

[Adrian Midgley]

Removed and recreated printer.  No change.
Removed plugins - not Gutenprint of coure - no change.

Starting gimp in a terminal with --verbose leads to

Initializing plug-in: 
'/usr/lib/gimp/2.0/plug-ins/file-rawtherapee/file-rawtherapee'
Initializing plug-in: '/usr/lib/gimp/2.0/plug-ins/file-darktable/file-darktable'
Starting extension: 'extension-script-fu'
INIT: gui_restore_after_callback
Parsing '/home/akm/.config/GIMP/2.10/menurc'
Parsing '/home/akm/.config/GIMP/2.10/action-history'
Parsing '/home/akm/.config/GIMP/2.10/devicerc'
Parsing '/home/akm/.config/GIMP/2.10/controllerrc'
loading menu '/usr/share/gimp/2.0/menus/image-menu.xml' for /image-menubar
/usr/lib/gimp/2.0/plug-ins/gutenprint: fatal error: Segmentation fault

The last line is the one which appears after an effort to print.

I'm stuck so far.

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

Title:
  Printing fails since last update

Status in cups package in Ubuntu:
  New

Bug description:
  I use Gimp-gutenprint to print photographs via CUPS to an Epson R2400
  It fails each time, reporting filter failure.
  I forget what the last update was, yesterday or day before, but it is only 
since then.

  ESC/P utility can print a nozzle check from the printer, that's
  working.

  CUPS seems to be telling me that a filter failed, due to a mismatch
  between device colour model and profile.

  I've tried with no profile in the setup:printer dialogue, no
  different.

  Where should I look?
  Is it likely to be a change in the last update?

  
  I'm on 18.04 LTS on an AMD processor with multiple screens on an Nvidia card.


  W [14/Sep/2019:00:10:31 +0100] AddProfile failed:
  org.freedesktop.ColorManager.Device.ProfileAlreadyAdded:profile object
  path \'/org/freedesktop/ColorManager/profiles/Stylus_Photo_R2400_RGB__\'
  has already been added
  E [14/Sep/2019:00:13:12 +0100] [Job 347] Aborting job because it has no files.
  E [14/Sep/2019:00:22:11 +0100] [Job 348] Aborting job because it has no files.
  E [14/Sep/2019:00:29:51 +0100] [Job 350] Job stopped due to filter
  errors; please consult the error_log file for details.
  D [14/Sep/2019:00:29:51 +0100] [Job 350] The following messages were
  recorded from 00:29:51 to 00:29:51
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Applying default options...
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Adding start banner page "none".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Adding end banner page "none".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] File of type application/pdf
  queued by "akm".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] hold_until=0
  D [14/Sep/2019:00:29:51 +0100] [Job 350] Queued on
  "Stylus-Photo-R2400" by "akm".
  D [14/Sep/2019:00:29:51 +0100] [Job 350] time-at-processing=1568417391
  D [14/Sep/2019:00:29:51 +0100] [Job 350] 3 filters for job:
  D [14/Sep/2019:00:29:51 +0100] [Job 350] pdftopdf (application/pdf to
  application/vnd.cups-pdf, cost 66)
  D [14/Sep/2019:00:29:51 +0100] [Job 350] gstoraster
  (application/vnd.cups-pdf to application/vnd.cups-raster, cost 99)
  D [14/Sep/2019:00:29:51 +0100] [Job 350] rastertogutenprint.5.2
  (application/vnd.cups-raster to printer/Stylus-Photo-R2400, cost 100)
  D [14/Sep/2019:00:29:51 +0100] [Job 350] job-sheets=none,none
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[0]="Stylus-Photo-R2400"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[1]="350"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[2]="akm"
  D [14/Sep/2019:00:29:51 +0100] [Job 350]
  argv[3]="[8-channel-printer-a] (imported)"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[4]="1"
  D [14/Sep/2019:00:29:51 +0100] [Job 350] argv[5]="StpMagentaGamma=None
  StpFineMagentaBalance=None StpFineHGray5Trans=None StpPlatenGap=1
  ColorModel=Gray StpCyanBalance=None StpFineBlackGamma=None
  StpLightMagentaValue=None StpHGray4Scale=None StpBlackDensity=None
  StpMagentaDensity=None StpHGray3Value=None StpHGray1Trans=None
  StpFineLightCyanTrans=None StpInkLimit=None StpFineHGray4Trans=None
  StpColorCorrection=None StpLightMagentaScale=None
  Resolution=1444x720dpi StpHGray3Scale=None StpPrintMethod=None
  StpQuality=Best StpHGray2Value=None StpMagentaBalance=None
  StpFineGamma=None StpFineHGray5Value=None StpBandEnhancement=0
  StpBrightness=None StpFineHGray3Trans=None StpFineCyanGamma=None
  StpDropSize1=None StpDropSize2=None StpFineCyanDensity=None
  StpDropSize3=None StpHGray2Scale=None StpLightCyanTrans=None
  StpHGray1Value=None StpFineHGray5Scale=None StpFineLightCyanValue=None
  StpFineContrast=None StpFineHGray4Value=None StpFineBrightness=None
  StpFineYellowDensity=None StpFineHGray2Trans=None
  StpYellowDensity=None StpGamma=None StpFineCyanBalance=None
  StpFineBlackTrans=None StpFineLightCyanScale=None StpHGray1Scale=None
  StpFineHGray4Scale=None StpFineYellowBalance=None
  StpFineSubchannelCutoff=None StpFineHGray3Value=None StpFullBleed
  

[Desktop-packages] [Bug 1844136] [NEW] [eoan] Thunderbird 68.0 does not include attachment coming from an external app

[Francois Thirioux]

Public bug reported:

(Eoan up-to-date, GNOME session)

When I choose to "send to" my PDF or image from Eog or Evince (probably
others too), TB 68 new message window appears but no file is attached.
Same issue inside Nautilus (right-click on a file, send to).

Was fully ok with TB 60.* .

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


** Tags: eoan

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

Title:
  [eoan] Thunderbird 68.0 does not include attachment coming from an
  external app

Status in thunderbird package in Ubuntu:
  New

Bug description:
  (Eoan up-to-date, GNOME session)

  When I choose to "send to" my PDF or image from Eog or Evince
  (probably others too), TB 68 new message window appears but no file is
  attached. Same issue inside Nautilus (right-click on a file, send to).

  Was fully ok with TB 60.* .

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

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

[Desktop-packages] [Bug 1801540]

[jg.staffel]

(In reply to Takashi Iwai from comment #271)

(In reply to Takashi Iwai from comment #249)
> (In reply to al from comment #248)
> > Thanks that did it works great now!
> 
> OK, I'll add the entry for 1022:1487 in the upstream, too.

The patch was backported to the 4.19.67 kernel.

With this and latest Gentoo stable kernel 4.19.72 and net-im/telegram-
desktop-bin-1.8.8 my companion hear myself while audio call. No echo
cancellation.

ASRock Fatal1ty B450 Gaming K4
ALC892, [1022:1457] subsys [1849:9893]

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

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

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

[Desktop-packages] [Bug 1844130] Re: Preview not show when clicking on dock icon where 2 or more windows are open

[Launchpad Bug Tracker]

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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Confirmed

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

Title:
  Preview not show when clicking on dock icon where 2 or more windows
  are open

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

Bug description:
  Observed behaviour:
  In Eoan when clicking on an application icon on the dock where there are two 
or more windows doesn't open the preview.  This is how it worked in D for 
example.

  Expected behaviour:
  Click on an icon in the dock where two or more windows are open should open 
the preview showing the mini versions of the available windows.

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

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

[Desktop-packages] [Bug 1844130] Re: Preview not show when clicking on dock icon where 2 or more windows are open

[Daniel van Vugt]

I wonder if this is distantly related to bug 1843520...

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

Title:
  Preview not show when clicking on dock icon where 2 or more windows
  are open

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

Bug description:
  Observed behaviour:
  In Eoan when clicking on an application icon on the dock where there are two 
or more windows doesn't open the preview.  This is how it worked in D for 
example.

  Expected behaviour:
  Click on an icon in the dock where two or more windows are open should open 
the preview showing the mini versions of the available windows.

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

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

[Desktop-packages] [Bug 1844126] Re: Update NVIDIA the 430 series and introduce the 435 series

[Alberto Milone]

** Description changed:

  Update NVIDIA the 430 series and introduce the 435 series from 19.10.
+ 
+ [Impact]
+ These releases provide both bug fixes and new features, and we would like to
+ make sure all of our users have access to these improvements.
+ 
+ See the changelog entry below for a full list of changes and bugs.
+ 
+ [Test Case]
+ The following development and SRU process was followed:
+ https://wiki.ubuntu.com/NVidiaUpdates
+ 
+ 
+ 
+ The QA team that executed the tests will be in charge of attaching the
+ artifacts and console output of the appropriate run to the bug. nVidia
+ maintainers team members will not mark ‘verification-done’ until this
+ has happened.
+ 
+ [Regression Potential]
+ In order to mitigate the regression potential, the results of the
+ aforementioned system level tests are attached to this bug.
+ 
+ 
+ 
+ 
+ [Discussion]
+ 
+ 430.50:
+ 
+   * New upstream release (LP: #1844126):
+ - Fixed display color range handling on pre-Turing GPUs, such
+   that when limited color range is selected through the display
+   controls page in nvidia-settings, output pixel values will be
+   correctly clamped to Consumer Technology Association (CTA)
+   range.
+ 
+ 435.21:
+   

   
+   * New upstream release: 

   
+ - Fixed a bug that caused the X server to crash when using

   
+   HardDPMS with an NVIDIA-driven GPU Screen.  

   
+ - Fixed a bug which caused the kernel to panic when exiting a 

   
+   single X server when multiple X servers were active and in an   

   
+   SLI configuration.  

   
+ - Fixed a regression introduced in the 430.* series of releases   

   
+   that caused a segmentation fault in libnvcuvid.so while using   

   
+   Video Codec SDK APIs on certain graphics boards.

   
+ - Added initial experimental support for runtime D3 (RTD3) power  

   
+   management on Turing notebook GPUs. 

   
+ - Improved nvidia-bug-report.sh to collect runtime D3 (RTD3)  

   
+   power management information.   

   
+ - Improved nvidia-bug-report.sh to collect ACPI tables when the   

   
+   acpidump tool is available. 

   
+ - Added Vulkan and OpenGL+GLX support for PRIME render offload.   

   
+   Please see the PRIME Render Offload chapter in the README for   

[Desktop-packages] [Bug 1844130] Re: Preview not show when clicking on dock icon where 2 or more windows are open

[Daniel van Vugt]

** Tags added: eoan

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

Title:
  Preview not show when clicking on dock icon where 2 or more windows
  are open

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

Bug description:
  Observed behaviour:
  In Eoan when clicking on an application icon on the dock where there are two 
or more windows doesn't open the preview.  This is how it worked in D for 
example.

  Expected behaviour:
  Click on an icon in the dock where two or more windows are open should open 
the preview showing the mini versions of the available windows.

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

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

[Desktop-packages] [Bug 1841437] Re: Don't update to 1.3.5

[Sebastien Bacher]

** Tags removed: version-skip-1.3.5
** Tags added: version-blocked-ff

** Description changed:

- Debian is skipping this version  due to a license issue, waiting for
- 1.3.6
+ The new version is in Debian but includes new features, we would need a
+ ffe if you want to update

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

Title:
  Don't update to 1.3.5

Status in remmina package in Ubuntu:
  Triaged

Bug description:
  The new version is in Debian but includes new features, we would need
  a ffe if you want to update

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

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

[Desktop-packages] [Bug 1844132] Re: FFe: Mesa 19.2.0

[Timo Aaltonen]

packages for testing: ppa:canonical-x/x-staging

** Changed in: mesa (Ubuntu)
   Status: New => In Progress

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu)
   Status: In Progress => Confirmed

** Description changed:

  It would be great to get 19.2.0 in eoan, though it's release cycle has
  slipped. It's working fine on a typical desktop use here on i915 (Kaby
  Lake). It would also migrate to llvm-9.
  
  New features:
+ 
+ Support for AMD Navi
  
  GL_ARB_post_depth_coverage on radeonsi (Navi)
  GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports 
SEAMLESS_CUBE_MAP)
  GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10)
  GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR)
  GL_EXT_texture_shadow_lod on i965, iris
  EGL_EXT_platform_device
  VK_AMD_buffer_marker on radv
  VK_EXT_index_type_uint8 on radv
  VK_EXT_post_depth_coverage on radv
  VK_EXT_queue_family_foreign on radv
  VK_EXT_sample_locations on radv
  VK_EXT_shader_demote_to_helper_invocation on Intel.
  VK_KHR_depth_stencil_resolve on radv
  VK_KHR_imageless_framebuffer on radv
  VK_KHR_shader_atomic_int64 on radv
  VK_KHR_uniform_buffer_standard_layout on radv
  
  (note: iris is the new DRI driver for newer Intel, not enabled by
  default yet)

** Description changed:

  It would be great to get 19.2.0 in eoan, though it's release cycle has
  slipped. It's working fine on a typical desktop use here on i915 (Kaby
  Lake). It would also migrate to llvm-9.
+ 
+ It is currently at rc3, and final version is expected to arrive next
+ week (week 39).
  
  New features:
  
  Support for AMD Navi
  
  GL_ARB_post_depth_coverage on radeonsi (Navi)
  GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports 
SEAMLESS_CUBE_MAP)
  GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10)
  GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR)
  GL_EXT_texture_shadow_lod on i965, iris
  EGL_EXT_platform_device
  VK_AMD_buffer_marker on radv
  VK_EXT_index_type_uint8 on radv
  VK_EXT_post_depth_coverage on radv
  VK_EXT_queue_family_foreign on radv
  VK_EXT_sample_locations on radv
  VK_EXT_shader_demote_to_helper_invocation on Intel.
  VK_KHR_depth_stencil_resolve on radv
  VK_KHR_imageless_framebuffer on radv
  VK_KHR_shader_atomic_int64 on radv
  VK_KHR_uniform_buffer_standard_layout on radv
  
  (note: iris is the new DRI driver for newer Intel, not enabled by
  default yet)

** Also affects: mesa (Ubuntu Eoan)
   Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
   Status: Confirmed

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

Title:
  FFe: Mesa 19.2.0

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Eoan:
  Confirmed

Bug description:
  It would be great to get 19.2.0 in eoan, though it's release cycle has
  slipped. It's working fine on a typical desktop use here on i915 (Kaby
  Lake). It would also migrate to llvm-9.

  It is currently at rc3, and final version is expected to arrive next
  week (week 39).

  New features:

  Support for AMD Navi

  GL_ARB_post_depth_coverage on radeonsi (Navi)
  GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports 
SEAMLESS_CUBE_MAP)
  GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10)
  GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR)
  GL_EXT_texture_shadow_lod on i965, iris
  EGL_EXT_platform_device
  VK_AMD_buffer_marker on radv
  VK_EXT_index_type_uint8 on radv
  VK_EXT_post_depth_coverage on radv
  VK_EXT_queue_family_foreign on radv
  VK_EXT_sample_locations on radv
  VK_EXT_shader_demote_to_helper_invocation on Intel.
  VK_KHR_depth_stencil_resolve on radv
  VK_KHR_imageless_framebuffer on radv
  VK_KHR_shader_atomic_int64 on radv
  VK_KHR_uniform_buffer_standard_layout on radv

  (note: iris is the new DRI driver for newer Intel, not enabled by
  default yet)

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

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

[Desktop-packages] [Bug 1844132] [NEW] FFe: Mesa 19.2.0

[Timo Aaltonen]

Public bug reported:

It would be great to get 19.2.0 in eoan, though it's release cycle has
slipped. It's working fine on a typical desktop use here on i915 (Kaby
Lake). It would also migrate to llvm-9.

It is currently at rc3, and final version is expected to arrive next
week (week 39).

New features:

Support for AMD Navi

GL_ARB_post_depth_coverage on radeonsi (Navi)
GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports 
SEAMLESS_CUBE_MAP)
GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10)
GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR)
GL_EXT_texture_shadow_lod on i965, iris
EGL_EXT_platform_device
VK_AMD_buffer_marker on radv
VK_EXT_index_type_uint8 on radv
VK_EXT_post_depth_coverage on radv
VK_EXT_queue_family_foreign on radv
VK_EXT_sample_locations on radv
VK_EXT_shader_demote_to_helper_invocation on Intel.
VK_KHR_depth_stencil_resolve on radv
VK_KHR_imageless_framebuffer on radv
VK_KHR_shader_atomic_int64 on radv
VK_KHR_uniform_buffer_standard_layout on radv

(note: iris is the new DRI driver for newer Intel, not enabled by
default yet)

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: Confirmed

** Affects: mesa (Ubuntu Eoan)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: Confirmed

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

Title:
  FFe: Mesa 19.2.0

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Eoan:
  Confirmed

Bug description:
  It would be great to get 19.2.0 in eoan, though it's release cycle has
  slipped. It's working fine on a typical desktop use here on i915 (Kaby
  Lake). It would also migrate to llvm-9.

  It is currently at rc3, and final version is expected to arrive next
  week (week 39).

  New features:

  Support for AMD Navi

  GL_ARB_post_depth_coverage on radeonsi (Navi)
  GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports 
SEAMLESS_CUBE_MAP)
  GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10)
  GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR)
  GL_EXT_texture_shadow_lod on i965, iris
  EGL_EXT_platform_device
  VK_AMD_buffer_marker on radv
  VK_EXT_index_type_uint8 on radv
  VK_EXT_post_depth_coverage on radv
  VK_EXT_queue_family_foreign on radv
  VK_EXT_sample_locations on radv
  VK_EXT_shader_demote_to_helper_invocation on Intel.
  VK_KHR_depth_stencil_resolve on radv
  VK_KHR_imageless_framebuffer on radv
  VK_KHR_shader_atomic_int64 on radv
  VK_KHR_uniform_buffer_standard_layout on radv

  (note: iris is the new DRI driver for newer Intel, not enabled by
  default yet)

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

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

[Desktop-packages] [Bug 1844045] Re: Screen flickering during boot and doesn't boot in for a log time

[Daniel van Vugt]

Could you please provide a video of the flickering?

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Screen flickering during boot and doesn't boot in for a log time

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The Wifi sudddenly stopped detecting which made me restart the system
  but at boot time the screen started flickering with ubuntu load screen
  and is taking long time to boot. Used recovery mode to get into the
  system but the same issue occurs everytime I restart or switch on the
  system. The system doesn't seem to suspend on lid close anymore.

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  Uname: Linux 4.15.0-62-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 15 14:51:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0794]
  InstallationDate: Installed on 2018-12-30 (258 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Vostro 15-3568
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=f6ce104c-4c98-4ee1-ba1b-68a51cd38131 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.01
  dmi.board.name: 01Y1RD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.01:bd08/03/2016:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 15-3568
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1829364] Re: Will not play sound via HDMI using 48000 Hz sample rate

[Jarno Suni]

** Description changed:

  Does not play sound when playing file that has 48000 Hz sample rate via
- sink output:iec958-stereo
+ sink output:iec958-stereo. This is when using proprietary nvidia-340
+ driver; when using nouveau driver, HDMI is not even recognized (Bug
+ #1844129).
  
  Note that the device (HP 8510w, having NVIDIA Quadro FX 570M graphics
  adapter) does not have real HDMI audio, but audio is somehow wired from
  motherboard's S/PDIF to HDMI explaining the sink name. Anyway, in the
  attached AlsaInfo.txt there is a device "Node 0x02 [Audio Output] wcaps
  0x30311: Stereo Digital" that has "rates [0x60]: 44100 48000".
  
  Workaround:
  Set
  alternate-sample-rate = 44100
  in /etc/pulse/daemon.conf and restart pulseaudio
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1283 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu May 16 12:39:15 2019
  InstallationDate: Installed on 2019-05-08 (7 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

Title:
  Will not play sound via HDMI using 48000 Hz sample rate

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Does not play sound when playing file that has 48000 Hz sample rate
  via sink output:iec958-stereo. This is when using proprietary
  nvidia-340 driver; when using nouveau driver, HDMI is not even
  recognized (Bug #1844129).

  Note that the device (HP 8510w, having NVIDIA Quadro FX 570M graphics
  adapter) does not have real HDMI audio, but audio is somehow wired
  from motherboard's S/PDIF to HDMI explaining the sink name. Anyway, in
  the attached AlsaInfo.txt there is a device "Node 0x02 [Audio Output]
  wcaps 0x30311: Stereo Digital" that has "rates [0x60]: 44100 48000".

  Workaround:
  Set
  alternate-sample-rate = 44100
  in /etc/pulse/daemon.conf and restart pulseaudio

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1283 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu May 16 12:39:15 2019
  InstallationDate: Installed on 2019-05-08 (7 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1844130] [NEW] Preview not show when clicking on dock icon where 2 or more windows are open

[Will Cooke]

Public bug reported:

Observed behaviour:
In Eoan when clicking on an application icon on the dock where there are two or 
more windows doesn't open the preview.  This is how it worked in D for example.

Expected behaviour:
Click on an icon in the dock where two or more windows are open should open the 
preview showing the mini versions of the available windows.

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


** Tags: rls-ee-incoming

** Tags added: rls-ee-incoming

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

Title:
  Preview not show when clicking on dock icon where 2 or more windows
  are open

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

Bug description:
  Observed behaviour:
  In Eoan when clicking on an application icon on the dock where there are two 
or more windows doesn't open the preview.  This is how it worked in D for 
example.

  Expected behaviour:
  Click on an icon in the dock where two or more windows are open should open 
the preview showing the mini versions of the available windows.

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

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

[Desktop-packages] [Bug 1836826] Re: Snaps not showing in categories due to store section name changes

[Robert Ancell]

** Changed in: gnome-software (Ubuntu Disco)
   Status: Triaged => Fix Committed

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

Title:
  Snaps not showing in categories due to store section name changes

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Triaged
Status in gnome-software source package in Disco:
  Fix Committed
Status in gnome-software source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  The Snap Store changed the names of some of the sections. This means that 
these are no longer mapped to the XDG categories used in GNOME Software. See 
https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/279

  [Test Case]
  1. Open GNOME Software
  2. Go to graphics categeory.

  Expected result:
  Snaps are shown

  Observer result:
  Only .debs are shown

  [Regression Potential]
  Fix is just to change the name mappings, should be low risk.

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

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

[Desktop-packages] [Bug 1843572] Re: Unable to select icons on the Ubuntu dock

[Emanuele]

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

I made a video to show the bug more clearly

https://youtu.be/HbVaZTnssUQ

I hope it's useful.

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

Title:
  Unable to select icons on the Ubuntu dock

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Coincidentally dask to dock did not work anymore: by clicking on any software 
on the dock, I could no longer make the switch from one software to another, it 
seems that the dock has been blocked.
  I attach a file with logs.

  Ubuntu 19.10

  gnome-shell/eoan,now 3.33.91-1ubuntu1 amd64 [installato, automatico]

  gnome-shell-extension-dashtodock/eoan,eoan 66-1 all

  mutter/eoan,now 3.34.0-1ubuntu1 amd64 [installato, automatico]

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 13:40:20 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-18 (204 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent

[Daniel van Vugt]

** Tags added: regression-release

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

Title:
  ubuntu-dock right-click menu appears at the top-left corner of the
  desktop (which in some cases is the wrong monitor) and is permanent

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress

Bug description:
  Very recently the ubuntu-dock has started displaying some right-click
  menus for pinned apps on the wrong monitor. It doesn't happen for all
  the apps, but when it does, the menu is permanent but you can't click
  on it and you have to restart gnome-shell with ALT-F2 'r' (which now
  always kills some apps like firefox).

  See attached screenshot where the menu for gnome-tweaks has appeared
  at the top left of the top monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.1
  Uname: Linux 5.3.0-050300rc8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 11:42:07 2019
  InstallationDate: Installed on 2019-07-01 (71 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1843572] Re: Unable to select icons on the Ubuntu dock

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1843520
   ubuntu-dock right-click menu appears at the top-left corner of the desktop 
(which in some cases is the wrong monitor) and is permanent

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

Title:
  Unable to select icons on the Ubuntu dock

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Coincidentally dask to dock did not work anymore: by clicking on any software 
on the dock, I could no longer make the switch from one software to another, it 
seems that the dock has been blocked.
  I attach a file with logs.

  Ubuntu 19.10

  gnome-shell/eoan,now 3.33.91-1ubuntu1 amd64 [installato, automatico]

  gnome-shell-extension-dashtodock/eoan,eoan 66-1 all

  mutter/eoan,now 3.34.0-1ubuntu1 amd64 [installato, automatico]

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 13:40:20 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-18 (204 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1843952] Re: Artifacts appear when I un-maximize Chromium or Firefox windows [Intel N3350]

[Daniel van Vugt]

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

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


** Summary changed:

- Artifacts appear when I un-maximize Chromium or Firefox windows
+ Artifacts appear when I un-maximize Chromium or Firefox windows [Intel N3350]

** This bug has been marked a duplicate of bug 1835521
   [regression] Windows flicker to black when resizing (Intel Apollo Lake)

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

Title:
  Artifacts appear when I un-maximize Chromium or Firefox windows [Intel
  N3350]

Status in mutter package in Ubuntu:
  New

Bug description:
  It's GNOME on Wayland bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: mutter 3.34.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 00:13:57 2019
  InstallationDate: Installed on 2019-09-09 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent

[Treviño]

@Rocko yes, it's there.

More precisely https://github.com/micheleg/dash-to-
dock/commit/bb5b0c545292549525ab1ceda6bbce633f49cfbd but I'm going to
prepare a fix for this first.

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

Title:
  ubuntu-dock right-click menu appears at the top-left corner of the
  desktop (which in some cases is the wrong monitor) and is permanent

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress

Bug description:
  Very recently the ubuntu-dock has started displaying some right-click
  menus for pinned apps on the wrong monitor. It doesn't happen for all
  the apps, but when it does, the menu is permanent but you can't click
  on it and you have to restart gnome-shell with ALT-F2 'r' (which now
  always kills some apps like firefox).

  See attached screenshot where the menu for gnome-tweaks has appeared
  at the top left of the top monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.1
  Uname: Linux 5.3.0-050300rc8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 11:42:07 2019
  InstallationDate: Installed on 2019-07-01 (71 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1843572] Re: Unable to select icons on the Ubuntu dock

[Emanuele]

I've had other random freezes, the most common problem is when I right-click on 
the menu (ubuntu-dock), it stays in the menu above on the top left, and doesn't 
go away easily.
When I right-click the dock icon, I have this log:

set 16 14:18:51 emanuc gnome-shell[2402]: JS ERROR: TypeError: 
mutterWindow.get_texture(...).get_size is not a function
  
_cloneTexture@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/windowPreview.js:382:62
  
_init@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/windowPreview.js:371:9
  
_populateAllWindowMenu@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:982:32
  
update@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:943:15
  
_redisplay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:909:9
  
popup@resource:///org/gnome/shell/ui/appDisplay.js:2341:9
  
popupMenu@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:351:9
  
_onButtonPress@resource:///org/gnome/shell/ui/appDisplay.js:1947:13


113/5000
I hope I explained myself well, if there are other things I can do to identify 
the problem, tell me. Thanks

** Attachment added: "Schermata del 2019-09-16 14-10-28.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843572/+attachment/5289003/+files/Schermata%20del%202019-09-16%2014-10-28.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/1843572

Title:
  Unable to select icons on the Ubuntu dock

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Coincidentally dask to dock did not work anymore: by clicking on any software 
on the dock, I could no longer make the switch from one software to another, it 
seems that the dock has been blocked.
  I attach a file with logs.

  Ubuntu 19.10

  gnome-shell/eoan,now 3.33.91-1ubuntu1 amd64 [installato, automatico]

  gnome-shell-extension-dashtodock/eoan,eoan 66-1 all

  mutter/eoan,now 3.34.0-1ubuntu1 amd64 [installato, automatico]

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 13:40:20 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-18 (204 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1843927] Re: Missing graphics drivers for AMD Ryzen 5 with Radeon Vega 8

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1843927

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Tags added: disco

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

** Summary changed:

- Missing graphics drivers for AMD Ryzen 5 with Radeon Vega 8
+ HDMI monitor not detected [AMD Ryzen 5 with Radeon Vega 8]

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

Title:
  HDMI monitor not detected [AMD Ryzen 5 with Radeon Vega 8]

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have recently installed Ubuntu 19.04 on an ASUS TUF Gaming FX505DY
  laptop.  The laptop has a AMD Ryzen 5 with Radeon Vega 8 processor.

  No warnings where raised during the installation process regarding
  problems with the graphics driver.  When I connected a HDMI connected
  monitor I found it did not work.

  I have attached the graphics driver logs

  ==
  cat /var/log/gpu-manager.log

  log_file: /var/log/gpu-manager.log
  last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
  new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
  can't access /run/u-d-c-nvidia-was-loaded file
  can't access /opt/amdgpu-pro/bin/amdgpu-pro-px
  Looking for nvidia modules in /lib/modules/5.0.0-27-generic/updates/dkms
  Looking for amdgpu modules in /lib/modules/5.0.0-27-generic/updates/dkms
  Is nvidia loaded? no
  Was nvidia unloaded? no
  Is nvidia blacklisted? no
  Is intel loaded? no
  Is radeon loaded? no
  Is radeon blacklisted? no
  Is amdgpu loaded? no
  Is amdgpu blacklisted? no
  Is amdgpu versioned? no
  Is amdgpu pro stack? no
  Is nouveau loaded? no
  Is nouveau blacklisted? no
  Is nvidia kernel module available? no
  Is amdgpu kernel module available? no
  Vendor/Device Id: 1002:67ef
  BusID "PCI:1@0:0:0"
  Is boot vga? no
  Error: can't access /sys/bus/pci/devices/:01:00.0/driver
  The device is not bound to any driver.
  Vendor/Device Id: 1002:15d8
  BusID "PCI:5@0:0:0"
  Is boot vga? yes
  Error: can't access /sys/bus/pci/devices/:05:00.0/driver
  The device is not bound to any driver.
  Error : Failed to open /dev/dri
  Error : Failed to open /dev/dri
  Error : Failed to open /dev/dri
  Error : Failed to open /dev/dri
  Does it require offloading? no
  last cards number = 2
  Has amd? yes
  Has intel? no
  Has nvidia? no
  How many cards? 2
  Has the system changed? No
  Unsupported discrete card vendor: 1002
  Nothing to do

  
==  
sudo lshw -C display
*-display UNCLAIMED   
 description: Display controller
 product: Baffin [Radeon RX 460/560D / Pro 450/455/460/555/560]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: e5
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi cap_list
 configuration: latency=0
 resources: memory:e000-efff memory:f000-f01f 
ioport:f000(size=256) memory:fea0-fea3 memory:fea4-fea5
*-display UNCLAIMED
 description: VGA compatible controller
 product: Picasso
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:05:00.0
 version: c2
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
 configuration: latency=0
 resources: memory:c000-cfff memory:d000-d01f 
ioport:c000(size=256) memory:fe50-fe57

  
  
*
  QUESTIONS

  1.  Why is the problem with unsupported drivers not flagged during the
  installation process?  The default driver does work for the laptop's
  monitor, but will not drive a second monitor attached to the HDMI port

  2.  I have seen reference to a general purpose AMD graphics driver,
  but there is no reference to this driver being supported on Ubuntu
  19.04.  If I went ahead and attempted to install the general purpose
  graphics driver, how would I back it out if it did not work.

  I have raised this issue as a "question", but I think it is probably a
  bug but I could not find out how to raise a bug associated with a lack
  of device drivers.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1843927] Re: HDMI monitor not detected [AMD Ryzen 5 with Radeon Vega 8]

[Daniel van Vugt]

Please also run the command:

  lspci -k > lspcik.txt

and send us the resulting file 'lspcik.txt'.

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

Title:
  HDMI monitor not detected [AMD Ryzen 5 with Radeon Vega 8]

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have recently installed Ubuntu 19.04 on an ASUS TUF Gaming FX505DY
  laptop.  The laptop has a AMD Ryzen 5 with Radeon Vega 8 processor.

  No warnings where raised during the installation process regarding
  problems with the graphics driver.  When I connected a HDMI connected
  monitor I found it did not work.

  I have attached the graphics driver logs

  ==
  cat /var/log/gpu-manager.log

  log_file: /var/log/gpu-manager.log
  last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
  new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
  can't access /run/u-d-c-nvidia-was-loaded file
  can't access /opt/amdgpu-pro/bin/amdgpu-pro-px
  Looking for nvidia modules in /lib/modules/5.0.0-27-generic/updates/dkms
  Looking for amdgpu modules in /lib/modules/5.0.0-27-generic/updates/dkms
  Is nvidia loaded? no
  Was nvidia unloaded? no
  Is nvidia blacklisted? no
  Is intel loaded? no
  Is radeon loaded? no
  Is radeon blacklisted? no
  Is amdgpu loaded? no
  Is amdgpu blacklisted? no
  Is amdgpu versioned? no
  Is amdgpu pro stack? no
  Is nouveau loaded? no
  Is nouveau blacklisted? no
  Is nvidia kernel module available? no
  Is amdgpu kernel module available? no
  Vendor/Device Id: 1002:67ef
  BusID "PCI:1@0:0:0"
  Is boot vga? no
  Error: can't access /sys/bus/pci/devices/:01:00.0/driver
  The device is not bound to any driver.
  Vendor/Device Id: 1002:15d8
  BusID "PCI:5@0:0:0"
  Is boot vga? yes
  Error: can't access /sys/bus/pci/devices/:05:00.0/driver
  The device is not bound to any driver.
  Error : Failed to open /dev/dri
  Error : Failed to open /dev/dri
  Error : Failed to open /dev/dri
  Error : Failed to open /dev/dri
  Does it require offloading? no
  last cards number = 2
  Has amd? yes
  Has intel? no
  Has nvidia? no
  How many cards? 2
  Has the system changed? No
  Unsupported discrete card vendor: 1002
  Nothing to do

  
==  
sudo lshw -C display
*-display UNCLAIMED   
 description: Display controller
 product: Baffin [Radeon RX 460/560D / Pro 450/455/460/555/560]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: e5
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi cap_list
 configuration: latency=0
 resources: memory:e000-efff memory:f000-f01f 
ioport:f000(size=256) memory:fea0-fea3 memory:fea4-fea5
*-display UNCLAIMED
 description: VGA compatible controller
 product: Picasso
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:05:00.0
 version: c2
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
 configuration: latency=0
 resources: memory:c000-cfff memory:d000-d01f 
ioport:c000(size=256) memory:fe50-fe57

  
  
*
  QUESTIONS

  1.  Why is the problem with unsupported drivers not flagged during the
  installation process?  The default driver does work for the laptop's
  monitor, but will not drive a second monitor attached to the HDMI port

  2.  I have seen reference to a general purpose AMD graphics driver,
  but there is no reference to this driver being supported on Ubuntu
  19.04.  If I went ahead and attempted to install the general purpose
  graphics driver, how would I back it out if it did not work.

  I have raised this issue as a "question", but I think it is probably a
  bug but I could not find out how to raise a bug associated with a lack
  of device drivers.

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

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

[Desktop-packages] [Bug 1843955] Re: Black zones in context menu appear in Firefox when I use GNOME on Wayland session

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1751593
   Weird black border flickers around windows in Wayland sessions

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

Title:
  Black zones in context menu appear  in Firefox when I use GNOME on
  Wayland session

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

Bug description:
  Eyes are very tired because of this

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 69.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 2019091951
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 00:28:29 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2019-09-09 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=69.0/2019091951 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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