[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment

[Leonardo Veiga]

I have nvidia-520 installed for a while. After noticing that the
packages have been kept back (don't know why), I tried to upgrade the
driver from the "Software and Updates" GUI. Not possible, all options
grayed out and a message reads "This device is using a manually-
installed driver".

Then I tried to "sudo ubuntu-drivers autoinstall", and got the error
"UnboundLocalError: local variable 'version' referenced before
assignment" and to this bug report.

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

Title:
  UnboundLocalError: local variable 'version' referenced before
  assignment

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

Bug description:
  Hello, we received a drive-by complaint about the ubuntu-drivers
  autoinstall tool:

  < Fhazal> hye i have problem with ubuntu 22.04 nvidia auto install command
  < Fhazal> this error appear when i try to auto install recommended driver
  < Fhazal> https://pastebin.com/ydZVFT24

  The contents of the pastebin:

  Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in 
  greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
  return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
  rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
  return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
  return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in 
new_func
  return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 432, in autoinstall
  command_install(config)
File "/usr/bin/ubuntu-drivers", line 187, in command_install
  UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in 
nvidia_desktop_pre_installation_hook
  with_nvidia_kms = version >= 470
  UnboundLocalError: local variable 'version' referenced before assignment

  
  Skimming the version on my system it sure feels plausible:

  def nvidia_desktop_pre_installation_hook(to_install):
  '''Applies changes that need to happen before installing the NVIDIA 
drivers'''
  with_nvidia_kms = False

  # Enable KMS if nvidia >= 470
  for package_name in to_install:
  if package_name.startswith('nvidia-driver-'):
  try:
  version = int(package_name.split('-')[-1])
  except ValueError:
  pass
  finally:
  with_nvidia_kms = version >= 470

  if with_nvidia_kms:
  set_nvidia_kms(1)


  If there was an exception splitting, indexing, or converting to an
  int, that 'version' variable may not have a value.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1993019/+subscriptions


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

[Desktop-packages] [Bug 1973389] [NEW] Audio freezes, skips and failure to change volume when opening snap

[Leonardo Müller]

Public bug reported:

When opening a snap, sounds being played may start skipping or freezing
and volume changes start failing, it can last from a few milliseconds to
multiple seconds, depending on the program being opened and how the
program playing the sound behaves.

This was observed with Firefox, Chromium, Teams, Retroarch and
Thunderbird snaps, at least.

When opening them, it's possible to see at least 50% iowait on top, htop
shows D for some processes, even pipewire, pipewire-pulse and
wireplumber may iowait.

A way to recreate this is to have some other program playing audio, as
celluloid, and then open a snap or many of them at once for the first
time.

This computer has a 5400 RPM HDD, which surely is part of the problem,
but still, sound freezes when opening the default web browser cause a
very negative experience. I can't reproduce this opening a program
installed as a deb, such as Stellarium, Google Chrome, SuperTuxKart or
even Steam.

I don't remember pulseaudio being so sensitive to iowait.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pipewire 0.3.48-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Fri May 13 22:08:16 2022
InstallationDate: Installed on 2017-06-13 (1795 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: pipewire
UpgradeStatus: Upgraded to jammy on 2019-12-22 (873 days ago)
modified.conffile..etc.cron.daily.apport: [deleted]

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


** Tags: amd64 apport-bug jammy third-party-packages

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

Title:
  Audio freezes, skips and failure to change volume when opening snap

Status in pipewire package in Ubuntu:
  New

Bug description:
  When opening a snap, sounds being played may start skipping or
  freezing and volume changes start failing, it can last from a few
  milliseconds to multiple seconds, depending on the program being
  opened and how the program playing the sound behaves.

  This was observed with Firefox, Chromium, Teams, Retroarch and
  Thunderbird snaps, at least.

  When opening them, it's possible to see at least 50% iowait on top,
  htop shows D for some processes, even pipewire, pipewire-pulse and
  wireplumber may iowait.

  A way to recreate this is to have some other program playing audio, as
  celluloid, and then open a snap or many of them at once for the first
  time.

  This computer has a 5400 RPM HDD, which surely is part of the problem,
  but still, sound freezes when opening the default web browser cause a
  very negative experience. I can't reproduce this opening a program
  installed as a deb, such as Stellarium, Google Chrome, SuperTuxKart or
  even Steam.

  I don't remember pulseaudio being so sensitive to iowait.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pipewire 0.3.48-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri May 13 22:08:16 2022
  InstallationDate: Installed on 2017-06-13 (1795 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to jammy on 2019-12-22 (873 days ago)
  modified.conffile..etc.cron.daily.apport: [deleted]

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


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

[Desktop-packages] [Bug 1969254] Re: wayland session not longer an option after recent update on Ubuntu 22.04

[Leonardo Ornelas]

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

Same problem for me.

NVIDIA Corporation GP108M [GeForce MX330] / Mesa Intel® Xe Graphics (TGL GT2) + 
 driver 510.
11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz × 8

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

Title:
  wayland session not longer an option after recent update on Ubuntu
  22.04

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  After some recent update to Ubuntu 22.04 dev, X11 is selected by
  default and there is no longer the option to select the display
  protocol at login.

  It seems I am not the only affected:
  https://askubuntu.com/questions/1402671/ubuntu-no-gear-for-
  waylaland-x11

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-session 42.0-1ubuntu2
  Uname: Linux 5.17.3-051703-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 15 22:20:35 2022
  InstallationDate: Installed on 2022-02-02 (72 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (28 days ago)

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


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

[Desktop-packages] [Bug 1961333] [NEW] Netbook display is turned off on login screen on startup

[Leonardo Soares Müller]

Public bug reported:

On the netbook model Positivo Mobo 5800, it was noticed that, on the end
of the boot process, the LightDM greeter won't appear and the screen
will turn off, disabling the backlight too. To be able to log in to the
graphical interface, it's required to go to a tty (for example, tty1)
and then back to the LightDM greeter (which is tty7 on this case).

When going back to the tty7, it's noticed that there are text still from
the boot for a few seconds, until the greeter finally appears.

The CPU is an Intel(R) Atom(TM) CPU N2600 @ 1.60GHz, it has a gma500
GPU. While gma500 is limiting, I've not observed this LightDM bug with,
for example, the Positivo Mobo 5900, which has the same CPU and same GPU
with the same revision and, even when applying the same image to both,
the 5900 works while the 5800 fails.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lightdm 1.30.0-0ubuntu4~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
Uname: Linux 5.4.0-100-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Feb 17 15:30:44 2022
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Netbook display is turned off on login screen on startup

Status in lightdm package in Ubuntu:
  New

Bug description:
  On the netbook model Positivo Mobo 5800, it was noticed that, on the
  end of the boot process, the LightDM greeter won't appear and the
  screen will turn off, disabling the backlight too. To be able to log
  in to the graphical interface, it's required to go to a tty (for
  example, tty1) and then back to the LightDM greeter (which is tty7 on
  this case).

  When going back to the tty7, it's noticed that there are text still
  from the boot for a few seconds, until the greeter finally appears.

  The CPU is an Intel(R) Atom(TM) CPU N2600 @ 1.60GHz, it has a gma500
  GPU. While gma500 is limiting, I've not observed this LightDM bug
  with, for example, the Positivo Mobo 5900, which has the same CPU and
  same GPU with the same revision and, even when applying the same image
  to both, the 5900 works while the 5800 fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu4~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
  Uname: Linux 5.4.0-100-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Feb 17 15:30:44 2022
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1924882] [NEW] Random freezing of the computer during testing.

[Leonardo]

Public bug reported:

I1m using UBUNTU 20.04

Problem: Occasionally there is a failure to display on the screen with
parts alternating colors and characters exchanged in the terminal (only
in the terminal). Control characters are displayed on the terminal and
"blink" effects occur on some lines.

First symptom: The firefox update made the browser screen (just inside
the browser screen) appear many black blocks over the texts and images,
corrected with the deactivation of the use of graphical acceleration.

Second symptom: after an update of ubuntu, he started to have a problem
in the terminal, with control characters being displayed and a change in
the mapping of the keyboard keys BUT this error does not happen in
GEdit.

Current symptom: when I open the terminal, the favorite icons on the edge of 
the screen where the terminal was opened change color alternately. The terminal 
screen has control characters and changes from character mapping to some keys.
The browser is not fluent in scrolling a web page.

Reboot the computer everything is normal and after a while it happens
again.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Sat Apr 17 22:13:54 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:100d]
InstallationDate: Installed on 2021-02-23 (53 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ASUSTeK COMPUTER INC. K46CA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=ec0afab4-cb78-44a3-8868-cf6565dfb058 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/17/2013
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K46CA.315
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K46CA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK46CA.315:bd05/17/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnK46CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: K
dmi.product.name: K46CA
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Random freezing of the computer during testing.

Status in xorg package in Ubuntu:
  New

Bug description:
  I1m using UBUNTU 20.04

  Problem: Occasionally there is a failure to display on the screen with
  parts alternating colors and characters exchanged in the terminal
  (only in the terminal). Control characters are displayed on the
  terminal and "blink" effects occur on some lines.

  First symptom: The firefox update made the browser screen (just inside
  the browser screen) appear many black blocks over the texts and
  images, corrected with the deactivation of the use of graphical
  acceleration.

  Second symptom: after an update of ubuntu, he started to have a
  problem in the terminal, with control characters being displayed and a
  change in the mapping of the keyboard keys BUT this error does not
  happen in GEdit.

  Current symptom: when I open the terminal, the favorite icons on the edge of 
the screen where the terminal was opened change color alternately. The terminal 
screen has control characters and changes from character mapping to some keys.
  The browser is not fluent in scrolling a web page.

  Reboot the computer everything is normal and after a while it happens
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 1817785] Re: installation of texlive-latex-base-doc does not make the documentation available to 'texdoc'

[Leonardo Gama]

This is affecting me in a fresh Ubuntu 18.04 installation. Thank's for
the temporary solution, @Ernst.

Here is a related question (made 9 months prior to this bug report
openning) on the TeX StackExchange website:
https://tex.stackexchange.com/questions/431244/texdoc-does-not-work-
anymore-after-ubuntu-upgrade/580678

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

Title:
  installation of texlive-latex-base-doc does not make the documentation
  available to 'texdoc'

Status in texlive-base package in Ubuntu:
  Confirmed

Bug description:
  I had texlive installed previously, on a freshly installed 18.04 system.
  Now I installed texlive-latex-base-doc.

  after installation, texdoc did not find the requested documentation, e.g. 
  $texdoc amsldoc
  Sorry, no documentation found for amsldoc.

  Only after executing 'dpkg-reconfigure texlive-base' the documentation
  was found.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: texlive-latex-base-doc (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 26 20:56:05 2019
  InstallationDate: Installed on 2014-08-28 (1643 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  SourcePackage: texlive-base
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (196 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1817785/+subscriptions

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

[Desktop-packages] [Bug 1901196] Re: kernel module failed to build [ Bad return status for module build on kernel: 5.8.0-25-generic (x86_64)]

[Leonardo]

I tried:

cd /usr/src/linux-headers-5.8.0-25-generic
sudo make oldconfig

   YACC scripts / kconfig / parser.tab. [Ch]
   HOSTCC scripts / kconfig / lexer.lex.o
   HOSTCC scripts / kconfig / parser.tab.o
   HOSTCC scripts / kconfig / preprocess.o
   HOSTCC scripts / kconfig / symbol.o
   HOSTCC scripts / kconfig / util.o
   HOSTLD scripts / kconfig / conf
scripts / kconfig / conf --oldconfig Kconfig
#
# configuration written to .config
#

And later:
sudo make prepare

scripts / kconfig / conf --syncconfig Kconfig
make [1]: *** There is no rule to build the target 'arch / x86 / tools / 
relocs_32.c', necessary for 'arch / x86 / tools / relocs_32.o'. High.
make: *** [arch / x86 / Makefile: 211: archscripts] Error 2

Is it here the bug?

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

Title:
  kernel module failed to build [ Bad return status for module build on
  kernel: 5.8.0-25-generic (x86_64)]

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

Bug description:
  While installing Nvidia-340 driver, I am getting the following error.

  Setting up nvidia-340 (340.108-0ubuntu5) ...
  dpkg: error: version '-' has bad syntax: revision number is empty
  dpkg: error: version '-' has bad syntax: revision number is empty
  dpkg: error: version '-' has bad syntax: revision number is empty
  update-initramfs: deferring update (trigger activated)
  INFO:Enable nvidia-340
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  Removing old nvidia-340-340.108 DKMS files...
  Loading new nvidia-340-340.108 DKMS files...
  Building for 5.8.0-25-generic
  Building for architecture x86_64
  Building initial module for 5.8.0-25-generic
  Error! Bad return status for module build on kernel: 5.8.0-25-generic (x86_64)
  Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information.
  dpkg: error processing package nvidia-340 (--configure):
   installed nvidia-340 package post-installation script subprocess returned 
error exit status 10
  Processing triggers for libc-bin (2.32-0ubuntu3) ...
  Processing triggers for initramfs-tools (0.137ubuntu12) ...
  update-initramfs: Generating /boot/initrd.img-5.8.0-25-generic
  Errors were encountered while processing:
   nvidia-340
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1901196/+subscriptions

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

[Desktop-packages] [Bug 1901196] Re: kernel module failed to build [ Bad return status for module build on kernel: 5.8.0-25-generic (x86_64)]

[Leonardo]

Hello, I'm the same. I started researching and tried:
sudo dkms --verbose build -m nvidia-340 -v 340.108
and it returned the same error.

Since I still have an old kernel installed I tried:
sudo dkms --verbose build -m nvidia-340 -v 340.108 -k 5.4.0-26-generic

and it worked perfect, just for that kernel.

I don't have much knowledge, and I don't know where the error can be
with the 5.8.0-25-generic kernel.

Note: I just upgraded Ubuntu to Groovy, everything worked fine except
nvidia-340.

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

Title:
  kernel module failed to build [ Bad return status for module build on
  kernel: 5.8.0-25-generic (x86_64)]

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

Bug description:
  While installing Nvidia-340 driver, I am getting the following error.

  Setting up nvidia-340 (340.108-0ubuntu5) ...
  dpkg: error: version '-' has bad syntax: revision number is empty
  dpkg: error: version '-' has bad syntax: revision number is empty
  dpkg: error: version '-' has bad syntax: revision number is empty
  update-initramfs: deferring update (trigger activated)
  INFO:Enable nvidia-340
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  Removing old nvidia-340-340.108 DKMS files...
  Loading new nvidia-340-340.108 DKMS files...
  Building for 5.8.0-25-generic
  Building for architecture x86_64
  Building initial module for 5.8.0-25-generic
  Error! Bad return status for module build on kernel: 5.8.0-25-generic (x86_64)
  Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information.
  dpkg: error processing package nvidia-340 (--configure):
   installed nvidia-340 package post-installation script subprocess returned 
error exit status 10
  Processing triggers for libc-bin (2.32-0ubuntu3) ...
  Processing triggers for initramfs-tools (0.137ubuntu12) ...
  update-initramfs: Generating /boot/initrd.img-5.8.0-25-generic
  Errors were encountered while processing:
   nvidia-340
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1901196/+subscriptions

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

[Desktop-packages] [Bug 1890494] Re: Closing Rhythmbox does not free the media keys

[Leonardo Jeanteur]

I am running Ubuntu in x11

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

Title:
  Closing Rhythmbox does not free the media keys

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Closing Rhythmbox, does not free the media keys, and no program can
  use them after that, not even Rhythmbox if you restart it.

  This seems to be very close to bug #1036489, but that one was active 8
  years ago, and was marked as expired 6 years ago.

  Restarting the machine frees the media keys again.

  Steps to reproduce:

  1. Verify that the media keys work (restart the machine if not)
  2. close rhythmbox with right click on the taskbar icon, use "stop & quit"
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. End the 'rhythmbox' process
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. in rhythmbox go to preferences -> plugins -> click preferences for any 
plugin
  3. click the 'restart' next to "Restart the player for the changes to take 
effect"
  4. once rhythmbox restarts, the media keys do not work anymore.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  
  $ apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.4-1ubuntu2
Candidate: 3.4.4-1ubuntu2
Version table:
   *** 3.4.4-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1890494] Re: Closing Rhythmbox does not free the media keys

[Leonardo Jeanteur]

Looking at my plugins I have both "MediaServer3 D-Bus Interface" and
"MPRIS D-Bus Interface" activated

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

Title:
  Closing Rhythmbox does not free the media keys

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Closing Rhythmbox, does not free the media keys, and no program can
  use them after that, not even Rhythmbox if you restart it.

  This seems to be very close to bug #1036489, but that one was active 8
  years ago, and was marked as expired 6 years ago.

  Restarting the machine frees the media keys again.

  Steps to reproduce:

  1. Verify that the media keys work (restart the machine if not)
  2. close rhythmbox with right click on the taskbar icon, use "stop & quit"
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. End the 'rhythmbox' process
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. in rhythmbox go to preferences -> plugins -> click preferences for any 
plugin
  3. click the 'restart' next to "Restart the player for the changes to take 
effect"
  4. once rhythmbox restarts, the media keys do not work anymore.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  
  $ apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.4-1ubuntu2
Candidate: 3.4.4-1ubuntu2
Version table:
   *** 3.4.4-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1890494] Re: Closing Rhythmbox does not free the media keys

[Leonardo Jeanteur]

launching with rhythmbox --disable-plugins does not allow for media buttons at 
all.
When trying to use one the 'no entry' sign show up on the screen

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

Title:
  Closing Rhythmbox does not free the media keys

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Closing Rhythmbox, does not free the media keys, and no program can
  use them after that, not even Rhythmbox if you restart it.

  This seems to be very close to bug #1036489, but that one was active 8
  years ago, and was marked as expired 6 years ago.

  Restarting the machine frees the media keys again.

  Steps to reproduce:

  1. Verify that the media keys work (restart the machine if not)
  2. close rhythmbox with right click on the taskbar icon, use "stop & quit"
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. End the 'rhythmbox' process
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. in rhythmbox go to preferences -> plugins -> click preferences for any 
plugin
  3. click the 'restart' next to "Restart the player for the changes to take 
effect"
  4. once rhythmbox restarts, the media keys do not work anymore.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  
  $ apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.4-1ubuntu2
Candidate: 3.4.4-1ubuntu2
Version table:
   *** 3.4.4-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1890632] [NEW] Can't open preferences

[Leonardo Jeanteur]

Public bug reported:

I can't seem to access the rhymbox preferences.
'Preferences' does not appear in the application menu (see attachment) since 
ubuntu 17.10.
I was still able to edit the preferences from the menu under the song slider, 
but I have now accidentally removed the whole top bar (with the current song, 
the previous, next, pause buttons, and that menu button).

So now I can't open the preferences, nor see the current song anymore,
or have it display again.

Note that the option in the view menu might have been from the
Alternative-Toolbar plugin

A temporary fix to get the view menu again would be appreciated too.

$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04

$ apt-cache policy rhythmbox
rhythmbox:
  Installed: 3.4.4-1ubuntu2
  Candidate: 3.4.4-1ubuntu2
  Version table:
 *** 3.4.4-1ubuntu2 500
500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status


Mirror of the attachment (screenshot of the application menu):
https://i.imgur.com/CJUVoRZ.png

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

** Attachment added: "rhythmbox no preferences.png"
   
https://bugs.launchpad.net/bugs/1890632/+attachment/5399332/+files/rhythmbox%20no%20preferences.png

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

Title:
  Can't open preferences

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  I can't seem to access the rhymbox preferences.
  'Preferences' does not appear in the application menu (see attachment) since 
ubuntu 17.10.
  I was still able to edit the preferences from the menu under the song slider, 
but I have now accidentally removed the whole top bar (with the current song, 
the previous, next, pause buttons, and that menu button).

  So now I can't open the preferences, nor see the current song anymore,
  or have it display again.

  Note that the option in the view menu might have been from the
  Alternative-Toolbar plugin

  A temporary fix to get the view menu again would be appreciated too.

  $ lsb_release -rd
  Description: Ubuntu 20.04.1 LTS
  Release: 20.04

  $ apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.4-1ubuntu2
Candidate: 3.4.4-1ubuntu2
Version table:
   *** 3.4.4-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Mirror of the attachment (screenshot of the application menu):
  https://i.imgur.com/CJUVoRZ.png

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

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

[Desktop-packages] [Bug 1890494] Re: Closing Rhythmbox does not free the media keys

[Leonardo Jeanteur]

After restarting the machine, launching rhythmbox from the command line does 
not print messages.
Subsequent launches do however

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

Title:
  Closing Rhythmbox does not free the media keys

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Closing Rhythmbox, does not free the media keys, and no program can
  use them after that, not even Rhythmbox if you restart it.

  This seems to be very close to bug #1036489, but that one was active 8
  years ago, and was marked as expired 6 years ago.

  Restarting the machine frees the media keys again.

  Steps to reproduce:

  1. Verify that the media keys work (restart the machine if not)
  2. close rhythmbox with right click on the taskbar icon, use "stop & quit"
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. End the 'rhythmbox' process
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. in rhythmbox go to preferences -> plugins -> click preferences for any 
plugin
  3. click the 'restart' next to "Restart the player for the changes to take 
effect"
  4. once rhythmbox restarts, the media keys do not work anymore.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  
  $ apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.4-1ubuntu2
Candidate: 3.4.4-1ubuntu2
Version table:
   *** 3.4.4-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1890494] Re: Closing Rhythmbox does not free the media keys

[Leonardo Jeanteur]

I am talking about the pause/play, previous song and next song keys.
On my Dell xps 13 laptop, those are f4, f5 and f6 (or fn + f4, fn + f5, fn + f6)

When opening Rhythmbox from the command line: (this is after having opened and 
closed it once, so the media keys were already not working)
Opening and using rhythmbox does not print error messages, but closing does:
/usr/lib/python3/dist-packages/gi/overrides/GObject.py:502: Warning: 
../../../gobject/gsignal.c:2735: instance '0x5635f68af300' has no handler with 
id '12157'
  return func(*args, **kwargs)
/usr/lib/python3/dist-packages/gi/overrides/GObject.py:502: Warning: 
../../../gobject/gsignal.c:2735: instance '0x5635f68af300' has no handler with 
id '12156'
  return func(*args, **kwargs)
/usr/lib/python3/dist-packages/gi/overrides/GObject.py:502: Warning: 
../../../gobject/gsignal.c:2735: instance '0x5635f68af300' has no handler with 
id '40060'
  return func(*args, **kwargs)


I will now restart my machine to launch rhythmbox the first time from
the command line (with working media keys)

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

Title:
  Closing Rhythmbox does not free the media keys

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Closing Rhythmbox, does not free the media keys, and no program can
  use them after that, not even Rhythmbox if you restart it.

  This seems to be very close to bug #1036489, but that one was active 8
  years ago, and was marked as expired 6 years ago.

  Restarting the machine frees the media keys again.

  Steps to reproduce:

  1. Verify that the media keys work (restart the machine if not)
  2. close rhythmbox with right click on the taskbar icon, use "stop & quit"
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. End the 'rhythmbox' process
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. in rhythmbox go to preferences -> plugins -> click preferences for any 
plugin
  3. click the 'restart' next to "Restart the player for the changes to take 
effect"
  4. once rhythmbox restarts, the media keys do not work anymore.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  
  $ apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.4-1ubuntu2
Candidate: 3.4.4-1ubuntu2
Version table:
   *** 3.4.4-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1890494] [NEW] Closing Rhythmbox does not free the media keys

[Leonardo Jeanteur]

Public bug reported:

Closing Rhythmbox, does not free the media keys, and no program can use
them after that, not even Rhythmbox if you restart it.

This seems to be very close to bug #1036489, but that one was active 8
years ago, and was marked as expired 6 years ago.

Restarting the machine frees the media keys again.

Steps to reproduce:

1. Verify that the media keys work (restart the machine if not)
2. close rhythmbox with right click on the taskbar icon, use "stop & quit"
3. reopen rhythmbox, the media keys do not work.

1. Verify that the media keys work (restart the machine if not)
2. End the 'rhythmbox' process
3. reopen rhythmbox, the media keys do not work.

1. Verify that the media keys work (restart the machine if not)
2. in rhythmbox go to preferences -> plugins -> click preferences for any plugin
3. click the 'restart' next to "Restart the player for the changes to take 
effect"
4. once rhythmbox restarts, the media keys do not work anymore.


$ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04


$ apt-cache policy rhythmbox
rhythmbox:
  Installed: 3.4.4-1ubuntu2
  Candidate: 3.4.4-1ubuntu2
  Version table:
 *** 3.4.4-1ubuntu2 500
500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  Closing Rhythmbox does not free the media keys

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Closing Rhythmbox, does not free the media keys, and no program can
  use them after that, not even Rhythmbox if you restart it.

  This seems to be very close to bug #1036489, but that one was active 8
  years ago, and was marked as expired 6 years ago.

  Restarting the machine frees the media keys again.

  Steps to reproduce:

  1. Verify that the media keys work (restart the machine if not)
  2. close rhythmbox with right click on the taskbar icon, use "stop & quit"
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. End the 'rhythmbox' process
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. in rhythmbox go to preferences -> plugins -> click preferences for any 
plugin
  3. click the 'restart' next to "Restart the player for the changes to take 
effect"
  4. once rhythmbox restarts, the media keys do not work anymore.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  
  $ apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.4-1ubuntu2
Candidate: 3.4.4-1ubuntu2
Version table:
   *** 3.4.4-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1036489] Re: Closing Rhythmbox doesn't close Rhythmbox and causes confusing key-binding behavior

[Leonardo Jeanteur]

This still affects me in Ubuntu 20.04.

Fully closing Rhythmbox does not free up the media keys, and if you
reopen it later the media keys will not work (and won't work for other
programs either)

Different ways to reproduce (note that the only way to have the media
keys working again is to restart the machine)

1. Verify that the media keys work (restart the machine if not)
2. close rhythmbox with right click on the taskbar icon, use "stop & quit"
3. reopen rhythmbox, the media keys do not work.

1. Verify that the media keys work (restart the machine if not)
2. End the 'rhythmbox' process
3. reopen rhythmbox, the media keys do not work.

1. Verify that the media keys work (restart the machine if not)
2. in rhythmbox go to preferences -> plugins -> click preferences for any plugin
3. click the 'restart' next to "Restart the player for the changes to take 
effect" 
4. once rhythmbox restarts, the media keys do not work anymore.

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

Title:
  Closing Rhythmbox doesn't close Rhythmbox and causes confusing key-
  binding behavior

Status in rhythmbox package in Ubuntu:
  Expired

Bug description:
  This is a problem I am experiencing in Quantal right now. Here is how
  to trigger it:

   1. I load Pithos and start listening to music. My track change and 
start/pause key-bindings work great.
   2. I load Rhythmbox to listen to a song on my computer. I stop Pithos 
playing and start playing Rhythmbox.
   3. With two media players open my key-bindings only seem to apply to one 
player, so I close Rhythmbox (clicking the X in the window).
   4. The window is not actually closed and my key-bindings still affect 
Rhythmbox - this is confusing as I see no icon on my Launcher.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
  Uname: Linux 3.5.0-8-generic i686
  ApportVersion: 2.4-0ubuntu6
  Architecture: i386
  Date: Mon Aug 13 21:20:01 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1880340] [NEW] Samba Bug delete gvfs-backends

[Leonardo Gilberto Muñoz Mendez]

Public bug reported:

Other Bug in the 18.04 Distribution I explain the cause of this error

About 3 months ago install samba all be good but delete the samba application 
but have and error 
a dialog box appears when I click in search net a circle red and tell me 
impossible mount /

I search in the net and the problem resolve in this form:

userspace virtual filesystem - backends
gvfs is a userspace virtual filesystem where mounts run as separate processes 
which you talk to via D-Bus. It also contains a gio module that seamlessly adds 
gvfs support to all applications using the gio API. It also supports exposing 
the gvfs mounts to non-gio applications using fuse. userspace virtual 
filesystem - backends
gvfs is a userspace virtual filesystem where mounts run as separate processes 
which you talk to via D-Bus. It also contains a gio module that seamlessly adds 
gvfs support to all applications using the gio API. It also supports exposing 
the gvfs mounts to non-gio applications using fuse.

Detailed Instructions:

Step 1
Run update command to update package repositories and get latest package 
information.
sudo apt-get update -y

Step 2
Run the install command with -y flag to quickly install the packages and 
dependencies.
sudo apt-get install -y gvfs-backends

Its all and fix the error

** Affects: sgml-base (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Samba Bug delete gvfs-backends

Status in sgml-base package in Ubuntu:
  New

Bug description:
  Other Bug in the 18.04 Distribution I explain the cause of this error

  About 3 months ago install samba all be good but delete the samba application 
but have and error 
  a dialog box appears when I click in search net a circle red and tell me 
impossible mount /

  I search in the net and the problem resolve in this form:

  userspace virtual filesystem - backends
  gvfs is a userspace virtual filesystem where mounts run as separate processes 
which you talk to via D-Bus. It also contains a gio module that seamlessly adds 
gvfs support to all applications using the gio API. It also supports exposing 
the gvfs mounts to non-gio applications using fuse. userspace virtual 
filesystem - backends
  gvfs is a userspace virtual filesystem where mounts run as separate processes 
which you talk to via D-Bus. It also contains a gio module that seamlessly adds 
gvfs support to all applications using the gio API. It also supports exposing 
the gvfs mounts to non-gio applications using fuse.

  Detailed Instructions:

  Step 1
  Run update command to update package repositories and get latest package 
information.
  sudo apt-get update -y

  Step 2
  Run the install command with -y flag to quickly install the packages and 
dependencies.
  sudo apt-get install -y gvfs-backends

  Its all and fix the error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/1880340/+subscriptions

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

[Desktop-packages] [Bug 1870250] [NEW] Brightness control works in a inconsistent manner using modesetting

[Leonardo Müller]

Public bug reported:

When using the combination of modesetting Xorg driver with Intel GVT-g
enabled, it was observed problems with brightness control.

While the brightness control still has functionality, it works with
significant delay for every change. Every change takes roughly half a
second, making the change from zero to full brightness using the
keyboard shortcuts take more than 10 seconds. The brightness keys are
buffered too, making it hard to reach intermediate values.

The attached video show the problem being reproduced using xfce4-power-
manager notification on the xfce4-panel.

This problem wasn't observed when using the Intel Xorg driver and this
problem doesn't happen if modesetting is used without iGVT-g.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-core 2:1.20.7-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
BootLog:
 
CompositorRunning: None
Date: Wed Apr  1 21:02:21 2020
DistUpgraded: 2019-12-22 18:50:28,852 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822]
InstallationDate: Installed on 2017-06-13 (1023 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 80UG
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 
i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 mtrr_gran_size=64M 
mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63
SourcePackage: xorg-server
UpgradeStatus: Upgraded to focal on 2019-12-22 (101 days ago)
dmi.bios.date: 08/09/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80UG
dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK
dmi.product.version: Lenovo ideapad 310-14ISK
dmi.sys.vendor: LENOVO
mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Brightness control works in a inconsistent manner using modesetting

Status in xorg-server package in Ubuntu:
  New

Bug description:
  When using the combination of modesetting Xorg driver with Intel GVT-g
  enabled, it was observed problems with brightness control.

  While the brightness control still has functionality, it works with
  significant delay for every change. Every change takes roughly half a
  second, making the change from zero to full brightness using the
  keyboard shortcuts take more than 10 seconds. The brightness keys are
  buffered too, making it hard to reach intermediate values.

  The attached video show the problem being reproduced using xfce4
  -power-manager notification on the xfce4-panel.

  This problem wasn't observed when using the Intel Xorg driver and this
  problem doesn't happen if modesetting is used without iGVT-g.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  Date: Wed Apr  1 21:02:21 2020
  DistUpgraded: 2019-12-22 

[Desktop-packages] [Bug 1870250] Re: Brightness control works in a inconsistent manner using modesetting

[Leonardo Müller]

** Attachment added: "Video reproducing the problem using xfce4-power-manager"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870250/+attachment/5344513/+files/TEST002.mkv

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

Title:
  Brightness control works in a inconsistent manner using modesetting

Status in xorg-server package in Ubuntu:
  New

Bug description:
  When using the combination of modesetting Xorg driver with Intel GVT-g
  enabled, it was observed problems with brightness control.

  While the brightness control still has functionality, it works with
  significant delay for every change. Every change takes roughly half a
  second, making the change from zero to full brightness using the
  keyboard shortcuts take more than 10 seconds. The brightness keys are
  buffered too, making it hard to reach intermediate values.

  The attached video show the problem being reproduced using xfce4
  -power-manager notification on the xfce4-panel.

  This problem wasn't observed when using the Intel Xorg driver and this
  problem doesn't happen if modesetting is used without iGVT-g.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  Date: Wed Apr  1 21:02:21 2020
  DistUpgraded: 2019-12-22 18:50:28,852 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822]
  InstallationDate: Installed on 2017-06-13 (1023 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 
i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 mtrr_gran_size=64M 
mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to focal on 2019-12-22 (101 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1868116] Re: QEMU monitor no longer works

[Leonardo Müller]

Thank you for investigating this. I would bisect QEMU, but wouldn't
investigate its libraries. Consequently, I would never find the cause of
this problem.

For now, I am using -monitor telnet:127.0.0.1:5,server,nowait to
have access to the monitor on QEMU guests.

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

Title:
  QEMU monitor no longer works

Status in QEMU:
  New
Status in qemu package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  New

Bug description:
  Repro:
  VTE
  $ meson _build && ninja -C _build && ninja -C _build install

  qemu:
  $ ../configure --python=/usr/bin/python3 --disable-werror --disable-user 
--disable-linux-user --disable-docs --disable-guest-agent --disable-sdl 
--enable-gtk --disable-vnc --disable-xen --disable-brlapi --disable-fdt 
--disable-hax --disable-vde --disable-netmap --disable-rbd --disable-libiscsi 
--disable-libnfs --disable-smartcard --disable-libusb --disable-usb-redir 
--disable-seccomp --disable-glusterfs --disable-tpm --disable-numa 
--disable-opengl --disable-virglrenderer --disable-xfsctl --disable-vxhs 
--disable-slirp --disable-blobs --target-list=x86_64-softmmu --disable-rdma 
--disable-pvrdma --disable-attr --disable-vhost-net --disable-vhost-vsock 
--disable-vhost-scsi --disable-vhost-crypto --disable-vhost-user 
--disable-spice --disable-qom-cast-debug --disable-vxhs --disable-bochs 
--disable-cloop --disable-dmg --disable-qcow1 --disable-vdi --disable-vvfat 
--disable-qed --disable-parallels --disable-sheepdog --disable-avx2 
--disable-nettle --disable-gnutls --disable-capstone --disable-tools 
--disable-libpmem --disable-iconv --disable-cap-ng
  $ make

  Test:
  $ LD_LIBRARY_PATH=/usr/local/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH 
./build/x86_64-softmmu/qemu-system-x86_64 -enable-kvm --drive 
media=cdrom,file=http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/mini.iso
  - switch to monitor with CTRL+ALT+2
  - try to enter something

  Affects head of both usptream git repos.

  
  --- original bug ---

  It was observed that the QEMU console (normally accessible using
  Ctrl+Alt+2) accepts no input, so it can't be used. This is being
  problematic because there are cases where it's required to send
  commands to the guest, or key combinations that the host would grab
  (as Ctrl-Alt-F1 or Alt-F4).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: qemu 1:4.2-3ubuntu2
  Uname: Linux 5.6.0-rc6+ x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 12:16:31 2020
  Dependencies:

  InstallationDate: Installed on 2017-06-13 (1009 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID PIDPPID %CPU COMMAND
   qemu-system-x86 Sl+   1000  1000   34275   25235 29.2 qemu-system-x86_64 -m 
4G -cpu Skylake-Client -device virtio-vga,virgl=true,xres=1280,yres=720 -accel 
kvm -device nec-usb-xhci -serial vc -serial stdio -hda 
/home/usuario/Sistemas/androidx86.img -display gtk,gl=on -device usb-audio
   kvm-nx-lpage-re S0 0   34284   2  0.0 [kvm-nx-lpage-re]
   kvm-pit/34275   S0 0   34286   2  0.0 [kvm-pit/34275]
  MachineType: LENOVO 80UG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-rc6+ 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 
i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 
zswap.enabled=1 zswap.zpool=z3fold 
resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M 
usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y 
scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 
nbd.max_part=63
  SourcePackage: qemu
  UpgradeStatus: Upgraded to focal on 2019-12-22 (87 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240

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

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

[Desktop-packages] [Bug 1867319] Re: Can not access desktop after switching user: stuck at "authentication required to refresh system repositories"

[leonardo]

Edit on the previous comments, the processes are not owned by the user,
processes are owned by root but ps  returns several lines like:

/usr/lib/policykit-1/polkit-agent-helper-1 USERNAME

where USERNAME is the user that gets stuck

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

Title:
  Can not access desktop after switching user: stuck at "authentication
  required to refresh system repositories"

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  When switching from the user (sudo-enabled) I normally use to another one 
(which I rarely use, and is also sudo-enabled), I can not access the desktop. 
  A window opens blocking the whole screen and asking the user password (the 
second user), whatever I type, the window does not close (see screenshot). In 
some cases after a random number of times I push "cancel" the window 
disappears, but not all the times.

  
  Steps to reproduce the bug:
   - switch from user A to user B
   - enter password in gdm, log-in is successful
   - update window opens and never disappears. I can not access the desktop.

  To exit this situation I need to change desktop with CTRL+ALT+F4 and
  log-in again with user A, which works. If I switch to user B again I
  am stuck again.

  Note that after this happens, I updated/upgraded repositories using
  user A and the window will be still there when switching to user B.

  
  What you expected to happen:
   - If I enter the user password the window should do something (start 
updating) but instead it produces an error (something on the line "This did not 
work") and the window remains there
   - If I push "cancel" the window remains there, only in some cases it did 
disappear after clicking cancel many times (tens of times)

  I'v seen this page describing something similar, but I don't have xRDP
  installed

  https://c-nergy.be/blog/?p=14051

  $ dpkg -l| grep -i xrdp
  $ 


  Ubuntu Version: packages updated to March 13 2020.
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  GNOME: 3.34.2
  Graphics: Intel UHD Graphics (Whiskey Lake 3x8 GT2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1867319/+subscriptions

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

[Desktop-packages] [Bug 1867319] Re: Can not access desktop after switching user: stuck at "authentication required to refresh system repositories"

[leonardo]

I see that the user has tens of /usr/lib/policykit-1/polkit-agent-
helper-1 processes running, which seems to be part of the policykit-1
package


** Package changed: ubuntu => policykit-1 (Ubuntu)

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

Title:
  Can not access desktop after switching user: stuck at "authentication
  required to refresh system repositories"

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  When switching from the user (sudo-enabled) I normally use to another one 
(which I rarely use, and is also sudo-enabled), I can not access the desktop. 
  A window opens blocking the whole screen and asking the user password (the 
second user), whatever I type, the window does not close (see screenshot). In 
some cases after a random number of times I push "cancel" the window 
disappears, but not all the times.

  
  Steps to reproduce the bug:
   - switch from user A to user B
   - enter password in gdm, log-in is successful
   - update window opens and never disappears. I can not access the desktop.

  To exit this situation I need to change desktop with CTRL+ALT+F4 and
  log-in again with user A, which works. If I switch to user B again I
  am stuck again.

  Note that after this happens, I updated/upgraded repositories using
  user A and the window will be still there when switching to user B.

  
  What you expected to happen:
   - If I enter the user password the window should do something (start 
updating) but instead it produces an error (something on the line "This did not 
work") and the window remains there
   - If I push "cancel" the window remains there, only in some cases it did 
disappear after clicking cancel many times (tens of times)

  I'v seen this page describing something similar, but I don't have xRDP
  installed

  https://c-nergy.be/blog/?p=14051

  $ dpkg -l| grep -i xrdp
  $ 


  Ubuntu Version: packages updated to March 13 2020.
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  GNOME: 3.34.2
  Graphics: Intel UHD Graphics (Whiskey Lake 3x8 GT2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1867319/+subscriptions

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

[Desktop-packages] [Bug 1866982] [NEW] xfce4-screensaver is triggering a Xorg crash, backtrace suggests a xserver-xorg-video-intel problem

[Leonardo Müller]

Public bug reported:

xfce4-screensaver is triggering a Xorg crash. The bug report I did on
xfce bugzilla against xfce4-screensaver is:
https://bugzilla.xfce.org/show_bug.cgi?id=16528

The bug report there have the steps to reproduce, log files and the full
backtrace of Xorg when the crash happened.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-video-intel 2:2.99.917+git20190815-1
Uname: Linux 5.6.0-050600rc4-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
BootLog:
 
CompositorRunning: None
CurrentDesktop: XFCE
Date: Wed Mar 11 07:34:32 2020
DistUpgraded: 2019-12-22 18:50:28,852 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822]
InstallationDate: Installed on 2017-06-13 (1001 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 006: ID 0cf3:e360 Qualcomm Atheros Communications 
 Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 003: ID 0bda:57f9 Realtek Semiconductor Corp. EasyCamera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80UG
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-050600rc4-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 
i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 
zswap.enabled=1 zswap.zpool=z3fold 
resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M 
usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y 
scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 
nbd.max_part=63
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: Upgraded to focal on 2019-12-22 (79 days ago)
dmi.bios.date: 08/09/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80UG
dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK
dmi.product.version: Lenovo ideapad 310-14ISK
dmi.sys.vendor: LENOVO
mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal regression reproducible ubuntu

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

Title:
  xfce4-screensaver is triggering a Xorg crash, backtrace suggests a
  xserver-xorg-video-intel problem

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  xfce4-screensaver is triggering a Xorg crash. The bug report I did on
  xfce bugzilla against xfce4-screensaver is:
  https://bugzilla.xfce.org/show_bug.cgi?id=16528

  The bug report there have the steps to reproduce, log files and the
  full backtrace of Xorg when the crash happened.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20190815-1
  Uname: Linux 5.6.0-050600rc4-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Mar 11 07:34:32 2020
  DistUpgraded: 2019-12-22 18:50:28,852 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822]
  InstallationDate: Installed on 2017-06-13 (1001 days ago)
  InstallationMedia: Xubuntu 

[Desktop-packages] [Bug 1866732] [NEW] Unable to add policies on Chromium snap

[Leonardo Müller]

Public bug reported:

When using the Chromium snap, the policies located in the directory /etc
/chromium-browser/policies/managed/ are no longer being read. The
consequence is that the policies are not applied.

This is particularly problematic on, for example, public computers,
where browsing history and passwords may be saved, or on school
computers, where the dinosaur game will be easily available.

Is there another way I'm unaware of to add system-wide policies when
using the Chromium snap? If not, would it be possible to make the snap
read the settings in the /etc/chromium-browser/policies/managed/
directory? This would make the transition from deb to snap easier on
systems which are already configured with system-wide policies.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Unable to add policies on Chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When using the Chromium snap, the policies located in the directory
  /etc/chromium-browser/policies/managed/ are no longer being read. The
  consequence is that the policies are not applied.

  This is particularly problematic on, for example, public computers,
  where browsing history and passwords may be saved, or on school
  computers, where the dinosaur game will be easily available.

  Is there another way I'm unaware of to add system-wide policies when
  using the Chromium snap? If not, would it be possible to make the snap
  read the settings in the /etc/chromium-browser/policies/managed/
  directory? This would make the transition from deb to snap easier on
  systems which are already configured with system-wide policies.

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

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

[Desktop-packages] [Bug 1809737] Re: Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks xkb.c:2387)

[Leonardo Soares Müller]

This bug is happening on Ubuntu Focal Daily too.

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

Title:
  Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks
  xkb.c:2387)

Status in Onboard:
  New
Status in X.Org X server:
  New
Status in onboard package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Onboard 1.4.1 crashes the entire Desktop if I selected any alternate
  character from pop-up

  [bishop@fringe ~]$ ls /usr/share/xsessions/
  xfce.desktop

  [bishop@fringe ~]$ echo $XDG_CURRENT_DESKTOP
  XFCE

  [bishop@fringe ~]$ echo $XDG_SESSION_TYPE
  x11

  [bishop@fringe ~]$ cat /etc/*-release
  Fedora release 29 (Twenty Nine)
  NAME=Fedora
  VERSION="29 (Twenty Nine)"
  ID=fedora
  VERSION_ID=29
  VERSION_CODENAME=""
  PLATFORM_ID="platform:f29"
  PRETTY_NAME="Fedora 29 (Twenty Nine)"
  ANSI_COLOR="0;34"
  LOGO=fedora-logo-icon
  CPE_NAME="cpe:/o:fedoraproject:fedora:29"
  HOME_URL="https://fedoraproject.org/;
  
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/;
  SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help;
  BUG_REPORT_URL="https://bugzilla.redhat.com/;
  REDHAT_BUGZILLA_PRODUCT="Fedora"
  REDHAT_BUGZILLA_PRODUCT_VERSION=29
  REDHAT_SUPPORT_PRODUCT="Fedora"
  REDHAT_SUPPORT_PRODUCT_VERSION=29
  PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy;
  Fedora release 29 (Twenty Nine)
  Fedora release 29 (Twenty Nine)

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

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

[Desktop-packages] [Bug 1859113] [NEW] No support for Zstandard

[Leonardo Müller]

Public bug reported:

As stated on https://facebook.github.io/zstd/

"Zstandard is a real-time compression algorithm, providing high
compression ratios. It offers a very wide range of compression / speed
trade-off, while being backed by a very fast decoder".

Other Linux distributions even started to use the Zstandard in the place
of xz compression for their packages due to how fast the decompression
is, even if there is a small penalty on ratio. On my own testing, I
noticed 17% faster compression and 88% faster decompression compared to
xz while there was a 3% differences on compression ratio for system
images.

With this bug report, I ask to add support for Zstandard on at least
file-roller. Currently, I have to use the command line tool zstd to work
with files compressed using Zstandard. On Thunar, *.zst files appear as
unknown and file-roller says there is no support for this file type.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: file-roller 3.32.2-1
Uname: Linux 4.19.93-041969 x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jan  9 22:59:56 2020
InstallationDate: Installed on 2017-06-13 (940 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: file-roller
UpgradeStatus: Upgraded to focal on 2019-12-22 (18 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  No support for Zstandard

Status in file-roller package in Ubuntu:
  New

Bug description:
  As stated on https://facebook.github.io/zstd/

  "Zstandard is a real-time compression algorithm, providing high
  compression ratios. It offers a very wide range of compression / speed
  trade-off, while being backed by a very fast decoder".

  Other Linux distributions even started to use the Zstandard in the
  place of xz compression for their packages due to how fast the
  decompression is, even if there is a small penalty on ratio. On my own
  testing, I noticed 17% faster compression and 88% faster decompression
  compared to xz while there was a 3% differences on compression ratio
  for system images.

  With this bug report, I ask to add support for Zstandard on at least
  file-roller. Currently, I have to use the command line tool zstd to
  work with files compressed using Zstandard. On Thunar, *.zst files
  appear as unknown and file-roller says there is no support for this
  file type.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: file-roller 3.32.2-1
  Uname: Linux 4.19.93-041969 x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jan  9 22:59:56 2020
  InstallationDate: Installed on 2017-06-13 (940 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: file-roller
  UpgradeStatus: Upgraded to focal on 2019-12-22 (18 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1859113/+subscriptions

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

[Desktop-packages] [Bug 1855626] Re: All sound halts for one minute at midnight on Mondays

[Leonardo Jeanteur]

As this happened again, and I paid more attention to the time, it seems
that the sound doesn't halt exactly at midnight, but rather during the
first minute of Monday.

All happenings of this but were between 00:00:00 and 00:00:59 so far

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

Title:
  All sound halts for one minute at midnight on Mondays

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Every week, on Monday at 00:00 all sound halts until the clock turns to 00:01.
  (Note as I often get confused with midnight/midday notations, I am referring 
to the minute after Sunday 23:59).

  When this happened the rhythmbox process had been running for more
  than a day, and I do not know if this happens if rhythmbox was
  launched on Sunday.

  I can confirm at the very least that this happened twice when the process was 
started on the previous Wednesday, and once on the previous Friday at 12:12.
  This bug happened to me many more times, but I did not check the process' 
information those times.

  The song timer stops during this minute.
  The last time this happened the song skipped a minute when it resumed, but 
from what I remember of the previous times the song had started off where it 
stopped (I could remember wrong though). The only difference I can think of 
between the last occurrence and the previous ones would be that I did not use 
any buttons this time around.

  
  What I expected to happen:
  The current song keeps playing
  What happened instead:
  The song halted for one minute

  Steps to reproduce:
  #1 Open Rhythmbox (if possible not on Sunday)
  #2 Wait for Sunday
  #3 Start listening to music before Sunday 23:59:59
  #4 Wait for Monday 00:00 while music is still playing
  The song will stop until 00:01

  ```
  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  $ apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.2-4ubuntu1
Candidate: 3.4.2-4ubuntu1
Version table:
   *** 3.4.2-4ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  ```
  Processor: Intel® Core™ i7-6600U CPU @ 2.60GHz × 4 
  GNOME: 3.28.2

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

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

[Desktop-packages] [Bug 1855626] [NEW] All sound halts for one minute at midnight on Mondays

[Leonardo Jeanteur]

Public bug reported:

Every week, on Monday at 00:00 all sound halts until the clock turns to 00:01.
(Note as I often get confused with midnight/midday notations, I am referring to 
the minute after Sunday 23:59).

When this happened the rhythmbox process had been running for more than
a day, and I do not know if this happens if rhythmbox was launched on
Sunday.

I can confirm at the very least that this happened twice when the process was 
started on the previous Wednesday, and once on the previous Friday at 12:12.
This bug happened to me many more times, but I did not check the process' 
information those times.

The song timer stops during this minute.
The last time this happened the song skipped a minute when it resumed, but from 
what I remember of the previous times the song had started off where it stopped 
(I could remember wrong though). The only difference I can think of between the 
last occurrence and the previous ones would be that I did not use any buttons 
this time around.


What I expected to happen:
The current song keeps playing
What happened instead:
The song halted for one minute

Steps to reproduce:
#1 Open Rhythmbox (if possible not on Sunday)
#2 Wait for Sunday
#3 Start listening to music before Sunday 23:59:59
#4 Wait for Monday 00:00 while music is still playing
The song will stop until 00:01

```
$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04

$ apt-cache policy rhythmbox
rhythmbox:
  Installed: 3.4.2-4ubuntu1
  Candidate: 3.4.2-4ubuntu1
  Version table:
 *** 3.4.2-4ubuntu1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
```
Processor: Intel® Core™ i7-6600U CPU @ 2.60GHz × 4 
GNOME: 3.28.2

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

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

Title:
  All sound halts for one minute at midnight on Mondays

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Every week, on Monday at 00:00 all sound halts until the clock turns to 00:01.
  (Note as I often get confused with midnight/midday notations, I am referring 
to the minute after Sunday 23:59).

  When this happened the rhythmbox process had been running for more
  than a day, and I do not know if this happens if rhythmbox was
  launched on Sunday.

  I can confirm at the very least that this happened twice when the process was 
started on the previous Wednesday, and once on the previous Friday at 12:12.
  This bug happened to me many more times, but I did not check the process' 
information those times.

  The song timer stops during this minute.
  The last time this happened the song skipped a minute when it resumed, but 
from what I remember of the previous times the song had started off where it 
stopped (I could remember wrong though). The only difference I can think of 
between the last occurrence and the previous ones would be that I did not use 
any buttons this time around.

  
  What I expected to happen:
  The current song keeps playing
  What happened instead:
  The song halted for one minute

  Steps to reproduce:
  #1 Open Rhythmbox (if possible not on Sunday)
  #2 Wait for Sunday
  #3 Start listening to music before Sunday 23:59:59
  #4 Wait for Monday 00:00 while music is still playing
  The song will stop until 00:01

  ```
  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  $ apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.2-4ubuntu1
Candidate: 3.4.2-4ubuntu1
Version table:
   *** 3.4.2-4ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  ```
  Processor: Intel® Core™ i7-6600U CPU @ 2.60GHz × 4 
  GNOME: 3.28.2

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

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

[Desktop-packages] [Bug 1848741] Re: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge)

[Leonardo da Silva]

This bug happens on ryzen 3400g with onboard graphics
the comment #23 solved my problem

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

Title:
  [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen
  2500u (Raven Ridge)

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  I have graphics artefacts: screan tearing, pieces of the previous window 
appear in the newly opened window.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-08 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1765775] Re: Window decoration becomes very large if the image has much more height than width

[Leonardo Müller]

The following image is triggering the bug:
https://i.imgur.com/To30M5D.png

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

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

Title:
  Window decoration becomes very large if the image has much more height
  than width

Status in eog package in Ubuntu:
  New

Bug description:
  When a image with much higher height than width is opened, the window
  decoration becomes very big, as it tries to keep the image
  proportional: https://i.imgur.com/SZu0lOk.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: eog 3.28.1-1
  Uname: Linux 4.16.3-041603-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Apr 20 13:08:37 2018
  InstallationDate: Installed on 2017-06-13 (310 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: eog
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (182 days ago)

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

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

[Desktop-packages] [Bug 1809737] Re: Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks xkb.c:2387)

[Leonardo Soares Müller]

I did a build applying the patch (fortunately no GTK 3 build was
required) and I was testing with one offending netbook.

The crash no longer happens when using the patched onboard version, and
I noticed that after I ran and added a letter with accent at least once
with the patched version, the onboard version from the repositories also
works.

However, there is a bug where the keyboard layout changes as I write it
and some letters add the wrong characters. The attached video shows the
problem, notice what happens with the "ç" character.

** Attachment added: "Video showing the keyboard layout problem"
   
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1809737/+attachment/5303916/+files/newonboard2.mkv

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

Title:
  Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks
  xkb.c:2387)

Status in Onboard:
  New
Status in X.Org X server:
  New
Status in onboard package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Onboard 1.4.1 crashes the entire Desktop if I selected any alternate
  character from pop-up

  [bishop@fringe ~]$ ls /usr/share/xsessions/
  xfce.desktop

  [bishop@fringe ~]$ echo $XDG_CURRENT_DESKTOP
  XFCE

  [bishop@fringe ~]$ echo $XDG_SESSION_TYPE
  x11

  [bishop@fringe ~]$ cat /etc/*-release
  Fedora release 29 (Twenty Nine)
  NAME=Fedora
  VERSION="29 (Twenty Nine)"
  ID=fedora
  VERSION_ID=29
  VERSION_CODENAME=""
  PLATFORM_ID="platform:f29"
  PRETTY_NAME="Fedora 29 (Twenty Nine)"
  ANSI_COLOR="0;34"
  LOGO=fedora-logo-icon
  CPE_NAME="cpe:/o:fedoraproject:fedora:29"
  HOME_URL="https://fedoraproject.org/;
  
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/;
  SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help;
  BUG_REPORT_URL="https://bugzilla.redhat.com/;
  REDHAT_BUGZILLA_PRODUCT="Fedora"
  REDHAT_BUGZILLA_PRODUCT_VERSION=29
  REDHAT_SUPPORT_PRODUCT="Fedora"
  REDHAT_SUPPORT_PRODUCT_VERSION=29
  PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy;
  Fedora release 29 (Twenty Nine)
  Fedora release 29 (Twenty Nine)

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

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

[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive

[Leonardo Soares Müller]

There are some computers and configurations I manage which rely on some
of these drivers:

evdev: there are some netbooks which have touchscreens that only work
with evdev, being detected by libinput but doing nothing. While this is
a libinput limitation, removing evdev would limit the netbooks'
capabilities: the touchscreen can be greatly beneficial, especially when
used with programs which can be centered on this type of interactivity
(ArduBlock is one example).

siliconmotion: some years ago, thousands of computers were bought with
PCI GPUs that use siliconmotion graphics. While some of these old
computers are unusable today, the GPUs aren't and can be installed and
used on new computers. These new computers have specifications good
enough to allow up to 5 seats for a single computer, greatly reducing
costs associated with keeping a laboratory, both by reduced initial
investment and reduced power usage.

I am worried: abandoning evdev would make some touchscreens stop
working, as libinput does not support those properly. Abandoning
siliconmotion would make certain multiseat configurations stop working,
making, for example, one laboratories with 8 computers for 22 seats
require buying additional 14 computers to replace what is going to stop
working.

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

Title:
  Remove obsolete X11 drivers from the archive

Status in xf86-input-mtrack package in Ubuntu:
  Incomplete
Status in xf86-input-xwiimote package in Ubuntu:
  New
Status in xserver-xorg-input-aiptek package in Ubuntu:
  New
Status in xserver-xorg-input-elographics package in Ubuntu:
  New
Status in xserver-xorg-input-evdev package in Ubuntu:
  Invalid
Status in xserver-xorg-input-keyboard package in Ubuntu:
  New
Status in xserver-xorg-input-mouse package in Ubuntu:
  New
Status in xserver-xorg-input-mutouch package in Ubuntu:
  New
Status in xserver-xorg-input-void package in Ubuntu:
  New
Status in xserver-xorg-video-ast package in Ubuntu:
  Triaged
Status in xserver-xorg-video-geode package in Ubuntu:
  New
Status in xserver-xorg-video-mach64 package in Ubuntu:
  New
Status in xserver-xorg-video-neomagic package in Ubuntu:
  New
Status in xserver-xorg-video-r128 package in Ubuntu:
  New
Status in xserver-xorg-video-savage package in Ubuntu:
  New
Status in xserver-xorg-video-siliconmotion package in Ubuntu:
  New
Status in xserver-xorg-video-sisusb package in Ubuntu:
  New
Status in xserver-xorg-video-tdfx package in Ubuntu:
  New
Status in xserver-xorg-video-trident package in Ubuntu:
  New

Bug description:
  xserver-xorg-video-all has not depended on these drivers for quite
  some time now, meaning that installation images didn't have them
  either nor installed them on the system. Now would be the time to drop
  them from the archive before next LTS & HWE-18.04 stack and in
  preparation for xserver 1.20.

  Some rationale in detail for future reference:
  input:
  -aiptek: no upstream release in 7 years
  -elographics: no upstream release in 6 years
  -evdev: replaced by -libinput (not entirely, see comment #1)
  -keyboard: replaced by -libinput
  -mtrack: no upstream release in 3 years, should be replaceable by -libinput 
by now
  -mouse: replaced by -libinput
  -mutouch: no upstream release in 7 years
  -void: xserver can start without an input driver these days
  -xwiimote: no upstream release in 5 years
  video:
  -ast: no upstream release in 3 years, no KMS support
  -geode: i386 only, no kernel support since moving to i586 (or i686?)
  -mach64: no KMS support
  -neomagic: no upstream release in 3 years, no KMS support
  -r128: no KMS support
  -savage: no KMS support
  -siliconmotion: no KMS suppport
  -sisusb: no KMS support
  -tdfx: no KMS support
  -trident: no KMS support

  Fedora dropped drivers without KMS (kernel modesetting) support five years 
ago:
  https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html

  one exception to this is -openchrome, which we'll keep since it has
  some users and might even get KMS support before next LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions

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

[Desktop-packages] [Bug 1809737] Re: Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks xkb.c:2387)

[Leonardo Soares Müller]

Is there a packaged version available with the fix for this bug? I'll
have one problematic machine for a few days so I can test. However, it
is an Intel Atom netbook, unlikely to be successful building onboard
directly on it.

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

Title:
  Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks
  xkb.c:2387)

Status in Onboard:
  New
Status in X.Org X server:
  New
Status in onboard package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Onboard 1.4.1 crashes the entire Desktop if I selected any alternate
  character from pop-up

  [bishop@fringe ~]$ ls /usr/share/xsessions/
  xfce.desktop

  [bishop@fringe ~]$ echo $XDG_CURRENT_DESKTOP
  XFCE

  [bishop@fringe ~]$ echo $XDG_SESSION_TYPE
  x11

  [bishop@fringe ~]$ cat /etc/*-release
  Fedora release 29 (Twenty Nine)
  NAME=Fedora
  VERSION="29 (Twenty Nine)"
  ID=fedora
  VERSION_ID=29
  VERSION_CODENAME=""
  PLATFORM_ID="platform:f29"
  PRETTY_NAME="Fedora 29 (Twenty Nine)"
  ANSI_COLOR="0;34"
  LOGO=fedora-logo-icon
  CPE_NAME="cpe:/o:fedoraproject:fedora:29"
  HOME_URL="https://fedoraproject.org/;
  
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/;
  SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help;
  BUG_REPORT_URL="https://bugzilla.redhat.com/;
  REDHAT_BUGZILLA_PRODUCT="Fedora"
  REDHAT_BUGZILLA_PRODUCT_VERSION=29
  REDHAT_SUPPORT_PRODUCT="Fedora"
  REDHAT_SUPPORT_PRODUCT_VERSION=29
  PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy;
  Fedora release 29 (Twenty Nine)
  Fedora release 29 (Twenty Nine)

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

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

[Desktop-packages] [Bug 1841190] Re: Xorg crashes when trying to insert letter with accent using Onboard

[Leonardo Soares Müller]

It seems I got a valid backtrace. I installed xserver-xorg-core-
hwe-18.04-dbgsym and it was possible to get a backtrace with more data.
Here is it:

(gdb) bt f
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
set = {__val = {171516928, 0, 0, 0, 0, 94568085079104, 94568054863600, 
67108868, 140083657316496, 0, 94568084835824, 94568085157664, 94568085157664, 
94568085534016, 0, 0}}
pid = 
tid = 
ret = 
#1  0x7f67c465e801 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x5602591f7720, sa_sigaction 
= 0x5602591f7720}, sa_mask = {__val = {94568085534016, 0 , 
67108868, 140083657316496, 5467293301926151424, 0}}, sa_flags = 1465188592, 
sa_restorer = 0x7ffc2f5ddeb0}
sigs = {__val = {32, 0 }}
__cnt = 
__set = 
__cnt = 
__set = 
#2  0x5602575166da in OsAbort () at ../../../../os/utils.c:1351
No locals.
#3  0x56025751c273 in AbortServer () at ../../../../os/log.c:879
No locals.
#4  0x56025751d095 in FatalError (f=f@entry=0x5602575500f0 "Caught signal 
%d (%s). Server aborting\n") at ../../../../os/log.c:1017
args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 
0x7ffc2f5ddfa0, reg_save_area = 0x7ffc2f5dded0}}
args2 = {{gp_offset = 8, fp_offset = 48, overflow_arg_area = 
0x7ffc2f5ddfa0, reg_save_area = 0x7ffc2f5dded0}}
beenhere = 1
#5  0x560257513773 in OsSigHandler (signo=11, sip=, 
unused=) at ../../../../os/osinit.c:156
unused = 
sip = 
signo = 11
#6  
No locals.
#7  _XkbSetMapChecks (client=client@entry=0x560259cd7c40, 
req=req@entry=0x56025a1b4dd0, values=values@entry=0x56025a1b4df4 "", 
dev=) at ../../../../xkb/xkb.c:2387
xkbi = 
xkb = 
error = 
nTypes = 0
nActions = 
mapWidths = '\000' 
symsPerKey = {0 }
map = 
i = 
#8  0x5602574b734f in ProcXkbSetMap (client=0x560259cd7c40) at 
../../../../xkb/xkb.c:2655
other = 0x560258ea7d40
dev = 0x560258ea84d0
tmp = 0x56025a1b4df4 ""
rc = 0
stuff = 
master = 0x560258ea84d0
#9  0x5602573b64e8 in Dispatch () at ../../../../dix/dispatch.c:478
result = 
client = 
start_tick = 1390
#10 0x5602573ba4e8 in dix_main (argc=11, argv=0x7ffc2f5de988, 
envp=) at ../../../../dix/main.c:276
i = 
alwaysCheckForInput = {0, 1}
#11 0x7f67c463fb97 in __libc_start_main (main=0x5602573a4150 , 
argc=11, argv=0x7ffc2f5de988, init=, fini=, 
rtld_fini=, stack_end=0x7ffc2f5de978) at ../csu/libc-start.c:310
self = 
__self = 
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, -957471381706168478, 
94568053358944, 140721103169920, 0, 0, -6824483104159357086, 
-6882266889145079966}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 
0x7f67c7364733 <_dl_init+259>, 0x7f67c7352438}, data = {prev = 0x0, cleanup = 
0x0, canceltype = -952744141}}}
not_first_call = 
#12 0x5602573a418a in _start ()
No symbol table info available.

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

Title:
  Xorg crashes when trying to insert letter with accent using Onboard

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Using Onboard, when trying to type a letter with accent, as á or à,
  Xorg crashes. This computer has a touch screen: some of its software
  is intended to be used with the touch screen and, as the screen can be
  rotated independently from the keyboard, the physical keyboard is not
  always available.

  As in Portuguese many words have accents, this crash would be
  extremely common.

  Regarding Xorg, I had to add the following settings to enable the
  touch screen:

  Section "InputClass"
  Identifier "HID Touchscreen"
  MatchUSBID "22b9:0005"
  Driver "evdev"
  Option "Emulate3Buttons" "false"
  Option "ButtonMapping" "1 0 0 0 0 0 0 0 0 0 0 0 0 0"
  EndSection

  Regarding Onboard, only the theme was changed.

  The operating system is Xubuntu 18.04 amd64. lspci -v output is below:

  lspci -v
  00:00.0 Host bridge: Intel Corporation Atom Processor D2xxx/N2xxx DRAM 
Controller (rev 04)
Subsystem: Elitegroup Computer Systems Atom Processor D2xxx/N2xxx DRAM 
Controller
Flags: bus master, fast devsel, latency 0

  00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
D2xxx/N2xxx Integrated Graphics Controller (rev 0b) (prog-if 00 [VGA 
controller])
Subsystem: Elitegroup Computer Systems Atom Processor D2xxx/N2xxx 
Integrated Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 26
Memory at 8020 (32-bit, non-prefetchable) [size=1M]
I/O ports at 40d0 [size=8]
[virtual] Expansion ROM at 000c 

[Desktop-packages] [Bug 1841190] Re: Xorg crashes when trying to insert letter with accent using Onboard

[Leonardo Soares Müller]

I sent a new report: it's bug 1841507, hopefully the data is good now.

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

Title:
  Xorg crashes when trying to insert letter with accent using Onboard

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Using Onboard, when trying to type a letter with accent, as á or à,
  Xorg crashes. This computer has a touch screen: some of its software
  is intended to be used with the touch screen and, as the screen can be
  rotated independently from the keyboard, the physical keyboard is not
  always available.

  As in Portuguese many words have accents, this crash would be
  extremely common.

  Regarding Xorg, I had to add the following settings to enable the
  touch screen:

  Section "InputClass"
  Identifier "HID Touchscreen"
  MatchUSBID "22b9:0005"
  Driver "evdev"
  Option "Emulate3Buttons" "false"
  Option "ButtonMapping" "1 0 0 0 0 0 0 0 0 0 0 0 0 0"
  EndSection

  Regarding Onboard, only the theme was changed.

  The operating system is Xubuntu 18.04 amd64. lspci -v output is below:

  lspci -v
  00:00.0 Host bridge: Intel Corporation Atom Processor D2xxx/N2xxx DRAM 
Controller (rev 04)
Subsystem: Elitegroup Computer Systems Atom Processor D2xxx/N2xxx DRAM 
Controller
Flags: bus master, fast devsel, latency 0

  00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
D2xxx/N2xxx Integrated Graphics Controller (rev 0b) (prog-if 00 [VGA 
controller])
Subsystem: Elitegroup Computer Systems Atom Processor D2xxx/N2xxx 
Integrated Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 26
Memory at 8020 (32-bit, non-prefetchable) [size=1M]
I/O ports at 40d0 [size=8]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: 
Kernel driver in use: gma500
Kernel modules: gma500_gfx

  00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller (rev 02)
Subsystem: Elitegroup Computer Systems NM10/ICH7 Family High Definition 
Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 27
Memory at 8030 (64-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 
(rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 16
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 3000-3fff
Memory behind bridge: 8040-807f
Prefetchable memory behind bridge: 8000-800f
Capabilities: 
Kernel driver in use: pcieport

  00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 
(rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 17
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 2000-2fff
Memory behind bridge: 8010-801f
Prefetchable memory behind bridge: 8080-809f
Capabilities: 
Kernel driver in use: pcieport

  00:1c.2 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 3 
(rev 02) (prog-if 00 [Normal decode])
Flags: fast devsel, IRQ 18
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 5000-5fff
Memory behind bridge: 80a0-80bf
Prefetchable memory behind bridge: 80c0-80df
Capabilities: 
Kernel driver in use: pcieport

  00:1c.3 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 4 
(rev 02) (prog-if 00 [Normal decode])
Flags: fast devsel, IRQ 19
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 6000-6fff
Memory behind bridge: 80e0-80ff
Prefetchable memory behind bridge: 8100-811f
Capabilities: 
Kernel driver in use: pcieport

  00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI 
Controller #1 (rev 02) (prog-if 00 [UHCI])
Subsystem: Elitegroup Computer Systems NM10/ICH7 Family USB UHCI 
Controller
Flags: bus master, medium devsel, latency 0, IRQ 23
I/O ports at 40a0 [size=32]
Kernel driver in use: uhci_hcd

  00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI 
Controller #2 (rev 02) (prog-if 00 [UHCI])
Subsystem: Elitegroup Computer Systems NM10/ICH7 Family USB UHCI 
Controller
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at 4080 [size=32]
Kernel driver 

[Desktop-packages] [Bug 1841190] Re: Xorg crashes when trying to insert letter with accent using Onboard

[Leonardo Soares Müller]

I had to use the step 3 to be able to report the bug. The .crash file
was uploaded to bug 1841428.

I noticed there is a backtrace in /var/log/Xorg.0.log.old which seems it
was not uploaded. I'm not sure it is relevant, but here is the
backtrace:

[   161.631] (EE) 
[   161.632] (EE) Backtrace:
[   161.690] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55e3d383e829]
[   161.692] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) 
[0x7f45de62a8df]
[   161.693] (EE) 2: /usr/lib/xorg/Xorg (XkbCompileKeymapFromString+0x229d) 
[0x55e3d37dd00d]
[   161.694] (EE) 3: /usr/lib/xorg/Xorg (XkbCompileKeymapFromString+0x982f) 
[0x55e3d37eba1f]
[   161.695] (EE) 4: /usr/lib/xorg/Xorg (SendErrorToClient+0x368) 
[0x55e3d36e1548]
[   161.695] (EE) 5: /usr/lib/xorg/Xorg (InitFonts+0x3c8) [0x55e3d36e5528]
[   161.698] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) 
[0x7f45de248b97]
[   161.698] (EE) 7: /usr/lib/xorg/Xorg (_start+0x2a) [0x55e3d36cf18a]
[   161.699] (EE) 
[   161.699] (EE) Segmentation fault at address 0x68
[   161.699] (EE) 
Fatal server error:
[   161.699] (EE) Caught signal 11 (Segmentation fault). Server aborting

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

Title:
  Xorg crashes when trying to insert letter with accent using Onboard

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Using Onboard, when trying to type a letter with accent, as á or à,
  Xorg crashes. This computer has a touch screen: some of its software
  is intended to be used with the touch screen and, as the screen can be
  rotated independently from the keyboard, the physical keyboard is not
  always available.

  As in Portuguese many words have accents, this crash would be
  extremely common.

  Regarding Xorg, I had to add the following settings to enable the
  touch screen:

  Section "InputClass"
  Identifier "HID Touchscreen"
  MatchUSBID "22b9:0005"
  Driver "evdev"
  Option "Emulate3Buttons" "false"
  Option "ButtonMapping" "1 0 0 0 0 0 0 0 0 0 0 0 0 0"
  EndSection

  Regarding Onboard, only the theme was changed.

  The operating system is Xubuntu 18.04 amd64. lspci -v output is below:

  lspci -v
  00:00.0 Host bridge: Intel Corporation Atom Processor D2xxx/N2xxx DRAM 
Controller (rev 04)
Subsystem: Elitegroup Computer Systems Atom Processor D2xxx/N2xxx DRAM 
Controller
Flags: bus master, fast devsel, latency 0

  00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
D2xxx/N2xxx Integrated Graphics Controller (rev 0b) (prog-if 00 [VGA 
controller])
Subsystem: Elitegroup Computer Systems Atom Processor D2xxx/N2xxx 
Integrated Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 26
Memory at 8020 (32-bit, non-prefetchable) [size=1M]
I/O ports at 40d0 [size=8]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: 
Kernel driver in use: gma500
Kernel modules: gma500_gfx

  00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller (rev 02)
Subsystem: Elitegroup Computer Systems NM10/ICH7 Family High Definition 
Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 27
Memory at 8030 (64-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 
(rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 16
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 3000-3fff
Memory behind bridge: 8040-807f
Prefetchable memory behind bridge: 8000-800f
Capabilities: 
Kernel driver in use: pcieport

  00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 
(rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 17
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 2000-2fff
Memory behind bridge: 8010-801f
Prefetchable memory behind bridge: 8080-809f
Capabilities: 
Kernel driver in use: pcieport

  00:1c.2 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 3 
(rev 02) (prog-if 00 [Normal decode])
Flags: fast devsel, IRQ 18
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 5000-5fff
Memory behind bridge: 80a0-80bf
Prefetchable memory behind bridge: 80c0-80df
Capabilities: 
Kernel driver in use: pcieport

  

[Desktop-packages] [Bug 1841190] [NEW] Xorg crashes when trying to insert letter with accent using Onboard

[Leonardo Soares Müller]

Public bug reported:

Using Onboard, when trying to type a letter with accent, as á or à, Xorg
crashes. This computer has a touch screen: some of its software is
intended to be used with the touch screen and, as the screen can be
rotated independently from the keyboard, the physical keyboard is not
always available.

As in Portuguese many words have accents, this crash would be extremely
common.

Regarding Xorg, I had to add the following settings to enable the touch
screen:

Section "InputClass"
Identifier "HID Touchscreen"
MatchUSBID "22b9:0005"
Driver "evdev"
Option "Emulate3Buttons" "false"
Option "ButtonMapping" "1 0 0 0 0 0 0 0 0 0 0 0 0 0"
EndSection

Regarding Onboard, only the theme was changed.

The operating system is Xubuntu 18.04 amd64. lspci -v output is below:

lspci -v
00:00.0 Host bridge: Intel Corporation Atom Processor D2xxx/N2xxx DRAM 
Controller (rev 04)
Subsystem: Elitegroup Computer Systems Atom Processor D2xxx/N2xxx DRAM 
Controller
Flags: bus master, fast devsel, latency 0

00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx 
Integrated Graphics Controller (rev 0b) (prog-if 00 [VGA controller])
Subsystem: Elitegroup Computer Systems Atom Processor D2xxx/N2xxx 
Integrated Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 26
Memory at 8020 (32-bit, non-prefetchable) [size=1M]
I/O ports at 40d0 [size=8]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: 
Kernel driver in use: gma500
Kernel modules: gma500_gfx

00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio 
Controller (rev 02)
Subsystem: Elitegroup Computer Systems NM10/ICH7 Family High Definition 
Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 27
Memory at 8030 (64-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 
02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 16
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 3000-3fff
Memory behind bridge: 8040-807f
Prefetchable memory behind bridge: 8000-800f
Capabilities: 
Kernel driver in use: pcieport

00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 
02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 17
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 2000-2fff
Memory behind bridge: 8010-801f
Prefetchable memory behind bridge: 8080-809f
Capabilities: 
Kernel driver in use: pcieport

00:1c.2 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 3 (rev 
02) (prog-if 00 [Normal decode])
Flags: fast devsel, IRQ 18
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 5000-5fff
Memory behind bridge: 80a0-80bf
Prefetchable memory behind bridge: 80c0-80df
Capabilities: 
Kernel driver in use: pcieport

00:1c.3 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 4 (rev 
02) (prog-if 00 [Normal decode])
Flags: fast devsel, IRQ 19
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 6000-6fff
Memory behind bridge: 80e0-80ff
Prefetchable memory behind bridge: 8100-811f
Capabilities: 
Kernel driver in use: pcieport

00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller 
#1 (rev 02) (prog-if 00 [UHCI])
Subsystem: Elitegroup Computer Systems NM10/ICH7 Family USB UHCI 
Controller
Flags: bus master, medium devsel, latency 0, IRQ 23
I/O ports at 40a0 [size=32]
Kernel driver in use: uhci_hcd

00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller 
#2 (rev 02) (prog-if 00 [UHCI])
Subsystem: Elitegroup Computer Systems NM10/ICH7 Family USB UHCI 
Controller
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at 4080 [size=32]
Kernel driver in use: uhci_hcd

00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller 
#3 (rev 02) (prog-if 00 [UHCI])
Subsystem: Elitegroup Computer Systems NM10/ICH7 Family USB UHCI 
Controller
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at 4060 [size=32]
Kernel driver in use: uhci_hcd

00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller 

[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card

[Leonardo]

Same issue for me.

Ubuntu 18.04, lightdm
MSI GS65 Stealth, Geforce GTX 1660 Ti

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

Title:
  prime-select intel is not powering off the nvidia card

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Right now, it seems that prime-select intel makes sure the nvidia driver is 
not loaded, as nvidia-settings reports.
  But my power consumption is > 20W.
  cat /proc/acpi/bbswitch reports the card is still on. 

  
  If bbswitch and powertop are reliable, then the nvidia card is still powered.
  This is a thinkpad w520 in Optimus mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-prime 0.8.7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 19:56:21 2018
  Dependencies:
   
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-14 (125 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions

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

[Desktop-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

[Leonardo Castro]

I confirm this bug on 19.04. Wifi worked well on Ubuntu 16.04. Why
doesn't Ubuntu go back to whatever worked in 16.04?

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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

[Desktop-packages] [Bug 1818249] [NEW] Panel screen does not turn on after login if notebook was suspended by closing the lid

[Leonardo Müller]

Public bug reported:

On Xubuntu 18.04, if it's set on power manager settings to suspend the
notebook if the lid is closed, when it's open, the login screen appears
but after the login the screen turns off. It was observed with xrandr
that no resolution is set. To fix this, I have to do one of these three
actions:

1) Use the xrandr command blindly;
2) Restart LightDM from a TTY;
3) Reboot.

When suspending using the Whisker Menu or using systemctl suspend, the
notebook panel turns on normally after login. It's happening only when
suspending by closing the notebook lid. Maybe it detects no screen
connected and then unset all resolutions?

The notebook model page is: https://pcsupport.lenovo.com/br/pt/products
/laptops-and-netbooks/300-series/310-14isk/80ug/80ugbr

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar  1 12:24:33 2019
InstallationDate: Installed on 2017-06-13 (625 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: lightdm
UpgradeStatus: Upgraded to bionic on 2017-10-20 (497 days ago)

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

Title:
  Panel screen does not turn on after login if notebook was suspended by
  closing the lid

Status in lightdm package in Ubuntu:
  New

Bug description:
  On Xubuntu 18.04, if it's set on power manager settings to suspend the
  notebook if the lid is closed, when it's open, the login screen
  appears but after the login the screen turns off. It was observed with
  xrandr that no resolution is set. To fix this, I have to do one of
  these three actions:

  1) Use the xrandr command blindly;
  2) Restart LightDM from a TTY;
  3) Reboot.

  When suspending using the Whisker Menu or using systemctl suspend, the
  notebook panel turns on normally after login. It's happening only when
  suspending by closing the notebook lid. Maybe it detects no screen
  connected and then unset all resolutions?

  The notebook model page is:
  https://pcsupport.lenovo.com/br/pt/products/laptops-and-
  netbooks/300-series/310-14isk/80ug/80ugbr

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar  1 12:24:33 2019
  InstallationDate: Installed on 2017-06-13 (625 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (497 days ago)

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

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

[Desktop-packages] [Bug 1810808] [NEW] blocchi continui pagine

[mastrototaro leonardo]

Public bug reported:

aprendo le pagine il computer va in blocco e non risponde piu ai comandi

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompositorRunning: None
Date: Mon Jan  7 17:27:27 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c059]
   Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c059]
InstallationDate: Installed on 2016-10-10 (819 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: SAMSUNG ELECTRONICS CO., LTD. R519/R719
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=3b9ac247-cddd-4beb-ae47-cd4dfa76b6f1 ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 09CI.M060.20100401.JIP
dmi.board.name: R519/R719
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr09CI.M060.20100401.JIP:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR519/R719:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR519/R719:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: R519/R719
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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.2-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
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: Thu Oct  4 11:40:09 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  blocchi continui pagine

Status in xorg package in Ubuntu:
  New

Bug description:
  aprendo le pagine il computer va in blocco e non risponde piu ai
  comandi

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Jan  7 17:27:27 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c059]
 Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c059]
  InstallationDate: Installed on 2016-10-10 (819 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R519/R719
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=3b9ac247-cddd-4beb-ae47-cd4dfa76b6f1 ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2010
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 09CI.M060.20100401.JIP
  dmi.board.name: R519/R719
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 

[Desktop-packages] [Bug 1806877] [NEW] bocchi connessioni e pagine

[mastrototaro leonardo]

Public bug reported:

blocchi continui e pagine che si bloccano e si aprono da sole pagine che
non chiedo

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompositorRunning: None
Date: Wed Dec  5 13:25:40 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c059]
   Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c059]
InstallationDate: Installed on 2016-10-10 (786 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: SAMSUNG ELECTRONICS CO., LTD. R519/R719
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=3b9ac247-cddd-4beb-ae47-cd4dfa76b6f1 ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 09CI.M060.20100401.JIP
dmi.board.name: R519/R719
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr09CI.M060.20100401.JIP:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR519/R719:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR519/R719:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: R519/R719
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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.2-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
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: Thu Oct  4 11:40:09 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  bocchi connessioni e pagine

Status in xorg package in Ubuntu:
  New

Bug description:
  blocchi continui e pagine che si bloccano e si aprono da sole pagine
  che non chiedo

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  Date: Wed Dec  5 13:25:40 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c059]
 Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c059]
  InstallationDate: Installed on 2016-10-10 (786 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R519/R719
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=3b9ac247-cddd-4beb-ae47-cd4dfa76b6f1 ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2010
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 09CI.M060.20100401.JIP
  dmi.board.name: R519/R719
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: 

[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen

[Leonardo Müller]

This happened to me when using Ubuntu Cosmic Cuttlefish with htop and
tilix installed beyond the clean install. I was able to open the
applications that are available in the dock and noticed the bar resizing
when hovering over it.

Later multiple graphical bugs started to happen and in the next boot
Xorg was failing to start. Rebooting again solved the login issues.

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

Title:
  Ubuntu dock/launcher is shown on the lock screen

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

Bug description:
  After an update from ubuntu 16.04 to 18.04 the dock is aviable on the 
lockscreen after user login.
  I did not configure this knowingly. Also i can start every application which 
is available on the dock.
  Settings, virtual box, visualstudio code and so on.

  After the update to 18.04 i just configure the screen frequency to
  144Hz and the night mode on. And attach the dock on bottom.

  I later undid these customizations back to configuration before, but
  the dock is stil aviable on lockscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 18:30:16 2018
  InstallationDate: Installed on 2018-04-08 (27 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (27 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell-extension-ubuntu-dock 0.9.1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1778069] [NEW] nautilus don't open files if set as default file manager

[Leonardo Müller]

Public bug reported:

If Nautilus is set as the preferred file manager with exo-preferred-
applications, it no longer opens files. It opens only directories,
.desktop files and executable files. Trying to open a file, be using
Enter or with double mouse click, as a text file or a video makes
Nautilus window blink for a instant and nothing happens. To be able to
open the files, it's needed to choose to open with another application
and then choose the application.

Once Nautilus is unset as the default file manager (Thunar is chosen,
for example), it starts to work fine again, opening files properly.

Nautilus' Debian Sid version do not have this problem.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
Uname: Linux 4.17.2-041702-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jun 21 10:55:41 2018
InstallationDate: Installed on 2017-06-13 (372 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: nautilus
UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago)
usr_lib_nautilus: dropbox 2015.10.28

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


** Tags: amd64 apport-bug bionic

** Summary changed:

- nautilus don't open files is set as default file manager
+ nautilus don't open files if set as default file manager

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

Title:
  nautilus don't open files if set as default file manager

Status in nautilus package in Ubuntu:
  New

Bug description:
  If Nautilus is set as the preferred file manager with exo-preferred-
  applications, it no longer opens files. It opens only directories,
  .desktop files and executable files. Trying to open a file, be using
  Enter or with double mouse click, as a text file or a video makes
  Nautilus window blink for a instant and nothing happens. To be able to
  open the files, it's needed to choose to open with another application
  and then choose the application.

  Once Nautilus is unset as the default file manager (Thunar is chosen,
  for example), it starts to work fine again, opening files properly.

  Nautilus' Debian Sid version do not have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  Uname: Linux 4.17.2-041702-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jun 21 10:55:41 2018
  InstallationDate: Installed on 2017-06-13 (372 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago)
  usr_lib_nautilus: dropbox 2015.10.28

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

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

[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card

[Leonardo]

Setting "nouveau.modeset=-1" does not help here. My DELL XPS L502X is
still running hot:


~$ sudo service lm-sensors status
● lm-sensors.service - Initialize hardware monitoring sensors
   Loaded: loaded (/lib/systemd/system/lm-sensors.service; enabled; vendor 
preset: enabled)
   Active: active (exited) since Thu 2018-06-07 20:18:15 CEST; 27min ago
  Process: 991 ExecStart=/usr/bin/sensors (code=exited, status=0/SUCCESS)
  Process: 807 ExecStart=/usr/bin/sensors -s (code=exited, status=0/SUCCESS)
 Main PID: 991 (code=exited, status=0/SUCCESS)

giu 07 20:18:15 xps sensors[991]: acpitz-virtual-0
giu 07 20:18:15 xps sensors[991]: Adapter: Virtual device
giu 07 20:18:15 xps sensors[991]: temp1:+96.0°C  (crit = +100.0°C)
giu 07 20:18:15 xps sensors[991]: temp2:+96.0°C  (crit = +100.0°C)
giu 07 20:18:15 xps sensors[991]: coretemp-isa-
giu 07 20:18:15 xps sensors[991]: Adapter: ISA adapter
giu 07 20:18:15 xps sensors[991]: Package id 0:  +96.0°C  (high = +86.0°C, crit 
= +100.0°C)
giu 07 20:18:15 xps sensors[991]: Core 0:+96.0°C  (high = +86.0°C, crit 
= +100.0°C)
giu 07 20:18:15 xps sensors[991]: Core 1:+95.0°C  (high = +86.0°C, crit 
= +100.0°C)
giu 07 20:18:15 xps systemd[1]: Started Initialize hardware monitoring sensors.



~$ cat /proc/cmdline 
BOOT_IMAGE=/vmlinuz-4.15.0-22-lowlatency 
root=UUID=345b57d7-dea8-44de-a3c0-4614b87a4565 ro quiet splash video=VGA2:d 
nouveau.runpm=-1 vt.handoff=1

~$ cat /proc/acpi/bbswitch
:01:00.0 ON

~$ sudo  cat /sys/kernel/debug/vgaswitcheroo/switch
0:IGD:+:Pwr::00:02.0
1:DIS: :DynPwr::01:00.0

~$ sudo lsmod | grep nouveau
nouveau  1716224  1
mxm_wmi16384  1 nouveau
ttm   102400  1 nouveau
wmi24576  5 
dell_wmi,wmi_bmof,dell_wmi_descriptor,mxm_wmi,nouveau
i2c_algo_bit   16384  2 nouveau,i915
drm_kms_helper167936  2 nouveau,i915
drm   397312  8 nouveau,i915,ttm,drm_kms_helper
video  40960  4 dell_wmi,dell_laptop,nouveau,i915



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

Title:
  prime-select intel is not powering off the nvidia card

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Right now, it seems that prime-select intel makes sure the nvidia driver is 
not loaded, as nvidia-settings reports.
  But my power consumption is > 20W.
  cat /proc/acpi/bbswitch reports the card is still on. 

  
  If bbswitch and powertop are reliable, then the nvidia card is still powered.
  This is a thinkpad w520 in Optimus mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-prime 0.8.7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 19:56:21 2018
  Dependencies:
   
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-14 (125 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions

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

[Desktop-packages] [Bug 1754862] Re: Screen remains active on lid close

[Leonardo Donelli]

I spoke to soon. Even with gnome tweak tool option to ON and
HandleLidSwitch=ignore in /etc/systemd/logind.conf , the screen remains
active when the lid is closed.

(In my previous test it turned off because I didn't set =ignore in
logind.conf yet so it was actually going in standby).

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

Title:
  Screen remains active on lid close

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a Dell XPS 13 9370 (early 2018 model) with Ubuntu 17.04
  installed. I use the Gnome on XOrg session.

  When I close the laptop lid, I can see through the small (< 1mm) hairline 
crack that the screen is still active, showing the entire desktop. This happens 
only once I am logged in to the gnome shell session, I tried closing the lid 
before logging and the screen is correctly blanked.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-03-01 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1754862] Re: Screen remains active on lid close

[Leonardo Donelli]

Ok, I've found the problem.

This was due to a setting I had enabled in "Gnome Tweak Tool": "Suspend
when laptop lid is closed" to OFF

Setting this option to OFF (the default is ON) adds an autostart link in
.config/autostart/ignore-lid-switch-tweak.desktop, which runs the
/usr/lib/gnome-tweak-tool/gnome-tweak-tool-lid-inhibitor utility, which
creates a logind inhibitor:

systemd-inhibit --list

[...]

 Who: gnome-tweak-tool-lid-inhibitor (UID 1000/learts, PID 
22291/gnome-tweak-too)
What: handle-lid-switch
 Why: user preference
Mode: block
   
[...]

"Mode: block" means that the signal is blocked and not passed to the
other parts which may be handling the lid switch, including what I
assume is the standard code handling the screen poweroff.

By toggling the option to ON, the inhibitor goes away and the screen is
turned off when I close the lid.

Therefore, I advise everyone against using the "Suspend when laptop lid is 
closed" option in gnome tweak tools. A much better way to diisable suspend on 
lid cose is to edit /etc/systemd/logind.conf
and set HandleLidSwitch=ignore.
There are also the additional options of HandleLidSwitchDocked and 
HandleLidSwitchExternalPower (this one since systemd 238) to set a different 
action to take on lid close when the laptop is connected to an external monitor 
or AC power, respectively.

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

Title:
  Screen remains active on lid close

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a Dell XPS 13 9370 (early 2018 model) with Ubuntu 17.04
  installed. I use the Gnome on XOrg session.

  When I close the laptop lid, I can see through the small (< 1mm) hairline 
crack that the screen is still active, showing the entire desktop. This happens 
only once I am logged in to the gnome shell session, I tried closing the lid 
before logging and the screen is correctly blanked.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-03-01 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1765846] [NEW] Pidgin freezes if two windows with chat are closed

[Leonardo Müller]

Public bug reported:

When using Pidgin, if a chat that is persistent is closed and the user
is notified because he/she was mentioned, when clicking in the
notification or in the panel indicator-messages, the chat is opened in a
new window, so Pidgin has the window with the friend and channel list
and two windows with chats.

If one window with chat is closed, all tabs with chats go to the
remaining one and the tabs no longer can be closed. If the user tries to
close the remaining chat window, then Pidgin freezes and the window
title changes many times per second, each instant with the name of one
of the channels. The only way to stop it then is to kill the process.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pidgin 1:2.12.0-1ubuntu4
Uname: Linux 4.16.3-041603-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Apr 20 17:43:08 2018
InstallationDate: Installed on 2017-06-13 (310 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: pidgin
UpgradeStatus: Upgraded to bionic on 2017-10-20 (182 days ago)

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

Title:
  Pidgin freezes if two windows with chat are closed

Status in pidgin package in Ubuntu:
  New

Bug description:
  When using Pidgin, if a chat that is persistent is closed and the user
  is notified because he/she was mentioned, when clicking in the
  notification or in the panel indicator-messages, the chat is opened in
  a new window, so Pidgin has the window with the friend and channel
  list and two windows with chats.

  If one window with chat is closed, all tabs with chats go to the
  remaining one and the tabs no longer can be closed. If the user tries
  to close the remaining chat window, then Pidgin freezes and the window
  title changes many times per second, each instant with the name of one
  of the channels. The only way to stop it then is to kill the process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pidgin 1:2.12.0-1ubuntu4
  Uname: Linux 4.16.3-041603-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Apr 20 17:43:08 2018
  InstallationDate: Installed on 2017-06-13 (310 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pidgin
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (182 days ago)

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

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

[Desktop-packages] [Bug 1765775] [NEW] Window decoration becomes very large if the image has much more height than width

[Leonardo Müller]

Public bug reported:

When a image with much higher height than width is opened, the window
decoration becomes very big, as it tries to keep the image proportional:
https://i.imgur.com/SZu0lOk.png

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: eog 3.28.1-1
Uname: Linux 4.16.3-041603-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Apr 20 13:08:37 2018
InstallationDate: Installed on 2017-06-13 (310 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: eog
UpgradeStatus: Upgraded to bionic on 2017-10-20 (182 days ago)

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

Title:
  Window decoration becomes very large if the image has much more height
  than width

Status in eog package in Ubuntu:
  New

Bug description:
  When a image with much higher height than width is opened, the window
  decoration becomes very big, as it tries to keep the image
  proportional: https://i.imgur.com/SZu0lOk.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: eog 3.28.1-1
  Uname: Linux 4.16.3-041603-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Apr 20 13:08:37 2018
  InstallationDate: Installed on 2017-06-13 (310 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: eog
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (182 days ago)

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

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

[Desktop-packages] [Bug 1764872] [NEW] When in fullscreen, the buttons to minimize and close don't appear when hovering the mouse

[Leonardo Müller]

Public bug reported:

When in fullscreen, the buttons that should appear when hovering the
mouse cursor centered on the top of the display don't appear. They still
have the function but, as it's impossible to see them, it's not possible
to see if the button will close or minimize the session.

I'm using vinagre with the VNC protocol to see and use my desktop, which
is in the local network.

I had this bug with virt-manager in Artful. It's curious to see it back,
but now in vinagre.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: vinagre 3.22.0-5
Uname: Linux 4.16.2-041602-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Apr 17 18:18:17 2018
InstallationDate: Installed on 2017-06-13 (307 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: vinagre
UpgradeStatus: Upgraded to bionic on 2017-10-20 (179 days ago)

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

Title:
  When in fullscreen, the buttons to minimize and close don't appear
  when hovering the mouse

Status in vinagre package in Ubuntu:
  New

Bug description:
  When in fullscreen, the buttons that should appear when hovering the
  mouse cursor centered on the top of the display don't appear. They
  still have the function but, as it's impossible to see them, it's not
  possible to see if the button will close or minimize the session.

  I'm using vinagre with the VNC protocol to see and use my desktop,
  which is in the local network.

  I had this bug with virt-manager in Artful. It's curious to see it
  back, but now in vinagre.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vinagre 3.22.0-5
  Uname: Linux 4.16.2-041602-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Apr 17 18:18:17 2018
  InstallationDate: Installed on 2017-06-13 (307 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: vinagre
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (179 days ago)

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

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

[Desktop-packages] [Bug 1763537] [NEW] libpulse-dev don't provide the required files to build static programs

[Leonardo Müller]

Public bug reported:

The package libpulse-dev don't provide the static libraries files
required to build static programs using libpulse-dev but, when building
pulseaudio, there is a option to build static libraries. Could they be
added to the package libpulse-dev?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libpulse-dev 1:11.1-1ubuntu7
Uname: Linux 4.16.1-041601-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   usuario1945 F...m pulseaudio
 /dev/snd/controlC0:  usuario1945 F pulseaudio
 /dev/snd/seq:usuario1926 F timidity
CurrentDesktop: XFCE
Date: Thu Apr 12 20:13:18 2018
InstallationDate: Installed on 2017-06-13 (303 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to bionic on 2017-10-20 (174 days ago)
dmi.bios.date: 07/10/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN43WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80UG
dmi.product.version: Lenovo ideapad 310-14ISK
dmi.sys.vendor: LENOVO

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

Title:
  libpulse-dev don't provide the required files to build static programs

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The package libpulse-dev don't provide the static libraries files
  required to build static programs using libpulse-dev but, when
  building pulseaudio, there is a option to build static libraries.
  Could they be added to the package libpulse-dev?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libpulse-dev 1:11.1-1ubuntu7
  Uname: Linux 4.16.1-041601-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   usuario1945 F...m pulseaudio
   /dev/snd/controlC0:  usuario1945 F pulseaudio
   /dev/snd/seq:usuario1926 F timidity
  CurrentDesktop: XFCE
  Date: Thu Apr 12 20:13:18 2018
  InstallationDate: Installed on 2017-06-13 (303 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (174 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1750707] Re: LibreOffice says permission was denied to open a file in a NTFS partition, even with it having permission

[Leonardo Müller]

Yes, the bug was resolved to me. I reported it when LibreOffice was at
version 5.4.4-0ubuntu5. When updated to 6.0, the bug no longer happened.

I've asked Simon to close this bug on IRC as LibreOffice was working
correctly for some time and its status had never changed.

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

Title:
  LibreOffice says permission was denied to open a file in a NTFS
  partition, even with it having permission

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  I'm trying to open a spreadsheet file located in a NTFS partition, but
  LibreOffice gives an error saying the permission is denied. I am sure
  I have permission to edit that file and that partition because I could
  edit it with Gedit (it does not show Read-Only on the bar) and I
  copied and created new files (not with LibreOffice) in the same
  directory the spreadsheet is.

  The NTFS partition is mounted at boot time using the following on /etc/fstab 
(redacted): 
  UUID=  /mnt/W10  ntfs-3g  defaults,windows_names  0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:5.4.4-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 20 23:16:05 2018
  InstallationDate: Installed on 2017-06-13 (252 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (124 days ago)

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

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

[Desktop-packages] [Bug 1690192] Re: Unable to configure Gmail account, login window has no functional buttons

[Leonardo Müller]

Thunderbird was updated soon after I did this report and the bug was
corrected.

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

Title:
  Unable to configure Gmail account, login window has no functional
  buttons

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Hello

  I tried to add a Gmail account, after choosing the options on
  Thunderbird, a window opens requesting the login information. However,
  the buttons on this window aren't functional, so clicking Next, Help
  or any other have no effect. I expected the buttons would work and I
  could log in the account.

  This bug is reported on https://support.mozilla.org/pt-
  BR/questions/1157902 and affected me, which was using the Ubuntu
  version. I was using thunderbird version
  45.8.0+build1-0ubuntu0.16.04.1.

  I have removed the thunderbird installation and I am using the one
  downloaded from the Thunderbird site (version 52.1) which has the
  correction.

  I believe the Thunderbird package should be updated to the newer
  version to solve this.

  Thank you.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

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

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

[Desktop-packages] [Bug 1754862] Re: Screen remains active on lid close

[Leonardo Donelli]

Ok, sorry for the late answer. Attached here is a fragment of journal
errors, this is the part that always gets logged when I close and reopen
the lid with no external monitor attached. I collected it using
`journalctl -b --priority warning --lines 50 --follow`

** Attachment added: "JournalErrors on lid close"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754862/+attachment/5083429/+files/journalErrors.txt

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

Title:
  Screen remains active on lid close

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a Dell XPS 13 9370 (early 2018 model) with Ubuntu 17.04
  installed. I use the Gnome on XOrg session.

  When I close the laptop lid, I can see through the small (< 1mm) hairline 
crack that the screen is still active, showing the entire desktop. This happens 
only once I am logged in to the gnome shell session, I tried closing the lid 
before logging and the screen is correctly blanked.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-03-01 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1754862] Re: Screen remains active on lid close

[Leonardo Donelli]

Keep in mind that I launched the command in a different configuration
(external monitor attached configured as the single display) and without
triggering the bug beforehand. Should I reupload any of the attachments
immediately after having triggered the bug? i.e. after closing and
reopening the lid using the laptop display that remains active.

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

Title:
  Screen remains active on lid close

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a Dell XPS 13 9370 (early 2018 model) with Ubuntu 17.04
  installed. I use the Gnome on XOrg session.

  When I close the laptop lid, I can see through the small (< 1mm) hairline 
crack that the screen is still active, showing the entire desktop. This happens 
only once I am logged in to the gnome shell session, I tried closing the lid 
before logging and the screen is correctly blanked.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-03-01 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

[Leonardo Donelli]

apport information

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

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

Title:
  Screen remains active on lid close

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell XPS 13 9370 (early 2018 model) with Ubuntu 17.04
  installed. I use the Gnome on XOrg session.

  When I close the laptop lid, I can see through the small (< 1mm) hairline 
crack that the screen is still active, showing the entire desktop. This happens 
only once I am logged in to the gnome shell session, I tried closing the lid 
before logging and the screen is correctly blanked.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-03-01 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

[Leonardo Donelli]

apport information

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

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

Title:
  Screen remains active on lid close

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell XPS 13 9370 (early 2018 model) with Ubuntu 17.04
  installed. I use the Gnome on XOrg session.

  When I close the laptop lid, I can see through the small (< 1mm) hairline 
crack that the screen is still active, showing the entire desktop. This happens 
only once I am logged in to the gnome shell session, I tried closing the lid 
before logging and the screen is correctly blanked.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-03-01 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1754862] Re: Screen remains active on lid close

[Leonardo Donelli]

apport information

** Tags added: apport-collected artful

** Description changed:

  I have a Dell XPS 13 9370 (early 2018 model) with Ubuntu 17.04
  installed. I use the Gnome on XOrg session.
  
- When I close the laptop lid, I can see through the small (< 1mm)
- hairline crack that the screen is still active, showing the entire
- desktop. This happens only once I am logged in to the gnome shell
- session, I tried closing the lid before logging and the screen is
- correctly blanked.
+ When I close the laptop lid, I can see through the small (< 1mm) hairline 
crack that the screen is still active, showing the entire desktop. This happens 
only once I am logged in to the gnome shell session, I tried closing the lid 
before logging and the screen is correctly blanked.
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.7
+ Architecture: amd64
+ CurrentDesktop: GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 17.10
+ InstallationDate: Installed on 2018-03-01 (11 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
+ Package: gnome-shell 3.26.2-0ubuntu0.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
+ Tags:  artful
+ Uname: Linux 4.13.0-36-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Screen remains active on lid close

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell XPS 13 9370 (early 2018 model) with Ubuntu 17.04
  installed. I use the Gnome on XOrg session.

  When I close the laptop lid, I can see through the small (< 1mm) hairline 
crack that the screen is still active, showing the entire desktop. This happens 
only once I am logged in to the gnome shell session, I tried closing the lid 
before logging and the screen is correctly blanked.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-03-01 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

[Leonardo Donelli]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1754862/+attachment/5076767/+files/JournalErrors.txt

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

Title:
  Screen remains active on lid close

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell XPS 13 9370 (early 2018 model) with Ubuntu 17.04
  installed. I use the Gnome on XOrg session.

  When I close the laptop lid, I can see through the small (< 1mm) hairline 
crack that the screen is still active, showing the entire desktop. This happens 
only once I am logged in to the gnome shell session, I tried closing the lid 
before logging and the screen is correctly blanked.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-03-01 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1754862] GsettingsChanges.txt

[Leonardo Donelli]

apport information

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

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

Title:
  Screen remains active on lid close

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell XPS 13 9370 (early 2018 model) with Ubuntu 17.04
  installed. I use the Gnome on XOrg session.

  When I close the laptop lid, I can see through the small (< 1mm) hairline 
crack that the screen is still active, showing the entire desktop. This happens 
only once I am logged in to the gnome shell session, I tried closing the lid 
before logging and the screen is correctly blanked.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-03-01 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1752901] [NEW] If libegl1 is installed, modeset fails and rendering falls back to CPU (llvmpipe)

[Leonardo Müller]

Public bug reported:

When I updated my system today ( https://paste.ubuntu.com/p/S7csQfNHT4/
), logged off and logged in, the GPU rendering stopped working. Now
using glxinfo it outputs: https://paste.ubuntu.com/p/njnbMHf7Bk/

Before libegl1 was required I hadn't it installed, but as now it is
unavoidable, it became a big problem.

The only way to make GPU rendering work on this machine is to create a
xorg.conf file at /etc/X11 and use the driver intel, but it is said this
is not recommended to use it with hardware newer than 2007.

Specifications:
Intel Core i3-6100U
Intel HD Graphics 520
8 GB of RAM

lspci output: https://paste.ubuntu.com/p/Djz3WxstQ5/

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libegl1 0.2.999+git20170802-2
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar  2 12:01:51 2018
Dependencies:
 gcc-8-base 8-20180218-1ubuntu1
 libc6 2.26-0ubuntu2.1
 libgcc1 1:8-20180218-1ubuntu1
 libglvnd0 0.2.999+git20170802-2
InstallationDate: Installed on 2017-06-13 (261 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: libglvnd
UpgradeStatus: Upgraded to bionic on 2017-10-20 (133 days ago)

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

Title:
  If libegl1 is installed, modeset fails and rendering falls back to CPU
  (llvmpipe)

Status in libglvnd package in Ubuntu:
  New

Bug description:
  When I updated my system today (
  https://paste.ubuntu.com/p/S7csQfNHT4/ ), logged off and logged in,
  the GPU rendering stopped working. Now using glxinfo it outputs:
  https://paste.ubuntu.com/p/njnbMHf7Bk/

  Before libegl1 was required I hadn't it installed, but as now it is
  unavoidable, it became a big problem.

  The only way to make GPU rendering work on this machine is to create a
  xorg.conf file at /etc/X11 and use the driver intel, but it is said
  this is not recommended to use it with hardware newer than 2007.

  Specifications:
  Intel Core i3-6100U
  Intel HD Graphics 520
  8 GB of RAM

  lspci output: https://paste.ubuntu.com/p/Djz3WxstQ5/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libegl1 0.2.999+git20170802-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar  2 12:01:51 2018
  Dependencies:
   gcc-8-base 8-20180218-1ubuntu1
   libc6 2.26-0ubuntu2.1
   libgcc1 1:8-20180218-1ubuntu1
   libglvnd0 0.2.999+git20170802-2
  InstallationDate: Installed on 2017-06-13 (261 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libglvnd
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (133 days ago)

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

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

[Desktop-packages] [Bug 1750941] [NEW] Pidgin crashes if I select text on chat and try to drag and drop it

[Leonardo Müller]

Public bug reported:

When I select text on Pidgin's chat and try to drag and drop it, the
pidgin crashes. This crash creates no file in /var/crash and gdb is very
inconclusive:

$ sudo gdb
GNU gdb (Ubuntu 8.1-0ubuntu1) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) attach 23768
Anexando a process 23768
[New LWP 23769]
[New LWP 23771]
[New LWP 23772]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fc9e38ba951 in __GI___poll (fds=0x7fc9c0001650, nfds=7, timeout=6998)
at ../sysdeps/unix/sysv/linux/poll.c:29
29  ../sysdeps/unix/sysv/linux/poll.c: Arquivo ou diretório não encontrado.
(gdb) continue
Continuando.
[Thread 0x7fc9c9bf0700 (LWP 23772) exited]
[Thread 0x7fc9ca3f1700 (LWP 23771) exited]
[Thread 0x7fc9ccd28700 (LWP 23769) exited]
[Inferior 1 (process 23768) exited with code 01]
(gdb) bt
No stack.

This is easily reproducible, as it happens always I select text on the
chat and try to drag and drop.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pidgin 1:2.12.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Feb 21 22:58:19 2018
InstallationDate: Installed on 2017-06-13 (253 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: pidgin
UpgradeStatus: Upgraded to bionic on 2017-10-20 (125 days ago)

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  Pidgin crashes if I select text on chat and try to drag and drop it

Status in pidgin package in Ubuntu:
  New

Bug description:
  When I select text on Pidgin's chat and try to drag and drop it, the
  pidgin crashes. This crash creates no file in /var/crash and gdb is
  very inconclusive:

  $ sudo gdb
  GNU gdb (Ubuntu 8.1-0ubuntu1) 8.1
  Copyright (C) 2018 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word".
  (gdb) attach 23768
  Anexando a process 23768
  [New LWP 23769]
  [New LWP 23771]
  [New LWP 23772]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7fc9e38ba951 in __GI___poll (fds=0x7fc9c0001650, nfds=7, timeout=6998)
  at ../sysdeps/unix/sysv/linux/poll.c:29
  29../sysdeps/unix/sysv/linux/poll.c: Arquivo ou diretório não encontrado.
  (gdb) continue
  Continuando.
  [Thread 0x7fc9c9bf0700 (LWP 23772) exited]
  [Thread 0x7fc9ca3f1700 (LWP 23771) exited]
  [Thread 0x7fc9ccd28700 (LWP 23769) exited]
  [Inferior 1 (process 23768) exited with code 01]
  (gdb) bt
  No stack.

  This is easily reproducible, as it happens always I select text on the
  chat and try to drag and drop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pidgin 1:2.12.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Feb 21 22:58:19 2018
  InstallationDate: Installed on 2017-06-13 (253 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pidgin
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (125 days ago)

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1750707] [NEW] LibreOffice says permission was denied to open a file in a NTFS partition, even with it having permission

[Leonardo Müller]

Public bug reported:

I'm trying to open a spreadsheet file located in a NTFS partition, but
LibreOffice gives an error saying the permission is denied. I am sure I
have permission to edit that file and that partition because I could
edit it with Gedit (it does not show Read-Only on the bar) and I copied
and created new files (not with LibreOffice) in the same directory the
spreadsheet is.

The NTFS partition is mounted at boot time using the following on /etc/fstab 
(redacted): 
UUID=  /mnt/W10  ntfs-3g  defaults,windows_names  0 0

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice 1:5.4.4-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Feb 20 23:16:05 2018
InstallationDate: Installed on 2017-06-13 (252 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to bionic on 2017-10-20 (124 days ago)

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  LibreOffice says permission was denied to open a file in a NTFS
  partition, even with it having permission

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I'm trying to open a spreadsheet file located in a NTFS partition, but
  LibreOffice gives an error saying the permission is denied. I am sure
  I have permission to edit that file and that partition because I could
  edit it with Gedit (it does not show Read-Only on the bar) and I
  copied and created new files (not with LibreOffice) in the same
  directory the spreadsheet is.

  The NTFS partition is mounted at boot time using the following on /etc/fstab 
(redacted): 
  UUID=  /mnt/W10  ntfs-3g  defaults,windows_names  0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:5.4.4-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 20 23:16:05 2018
  InstallationDate: Installed on 2017-06-13 (252 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (124 days ago)

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

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

[Desktop-packages] [Bug 1750421] Re: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado

[Leonardo Müller]

** Description changed:

  Hi
  
  I "upgraded" from Xubuntu 17.10 to 18.04 using the information from this
  post: https://community.ubuntu.com/t/bionic-daily-is-out/1530/4
  
- When libfontconfig-dev:amd64 tried to update it failed. I tried again
+ When libfontconfig1-dev:amd64 tried to update it failed. I tried again
  and it failed again, then I opened synaptic and noticed that the
- libfontconfig-dev:i386 was already updated to the last version. After
+ libfontconfig1-dev:i386 was already updated to the last version. After
  the i386 version was purged, the amd64 version could be updated and the
  upgrade finished.
  
  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfontconfig1-dev 2.12.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Mon Feb 19 14:38:06 2018
  ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
  InstallationDate: Installed on 2017-06-13 (250 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
-  dpkg 1.19.0.5ubuntu1
-  apt  1.6~alpha7ubuntu2
+  dpkg 1.19.0.5ubuntu1
+  apt  1.6~alpha7ubuntu2
  SourcePackage: fontconfig
  Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: 
a tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (122 days ago)

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

Title:
  package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade:
  a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-
  devel.pdf.gz' partilhado, que é diferente de outras instâncias do
  pacote libfontconfig1-dev:amd64

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Hi

  I "upgraded" from Xubuntu 17.10 to 18.04 using the information from
  this post: https://community.ubuntu.com/t/bionic-daily-is-out/1530/4

  When libfontconfig1-dev:amd64 tried to update it failed. I tried again
  and it failed again, then I opened synaptic and noticed that the
  libfontconfig1-dev:i386 was already updated to the last version. After
  the i386 version was purged, the amd64 version could be updated and
  the upgrade finished.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfontconfig1-dev 2.12.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Mon Feb 19 14:38:06 2018
  ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
  InstallationDate: Installed on 2017-06-13 (250 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu2
  SourcePackage: fontconfig
  Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: 
a tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (122 days ago)

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

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

[Desktop-packages] [Bug 1750421] [NEW] package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilha

[Leonardo Müller]

Public bug reported:

Hi

I "upgraded" from Xubuntu 17.10 to 18.04 using the information from this
post: https://community.ubuntu.com/t/bionic-daily-is-out/1530/4

When libfontconfig-dev:amd64 tried to update it failed. I tried again
and it failed again, then I opened synaptic and noticed that the
libfontconfig-dev:i386 was already updated to the last version. After
the i386 version was purged, the amd64 version could be updated and the
upgrade finished.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libfontconfig1-dev 2.12.6-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Mon Feb 19 14:38:06 2018
ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
InstallationDate: Installed on 2017-06-13 (250 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~alpha7ubuntu2
SourcePackage: fontconfig
Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: a 
tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
UpgradeStatus: Upgraded to bionic on 2017-10-20 (122 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade:
  a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-
  devel.pdf.gz' partilhado, que é diferente de outras instâncias do
  pacote libfontconfig1-dev:amd64

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Hi

  I "upgraded" from Xubuntu 17.10 to 18.04 using the information from
  this post: https://community.ubuntu.com/t/bionic-daily-is-out/1530/4

  When libfontconfig-dev:amd64 tried to update it failed. I tried again
  and it failed again, then I opened synaptic and noticed that the
  libfontconfig-dev:i386 was already updated to the last version. After
  the i386 version was purged, the amd64 version could be updated and
  the upgrade finished.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfontconfig1-dev 2.12.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Mon Feb 19 14:38:06 2018
  ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
  InstallationDate: Installed on 2017-06-13 (250 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu2
  SourcePackage: fontconfig
  Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: 
a tentar sobreescrever 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é 
diferente de outras instâncias do pacote libfontconfig1-dev:amd64
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (122 days ago)

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

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

[Desktop-packages] [Bug 1749940] [NEW] package network-manager-gnome 1.2.6-0ubuntu0.16.04.4 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tenta

[Leonardo Pereira Pimentel Leite]

Public bug reported:

please , i don't understand the bug , help ! alguns arquivos no
terminal estao informando que o pacote está corrompido e eu nao sei o
que fazer

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: network-manager-gnome 1.2.6-0ubuntu0.16.04.4
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Thu Feb 15 06:05:37 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-11-29 (78 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
IpRoute:
 default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
 169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
 192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.111  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: network-manager-applet
Title: package network-manager-gnome 1.2.6-0ubuntu0.16.04.4 failed to 
install/upgrade: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

 wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  SAM 
NET Tayrone 1  b4738f86-8f8b-4d7e-a051-3b82b8c5262e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enp2s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  --   
  ----  
   
 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  --   
  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package network-manager-gnome 1.2.6-0ubuntu0.16.04.4 failed to
  install/upgrade: O pacote está num mau estado de inconsistência; deve
  reinstala-lo antes de tentar configura-lo.

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  please , i don't understand the bug , help ! alguns arquivos no
  terminal estao informando que o pacote está corrompido e eu nao sei o
  que fazer

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: network-manager-gnome 1.2.6-0ubuntu0.16.04.4
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb 15 06:05:37 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-11-29 (78 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.111  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: network-manager-applet
  Title: package network-manager-gnome 1.2.6-0ubuntu0.16.04.4 failed to 
install/upgrade: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  

[Desktop-packages] [Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use

[Leonardo Donelli]

I do not seem to have the memory leak problem (the used RAM doesn't seem
to grow constantly and without bounds), but still it uses constantly
almost 200 MB of memory, which seems kind of unacceptable to me for an
application which is usually run rarely or not at all for people who
prefer using apt. I get that terminal users should not be the main
concern of the OS/DE developers, but still, an option to disable the
gnome-software autostart would be nice.

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

Title:
  gnome-software using hundreds of MB of memory when not in use

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  It seems gnome-software is running in the background all the time. Not
  a big deal if it was lightweight, but it seems to use hundreds of MB
  (from smem output):

PID User Command Swap  USS  PSS  
RSS 
   2291 jan  /usr/bin/gnome-software --g   285436   112576   117982   
134036 

  A total of over 400MB in RAM and swap combined.

  After killing and restarting, it takes "only" a bit over 100MB.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 24 09:45:53 2016
  InstallationDate: Installed on 2012-11-10 (1382 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-06-19 (65 days ago)

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

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

[Desktop-packages] [Bug 1729707] [NEW] Ubuntu stop working when try to change network setup

[Leonardo Delgado]

Public bug reported:

Can't change wifi network. In /var/log/syslog report multiple times:

wpa_supplicant[830]: message repeated 22 times: [ wlp2s0: CTRL-EVENT-
SCAN-FAILED ret=-16 retry=1

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

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

Title:
  Ubuntu stop working when try to change network setup

Status in wpa package in Ubuntu:
  New

Bug description:
  Can't change wifi network. In /var/log/syslog report multiple times:

  wpa_supplicant[830]: message repeated 22 times: [ wlp2s0: CTRL-EVENT-
  SCAN-FAILED ret=-16 retry=1

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

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

[Desktop-packages] [Bug 1690192] [NEW] Unable to configure Gmail account, login window has no functional buttons

[Leonardo Müller]

Public bug reported:

Hello

I tried to add a Gmail account, after choosing the options on
Thunderbird, a window opens requesting the login information. However,
the buttons on this window aren't functional, so clicking Next, Help or
any other have no effect. I expected the buttons would work and I could
log in the account.

This bug is reported on https://support.mozilla.org/pt-
BR/questions/1157902 and affected me, which was using the Ubuntu
version. I was using thunderbird version 45.8.0+build1-0ubuntu0.16.04.1.

I have removed the thunderbird installation and I am using the one
downloaded from the Thunderbird site (version 52.1) which has the
correction.

I believe the Thunderbird package should be updated to the newer version
to solve this.

Thank you.

$ lsb_release -rd
Description:Ubuntu 16.04.2 LTS
Release:16.04

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

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

Title:
  Unable to configure Gmail account, login window has no functional
  buttons

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Hello

  I tried to add a Gmail account, after choosing the options on
  Thunderbird, a window opens requesting the login information. However,
  the buttons on this window aren't functional, so clicking Next, Help
  or any other have no effect. I expected the buttons would work and I
  could log in the account.

  This bug is reported on https://support.mozilla.org/pt-
  BR/questions/1157902 and affected me, which was using the Ubuntu
  version. I was using thunderbird version
  45.8.0+build1-0ubuntu0.16.04.1.

  I have removed the thunderbird installation and I am using the one
  downloaded from the Thunderbird site (version 52.1) which has the
  correction.

  I believe the Thunderbird package should be updated to the newer
  version to solve this.

  Thank you.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

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

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

[Desktop-packages] [Bug 1668465] Re: weird color display after suspend.

[Leonardo de la Cerda]

I found the same bug.
This is my graphic card (but I'm not sure how to check the driver version):
Video Card: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1)
OS version: Ubuntu 16.04.2 LTS

I think that those "funny" colors space is the video card memory that wasn't 
refreshed. Maybe during the suspend it got some noise values and it should be 
fixed with a 'redraw' call.
But I'm no expert on Ubuntu or video card code :P

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

Title:
  weird color display after suspend.

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I restart the display manager then the display is fine again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 28 09:24:44 2017
  InstallationDate: Installed on 2016-03-31 (334 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-10-19 (131 days ago)

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

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

[Desktop-packages] [Bug 1665432] [NEW] Error with cups-daemon package when reinstalling many packages to recover wireless connection with QCA9377

[Leonardo Müller]

Public bug reported:

I had a issue with my Wireless and Bluetooth card, Qualcomm Atheros
Device [168c:0042] (rev 30), which appears on Windows 10 as QCA9377, and
to solve it I have searched and tried different alternatives. The one
that worked was to reinstall many packages, all the ones I have found
when searching for, firstly, "wireless", then "wifi" and then
"internet", on synaptic. When doing the "internet" reinstall, a error
happened on cups-daemon and it crashed. When I tried again, it worked. I
rebooted the computer and the Wireless is functioning again (Bluetooth
was already OK).

I am using the Kernel 4.9.10-040910-generic from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.10/ because I was
trying to solve this issue and because the official Kernles 4.4 and 4.8
don't eject external HDDs from the USB 3.0 correctly. The notebook model
is Lenovo Ideapad 310-14ISK.

While this window to report the bug appeared saying cups is the culprit,
all this only happened because the wireless device QCA9377 was not
working.

usuario@usuario-Lenovo-ideapad-310-14ISK:~$ lsb_release -rd
Description:Ubuntu 16.04.2 LTS
Release:16.04

usuario@usuario-Lenovo-ideapad-310-14ISK:~$ uname -a
Linux usuario-Lenovo-ideapad-310-14ISK 4.9.10-040910-generic #201702141931 SMP 
Wed Feb 15 00:33:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

I hope this information may be helpful.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
Uname: Linux 4.9.10-040910-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CupsErrorLog: W [16/Feb/2017:14:42:01 -0200] Notifier for subscription 298 
(dbus://) went away, retrying!
Date: Thu Feb 16 16:05:14 2017
ErrorMessage: sub-processo novo script pre-removal retornou estado de saída de 
erro 1
InstallationDate: Installed on 2016-12-31 (47 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lpstat: device for Deskjet-2050-J510-series: 
hp:/usb/Deskjet_2050_J510_series?serial=BR1C1FK1K005D1
MachineType: LENOVO 80UG
Papersize: a4
PpdFiles: Deskjet-2050-J510-series: HP Deskjet 2050 j510 Series, hpcups 3.16.3
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.9.10-040910-generic 
root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.10-040910-generic 
root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: sub-processo novo 
script pre-removal retornou estado de saída de erro 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/03/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN37WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN37WW:bd10/03/2016:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
dmi.product.name: 80UG
dmi.product.version: Lenovo ideapad 310-14ISK
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package xenial

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

Title:
  Error with cups-daemon package when reinstalling many packages to
  recover wireless connection with QCA9377

Status in cups package in Ubuntu:
  New

Bug description:
  I had a issue with my Wireless and Bluetooth card, Qualcomm Atheros
  Device [168c:0042] (rev 30), which appears on Windows 10 as QCA9377,
  and to solve it I have searched and tried different alternatives. The
  one that worked was to reinstall many packages, all the ones I have
  found when searching for, firstly, "wireless", then "wifi" and then
  "internet", on synaptic. When doing the "internet" reinstall, a error
  happened on cups-daemon and it crashed. When I tried again, it worked.
  I rebooted the computer and the Wireless is functioning again
  (Bluetooth was already OK).

  I am using the Kernel 4.9.10-040910-generic from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.10/ because I was
  trying to solve this issue and because the official Kernles 4.4 and
  4.8 don't eject external HDDs from the USB 3.0 correctly. The notebook
  model is Lenovo Ideapad 310-14ISK.

  While this window to report the bug appeared saying cups is the
  culprit, all this only happened because the wireless device QCA9377
  was not working.

  usuario@usuario-Lenovo-ideapad-310-14ISK:~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  usuario@usuario-Lenovo-ideapad-310-14ISK:~$ uname -a
  Linux usuario-Lenovo-ideapad-310-14ISK 4.9.10-040910-generic 

[Desktop-packages] [Bug 1661387] [NEW] After click Ubuntu Software icon, Ubuntu Software launches and open, but 5 secons later suddenly closes.

[Leonardo Pinheiro Loureiro]

Public bug reported:

Ubuntu 16.04 LTS

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Feb  2 18:44:25 2017
InstallationDate: Installed on 2017-02-01 (1 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  After click Ubuntu Software icon, Ubuntu Software launches and open,
  but 5 secons later suddenly closes.

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb  2 18:44:25 2017
  InstallationDate: Installed on 2017-02-01 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  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/1661387/+subscriptions

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

[Desktop-packages] [Bug 1394189] Re: [Samsung NP-RF711-S07UK] Nvidia proprietary driver stopped working after ubuntu 14.04 updates from 18 November 2014

[Leonardo Lima de Vasconcellos]

Same error message when using dual monitor. One is the integrated laptop
lcd (1366x768) and the other is HDMI 1080p monitor.

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  [Samsung NP-RF711-S07UK] Nvidia proprietary driver stopped working
  after ubuntu 14.04 updates from  18 November 2014

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed

Bug description:
  Dual Screen not working on 14.04 when I log in today.  Get error
  message:

  Failed to apply configuration: %s

  
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2:
  could not set the configuration for CRTC 63

  Yesterday I applied updates.  Ubuntu software history shows these as:

  bsdutils(2.20.1-5.1ubuntu20.2,2.20.1-5.1ubuntu20.3)
  xserver-xorg-video-intel(2.99.910-0ubuntu1.2,2.99.910-0ubuntu1.3)

  Previous to this I have had no problems with dual screen on 14.04.

  WORKAROUND: Reverted to the Nouveau driver. The nvidia driver 331.38
  previously worked but doesn't now after the above Ubuntu updates.

  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c0a5]
     Subsystem: Samsung Electronics Co Ltd Device [144d:c0a5]
  InstallationDate: Installed on 2014-08-30 (91 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=2d9f275c-a65b-4e1a-a20b-e2ad679f1109 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 3.13.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 15HX.M042.20120302.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 15HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr15HX.M042.20120302.SSH:bd03/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr15HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr15HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: RF511/RF411/RF711
  dmi.product.version: 15HX
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Nov 30 12:26:46 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13133
   vendor SEC
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1394189/+subscriptions

-- 
Mailing list: 

[Desktop-packages] [Bug 1653727] [NEW] infectado con arcivos cript desde windows seven

[Juan Leonardo Sanchez]

Public bug reported:

dicsco compartido con windos seven

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-74.82-generic 3.19.8-ckt22
Uname: Linux 3.19.0-74-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.7
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Jan  3 10:47:22 2017
DistUpgraded: 2016-09-22 00:37:21,126 DEBUG enabling apt cron job
DistroCodename: vivid
DistroVariant: ubuntu
DpkgLog:
 
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Elitegroup Computer Systems Device [1019:3184]
InstallationDate: Installed on 2015-02-16 (686 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
MachineType: ECS H61H2-CM
ProcEnviron:
 LANGUAGE=es_VE:es
 PATH=(custom, no user)
 LANG=es_VE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic 
root=UUID=8426958f-20c8-4974-b61a-da41d6109d75 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to vivid on 2016-09-22 (103 days ago)
dmi.bios.date: 08/12/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.name: H61H2-CM
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/12/2011:svnECS:pnH61H2-CM:pvr:rvnECS:rnH61H2-CM:rvr1.0:cvnECS:ct3:cvr:
dmi.product.name: H61H2-CM
dmi.sys.vendor: ECS
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Tue Jan  3 10:33:48 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputSIGMACHIP Usb Mouse  MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   59776 
 vendor LCD
xserver.version: 2:1.17.1-0ubuntu3

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


** Tags: apport-bug compiz-0.9 i386 third-party-packages ubuntu vivid

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

Title:
  infectado con arcivos cript desde windows seven

Status in xorg package in Ubuntu:
  New

Bug description:
  dicsco compartido con windos seven

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-74.82-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-74-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Jan  3 10:47:22 2017
  DistUpgraded: 2016-09-22 00:37:21,126 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Device [1019:3184]
  InstallationDate: Installed on 2015-02-16 (686 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  MachineType: ECS H61H2-CM
  ProcEnviron:
   LANGUAGE=es_VE:es
   PATH=(custom, no user)
   LANG=es_VE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic 
root=UUID=8426958f-20c8-4974-b61a-da41d6109d75 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to vivid on 2016-09-22 (103 days ago)
  dmi.bios.date: 08/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.name: H61H2-CM
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.modalias: 

[Desktop-packages] [Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

[Leonardo Donelli]

I think this is caused by the (insane, IMO) patch for bug #191889 here:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/network-
manager/trusty/view/head:/debian/patches/lp191889_always_offline_with_unmanaged_devices.patch

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

Title:
  NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were 
created by Docker.
  Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged 
under the gnome system tray icon which is kind of annoying.
  I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 24 14:22:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-29 (632 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  IpRoute:
   default via 192.168.178.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
   192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.40
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-08-19T11:46:06.705439
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1630839] [NEW] Request for applying a patch to support OpenVSwitch in hostapd

[Leonardo Silva Amaral]

Public bug reported:

Hello Devs,

I'm requesting the patch https://github.com/helmut-
jacob/hostapd/commit/c89daaeca4ee90c8bc158e37acb1b679c823d7ab to be
applied in hostapd in Ubuntu. I compiled wpa-2.4 from Ubuntu sources
with the attached patch and worked well with ath9k_htc + OpenVSwitch
from Ubuntu 16.04.

Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: hostapd 1:2.4-0ubuntu6
Uname: Linux 4.6.3-040603-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Oct  5 23:40:38 2016
InstallationDate: Installed on 2016-01-14 (266 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
SourcePackage: wpa
UpgradeStatus: Upgraded to xenial on 2016-05-13 (145 days ago)
modified.conffile..etc.default.hostapd: [modified]
mtime.conffile..etc.default.hostapd: 2016-10-05T00:16:08.475114

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


** Tags: amd64 apport-bug xenial

** Patch added: "Patch I've applied to Ubuntu upstream wpa source package."
   
https://bugs.launchpad.net/bugs/1630839/+attachment/4755576/+files/hostapd_openvswitch.patch

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

Title:
  Request for applying a patch to support OpenVSwitch in  hostapd

Status in wpa package in Ubuntu:
  New

Bug description:
  Hello Devs,

  I'm requesting the patch https://github.com/helmut-
  jacob/hostapd/commit/c89daaeca4ee90c8bc158e37acb1b679c823d7ab to be
  applied in hostapd in Ubuntu. I compiled wpa-2.4 from Ubuntu sources
  with the attached patch and worked well with ath9k_htc + OpenVSwitch
  from Ubuntu 16.04.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hostapd 1:2.4-0ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct  5 23:40:38 2016
  InstallationDate: Installed on 2016-01-14 (266 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to xenial on 2016-05-13 (145 days ago)
  modified.conffile..etc.default.hostapd: [modified]
  mtime.conffile..etc.default.hostapd: 2016-10-05T00:16:08.475114

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

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

[Desktop-packages] [Bug 1630324] [NEW] Broadcom wifi dies in 60s cycles with 4.8 kernel

[Leonardo]

Public bug reported:

I have a Dell XPS 13 9350 with a Broadcom wifi adapter. Wifi connects
fine, but dies for around 5-10s (the signal dies completely, tools like
wavemon show "no interface data") in regular cycles of about 60s. dmesg
logs the same brcmfmac errors every minute or so: "brcmfmac:
brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)".

network-manager's icon doesn't change however (remains as if the adapter
was connected).

This issue started to affect me when using kernel 4.8 on Ubuntu 16.04. I
previously used kernel 4.7 and did not experience this bug.

I booted the 16.10 daily build and experienced exactly the same errors.

$ lspci | grep BCM4350
3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless Network 
Adapter (rev 08)

$ dmesg | grep brcm
[5.864558] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 22 
2015 06:16:26 version 7.35.180.119 (r594535) FWID 01-e791c176
[5.898803] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 
0x30)
[   74.991987] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 
0x30)
[  142.503220] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 
0x30)
...

$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu4
Uname: Linux 4.8.0-040800-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct  4 14:15:02 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-05-26 (131 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
 default via 192.168.0.1 dev wlp58s0  proto static  metric 600 
 169.254.0.0/16 dev wlp58s0  scope link  metric 1000 
 192.168.0.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.0.29  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

 wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/0  Guava 
Guest 1  68ae8dc2-ab23-42ef-9e41-ac8e9d91385a  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --
 ----
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: amd64 apport-bug xenial

** Summary changed:

- wifi connection dies intermittently in 60s cycles
+ Broadcom wifi dies in 60s cycles with 4.8 kernel

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

Title:
  Broadcom wifi dies in 60s cycles with 4.8 kernel

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a Dell XPS 13 9350 with a Broadcom wifi adapter. Wifi connects
  fine, but dies for around 5-10s (the signal dies completely, tools
  like wavemon show "no interface data") in regular cycles of about 60s.
  dmesg logs the same brcmfmac errors every minute or so: "brcmfmac:
  brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)".

  network-manager's icon doesn't change however (remains as if the
  adapter was connected).

  This issue started to affect me when using kernel 4.8 on Ubuntu 16.04.
  I previously used kernel 4.7 and did not experience this bug.

  I booted the 16.10 daily build and experienced exactly the same
  errors.

  $ lspci | grep BCM4350
  3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless 
Network Adapter (rev 08)

  $ dmesg | grep brcm
  [5.864558] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 
22 2015 06:16:26 version 7.35.180.119 (r594535) FWID 01-e791c176
  [5.898803] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code 
(0x30 0x30)
  [   74.991987] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code 
(0x30 0x30)
  [  142.503220] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code 
(0x30 0x30)
  ...

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  Uname: Linux 4.8.0-040800-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct  4 14:15:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  

[Desktop-packages] [Bug 1086783] Re: New PolicyKit 0.106 changes configuration file format

[Leonardo Borda]

@mdeslaur

Hi any chance we can revisit this use case again and add mazjs185
through the MIR process for newer Ubuntu versions?

Thank you

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

Title:
  New PolicyKit 0.106 changes configuration file format

Status in policykit-1 package in Ubuntu:
  Triaged
Status in policykit-1 package in Debian:
  Fix Released

Bug description:
  From the NEWS file:

  This is polkit 0.106. There's a major change in this release which is
  a switch from .pkla files (keyfile-format) to .rules files
  (JavaScript).

  We may want to hold off on the new version because it requires
  rewriting the configuration files, and adds a dependency on mozjs185,
  which will need a MIR (and getting a MIR may be problematic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1086783/+subscriptions

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

[Desktop-packages] [Bug 1574729] Re: Audio/Video not in sync on M10/frieza

[Leonardo Donelli]

Guys, if you can, keep up updated on this. I bought the M10 basically
only just to support Ubuntu Touch, knowing well that it wouldn't have
(yet) a lof of things Android has, but thinking that "at least I will be
able to watch videos on it, which is the primary use I have of a tablet
anyway".

Because of this bug, I can't really do that..

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

Title:
  Audio/Video not in sync on M10/frieza

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in frieza:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Watching a video (either with the media player or the browser) shows a
  lag between audio and video. It's out of sync for some hundred
  milliseconds, just enough to be very annoying while watching the
  video.

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

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

[Desktop-packages] [Bug 1546685] [NEW] package libsndfile1:amd64 1.0.25-9.1ubuntu0.15.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attem

[Leonardo Neves]

Public bug reported:

when i try install gparted the process stop and appear the error message

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: libsndfile1:amd64 1.0.25-9.1ubuntu0.15.10.1
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Wed Feb 17 16:22:55 2016
DuplicateSignature: package:libsndfile1:amd64:1.0.25-9.1ubuntu0.15.10.1:package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-02-17 (0 days ago)
InstallationMedia: It
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt  1.0.10.2ubuntu1
SourcePackage: libsndfile
Title: package libsndfile1:amd64 1.0.25-9.1ubuntu0.15.10.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package wily

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

Title:
  package libsndfile1:amd64 1.0.25-9.1ubuntu0.15.10.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libsndfile package in Ubuntu:
  New

Bug description:
  when i try install gparted the process stop and appear the error
  message

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libsndfile1:amd64 1.0.25-9.1ubuntu0.15.10.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Wed Feb 17 16:22:55 2016
  DuplicateSignature: 
package:libsndfile1:amd64:1.0.25-9.1ubuntu0.15.10.1:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-02-17 (0 days ago)
  InstallationMedia: It
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: libsndfile
  Title: package libsndfile1:amd64 1.0.25-9.1ubuntu0.15.10.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1533948] [NEW] Firefox developer edition doesn't emit any sound

[Fabián Leonardo Lopez Bernal]

Public bug reported:

It doesn't play anything, videos, notifications etc it must be a firefox
error because it works fine in google chrome

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 45.0~a2~hg20160113r298320-0ubuntu1~umd1~trusty [origin: 
LP-PPA-ubuntu-mozilla-daily-firefox-aurora]
ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
Uname: Linux 3.16.0-57-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  fabian 2766 F pulseaudio
 /dev/snd/controlC0:  fabian 2766 F pulseaudio
BuildID: 20160113160711
Channel: aurora
CurrentDesktop: GNOME
Date: Wed Jan 13 22:06:41 2016
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefSources:
 /usr/lib/firefox/defaults/pref/vendor-gre.js
 /usr/lib/firefox/defaults/pref/channel-prefs.js
 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 2015-03-14 (305 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
IpRoute:
 default via 192.168.0.1 dev wlan0  proto static 
 172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
 192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.3  metric 9
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefSources:
 /usr/lib/firefox/defaults/pref/vendor-gre.js
 /usr/lib/firefox/defaults/pref/channel-prefs.js
 prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile0 (Default) - LastVersion=38.0/20150511103818 (Out of date)
 Profile1 - LastVersion=45.0a2/20160113160711 (In use)
RelatedPackageVersions:
 totem-mozilla 3.10.1-1ubuntu4
 rhythmbox-mozilla 3.0.2-0ubuntu2
 gnome-shell   3.10.4-0ubuntu5.2
 google-talkplugin 5.41.0.0-1
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0YHW11
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/30/2014:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0YHW11:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Inspiron 7537
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug aurora-channel third-party-packages trusty

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

Title:
  Firefox developer edition doesn't emit any sound

Status in firefox package in Ubuntu:
  New

Bug description:
  It doesn't play anything, videos, notifications etc it must be a
  firefox error because it works fine in google chrome

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 45.0~a2~hg20160113r298320-0ubuntu1~umd1~trusty [origin: 
LP-PPA-ubuntu-mozilla-daily-firefox-aurora]
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-57-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fabian 2766 F pulseaudio
   /dev/snd/controlC0:  fabian 2766 F pulseaudio
  BuildID: 20160113160711
  Channel: aurora
  CurrentDesktop: GNOME
  Date: Wed Jan 13 22:06:41 2016
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
   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 2015-03-14 (305 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
   192.168.0.0/24 dev wlan0  proto kernel  scope 

[Desktop-packages] [Bug 1486014] [NEW] package python3-speechd 0.8-5ubuntu1 failed to install/upgrade: ErrorMessage: package python3-speechd is not ready for configuration cannot configure (current st

[Leonardo Pondian Tizzei]

Public bug reported:

error while upgrading from ubuntu 12.04 to 14.04

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python3-speechd 0.8-5ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-52.79~precise1-generic 3.5.7.33
Uname: Linux 3.5.0-52-generic x86_64
NonfreeKernelModules: symap_custom_dkms_x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Mon Aug 17 23:11:50 2015
DuplicateSignature: package:python3-speechd:0.8-5ubuntu1:ErrorMessage: package 
python3-speechd is not ready for configuration  cannot configure (current 
status `half-installed')
ErrorMessage: ErrorMessage: package python3-speechd is not ready for 
configuration  cannot configure (current status `half-installed')
InstallationDate: Installed on 2013-05-21 (818 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
PackageArchitecture: all
SourcePackage: speech-dispatcher
Title: package python3-speechd 0.8-5ubuntu1 failed to install/upgrade: 
ErrorMessage: package python3-speechd is not ready for configuration  cannot 
configure (current status `half-installed')
UpgradeStatus: Upgraded to trusty on 2015-08-18 (0 days ago)

** Affects: speech-dispatcher (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check trusty

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

Title:
  package python3-speechd 0.8-5ubuntu1 failed to install/upgrade:
  ErrorMessage: package python3-speechd is not ready for configuration
  cannot configure (current status `half-installed')

Status in speech-dispatcher package in Ubuntu:
  New

Bug description:
  error while upgrading from ubuntu 12.04 to 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python3-speechd 0.8-5ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-52.79~precise1-generic 3.5.7.33
  Uname: Linux 3.5.0-52-generic x86_64
  NonfreeKernelModules: symap_custom_dkms_x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Mon Aug 17 23:11:50 2015
  DuplicateSignature: package:python3-speechd:0.8-5ubuntu1:ErrorMessage: 
package python3-speechd is not ready for configuration  cannot configure 
(current status `half-installed')
  ErrorMessage: ErrorMessage: package python3-speechd is not ready for 
configuration  cannot configure (current status `half-installed')
  InstallationDate: Installed on 2013-05-21 (818 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
  PackageArchitecture: all
  SourcePackage: speech-dispatcher
  Title: package python3-speechd 0.8-5ubuntu1 failed to install/upgrade: 
ErrorMessage: package python3-speechd is not ready for configuration  cannot 
configure (current status `half-installed')
  UpgradeStatus: Upgraded to trusty on 2015-08-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1486014/+subscriptions

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

[Desktop-packages] [Bug 1292113] Re: CTRL+ALT+T - shortcut to open Terminal is does not work

[Leonardo Donelli]

I also still encounter this problem sporadically in 15.04

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

Title:
  CTRL+ALT+T - shortcut to open Terminal is does not work

Status in GNOME Terminal:
  New
Status in gnome-terminal package in Ubuntu:
  Fix Released

Bug description:
  The global shortcut CTRL+ALT+T to open a new terminal windows is missing in 
Ubuntu since 14.04
  Please reenable it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-terminal 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 13 18:01:32 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-10 (92 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to trusty on 2014-03-07 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1292113/+subscriptions

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

[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another

[Leonardo Nicolas]

I had this problem only on Elementary OS Freya and Ubuntu Gnome 14.10.
Currently I use Manjaro with Gnome 3.14.3 and I haven't had this problem
since.

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

Title:
  Second screen position isn't saved from one session to another

Status in elementary OS:
  Won't Fix
Status in Gnome Settings Daemon:
  New
Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  (Noticed on Ubuntu 14.04 beta 1 GNOME)
  At work I have a second screen, which I prefer to virtually put on the left 
side of my laptop screen.
  Using gnome-control-center I can change the position of the second without 
problem.
  But when I disconnect the second screen (to work on another place) and then 
connect it again
  OR if I just power off the laptop and turn it on again,
  the second screen position is set back to the default right position.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu53
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 14 08:50:00 2014
  InstallationDate: Installed on 2014-03-01 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

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

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

[Desktop-packages] [Bug 1059374] Re: Using Adwaita, many widgets are drawn with a solid black background

[Leonardo Nicolas]

I have a similar issue using Adwaita default theme in Gnome 3.14, but what is 
being drawn with a black solid background is the application system bar in some 
applications (firefox, pidgin, playonlinux, etc. See attached).
Is It the same bug?

** Attachment added: Seleção_007.png
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1059374/+attachment/4258452/+files/Sele%C3%A7%C3%A3o_007.png

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

Title:
  Using Adwaita, many widgets are drawn with a solid black background

Status in GTK+ GUI Toolkit:
  Fix Released
Status in Overlay Scrollbar:
  Confirmed
Status in “gnome-themes-standard” package in Ubuntu:
  Confirmed
Status in “gtk+3.0” package in Ubuntu:
  Fix Released
Status in “overlay-scrollbar” package in Ubuntu:
  Triaged

Bug description:
  When I use the Adwaita theme, some widgets end up being drawn with a
  black background after particular interactions. Here are two examples:

  If I open gedit, by default I see a new black document. The notebook
  widget is visible, and rendered correctly. As soon as I open another
  document (no matter if I close the existing one first), the entire
  widget starts being drawn with a black background.

  If I open System Settings, then click the (Ubuntu) Online Accounts
  panel, the box with the Remove account button has a solid black
  background. If, instead, I open Online Accounts directly from its
  launcher (run gnome-control-center credentials), everything is
  rendered correctly: there are no solid black backgrounds until I click
  All Settings and select the Online Accounts panel again.

  This has been happening consistently on two very different machines,
  both updated to Quantal from 12.04 using the upgrade tool.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libgtk-3-0 3.6.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.5.3-0ubuntu1
  Architecture: amd64
  Date: Sun Sep 30 21:18:23 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110906)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to quantal on 2012-08-26 (35 days ago)

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

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

[Desktop-packages] [Bug 1369251] Re: unity-settings-daemon doesn't load settings at boot

[Leonardo Donelli]

Nicolas, that works for me only for some settings like terminal profile,
DPI settings, and window theme. It doesn't work for icon theme, at least
it doesn't change the icons in the launcher.

My work around at the moment is to log out, move to Guest user in
login screen, move back to my user and login. That usually does it.

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

Title:
  unity-settings-daemon doesn't load settings at boot

Status in “unity-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  When booting my PC, my gtk and unity settings(gtk theme, icon theme, DPI 
scaling, ...) are not loaded and when I login I find myself in a default 
environment.
  If I log-out and login again, the settings are loaded correctly.

  Could this be caused by a really fast boot (3-4 seconds from GRUB to login 
screen, SSD) and a unity version of bug #574269?
  I've tried editing the autostart script to add a little sleep but it seems to 
work only occasionally.

  Attached x-0-greeter.log, is it  useful?

  Ubuntu 14.04.1
  unity-settings-daemon Version: 14.04.0+14.04.20140606-0ubuntu1

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

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

[Desktop-packages] [Bug 1287915] Re: pdf not rendered to device pixels on high-dpi screen

[Leonardo Donelli]

Will this be backported to trusty?

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

Title:
  pdf not rendered to device pixels on high-dpi screen

Status in Evince document viewer:
  Fix Released
Status in “evince” package in Ubuntu:
  Fix Released

Bug description:
  If the global scaling factor is set to something different from 1 on a
  high-dpi screen, pdfs look blurry because they are rendered to UI
  units instead of device pixels. This renders the main advantage of
  higher-resolution screens (sharp vector fonts/graphics) useless for
  the moment.

  org.gnome.desktop.interface.scaling-factor = 2
  As I've heard the used setting for the scaling factor might change.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar  4 22:02:23 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-02-02 (30 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201)
  KernLog:
   
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1287915] Re: pdf not rendered to device pixels on high-dpi screen

[Leonardo Donelli]

I proposed evince as for a backport: https://bugs.launchpad.net/trusty-
backports/+bug/1377281

If you want to help, mark yourself as afflicted by the bug and help with
the testing.

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

Title:
  pdf not rendered to device pixels on high-dpi screen

Status in Evince document viewer:
  Fix Released
Status in “evince” package in Ubuntu:
  Fix Released

Bug description:
  If the global scaling factor is set to something different from 1 on a
  high-dpi screen, pdfs look blurry because they are rendered to UI
  units instead of device pixels. This renders the main advantage of
  higher-resolution screens (sharp vector fonts/graphics) useless for
  the moment.

  org.gnome.desktop.interface.scaling-factor = 2
  As I've heard the used setting for the scaling factor might change.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar  4 22:02:23 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-02-02 (30 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201)
  KernLog:
   
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1065810] Re: Remmina remote desktop window not visible when minimized

[Leonardo Corato]

Same problem in Trusty and also in Utopic. (fastidio :D )

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

Title:
  Remmina remote desktop window not visible when minimized

Status in Unity:
  Confirmed
Status in “remmina” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  When I minimize an RDP session window, the icon disapear from the
  Unity's taskbar. There is no way to bring it back. The only solution
  is to #killall remmina, and then reopen the session.

  A workaround is to go to remmina settings and disable the tray icon,
  which is a neat feature.

  Tha bug #782331 claims that it is fixed, but that is wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: remmina 1.0.0-1ubuntu6.1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Fri Oct 12 15:07:16 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120316)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1299629] Re: [V320-M.BG31P1, Intel PantherPoint HDMI, Digital Out, HDMI] No sound at all

[Leonardo]

Great! Thanks!

Very simple solution, but impossible to find unless by accident!
It worked, just pressing + on the monitor!

:-)

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

Title:
  [V320-M.BG31P1, Intel PantherPoint HDMI, Digital Out, HDMI] No sound
  at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  no sound in LG All in One with Ubuntu 13.10

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mirkos 9009 F pulseaudio
   /dev/snd/pcmC0D3p:   mirkos 9009 F...m pulseaudio
  Date: Sat Mar 29 20:06:47 2014
  InstallationDate: Installed on 2014-03-23 (6 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mirkos 9009 F pulseaudio
   /dev/snd/pcmC0D3p:   mirkos 9009 F...m pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [V320-M.BG31P1, Intel PantherPoint HDMI, Digital Out, HDMI] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: VICTSF90
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: V720
  dmi.board.vendor: LG Electronics
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrVICTSF90:bd08/08/2013:svnLGElectronics:pnV320-M.BG31P1:pvr1.0:rvnLGElectronics:rnV720:rvr1.0:cvnLGElectronics:ct13:cvr0.1:
  dmi.product.name: V320-M.BG31P1
  dmi.product.version: 1.0
  dmi.sys.vendor: LG Electronics

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1299629/+subscriptions

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

[Desktop-packages] [Bug 976306] Re: must start application at least twice for it to work

[Leonardo Borda]

Same thing here

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

Title:
  must start application at least twice for it to work

Status in “pidgin” package in Ubuntu:
  Confirmed

Bug description:
  You have to start the app and then close it and start it again for it
  to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pidgin 1:2.10.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sat Apr  7 21:32:54 2012
  ExecutablePath: /usr/bin/pidgin
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: pidgin
  UpgradeStatus: Upgraded to precise on 2012-04-06 (1 days ago)

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

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

[Desktop-packages] [Bug 1292528] [NEW] Unity lockscreen not showing properly when a fullscreen window is focused

[Leonardo Robol]

Public bug reported:

I'm experiencing an issues with the new Unity Lockscreen that has just
landed in trusty. It's working very nicely most of the time but, when I
have a full screen window focused (say, A Chrome window, a full screen
video, etc.), the lock screen activation isn't working. More precisely,
I can se all the windows on my workspace as if they were set with a
partial opacity. A screenshot of the behaviour (with fullscreen Chrome +
a terminal) is attached to this report.

Typing my password and pressing ENTER unlocks the screen correctly, as
expected.

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

** Attachment added: Screenshot documenting the strange behaviour
   
https://bugs.launchpad.net/bugs/1292528/+attachment/4023955/+files/gnome-screensaver.png

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

Title:
  Unity lockscreen not showing properly when a fullscreen window is
  focused

Status in “unity” package in Ubuntu:
  New

Bug description:
  I'm experiencing an issues with the new Unity Lockscreen that has just
  landed in trusty. It's working very nicely most of the time but, when
  I have a full screen window focused (say, A Chrome window, a full
  screen video, etc.), the lock screen activation isn't working. More
  precisely, I can se all the windows on my workspace as if they were
  set with a partial opacity. A screenshot of the behaviour (with
  fullscreen Chrome + a terminal) is attached to this report.

  Typing my password and pressing ENTER unlocks the screen correctly, as
  expected.

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

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

[Desktop-packages] [Bug 1292528] Re: Unity lockscreen not showing properly when a fullscreen window is focused

[Leonardo Robol]

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

Sorry for not having seen it before. This seems to be a duplicate of bug
#1291571.

** This bug has been marked a duplicate of bug 1291571
   Locking while a window is in fullscreen results in lockscreen being nearly 
invisible

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

Title:
  Unity lockscreen not showing properly when a fullscreen window is
  focused

Status in “unity” package in Ubuntu:
  New

Bug description:
  I'm experiencing an issue with the new Unity Lockscreen that has just
  landed in trusty. It's working very nicely most of the time but, when
  I have a full screen window focused (say, A Chrome window, a full
  screen video, etc.), the lock screen activation isn't working. More
  precisely, I can se all the windows on my workspace as if they were
  set with a partial opacity. A screenshot of the behaviour (with
  fullscreen Chrome + a terminal) is attached to this report.

  Typing my password and pressing ENTER unlocks the screen correctly, as
  expected.

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

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

[Desktop-packages] [Bug 714259] Re: Printer driver for Samsung CLP-510 (Splix)

[Leonardo Hamada]

If I remember correctly, this version of ubuntu shipped with a new
gstoraster cups utility. The included pstoraster in this ubuntu version
does not work well with splix.

Since both commands accepts the same arguments, you could make a synlink
pstoraster-gstoraster to replace the existing pstoraster.


Should work,


Bye

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

Title:
  Printer driver for Samsung CLP-510 (Splix)

Status in SpliX:
  Unknown
Status in “splix” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: software-center

   The printer dosn't print the 2nd and all further pages correct. The
  1st is correct. It's a bug in the 2.0 version of splix. Version 1.0.1
  printed correct

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: software-center 3.0.7
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic i686
  Architecture: i386
  Date: Sun Feb  6 18:54:27 2011
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   LANG=de_DE.utf8
   SHELL=/bin/bash
  SourcePackage: software-center

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

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

[Desktop-packages] [Bug 1280422] [NEW] black background when the dash is open

[Leonardo Alvarado]

Public bug reported:

al abrir el dash, este se torna oscuro en todo momento, y es incómodo
trabajar asi aveces.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Feb 14 14:50:01 2014
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
EcryptfsInUse: Yes
GraphicsCard:
 Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:048b]
   Subsystem: Dell Device [1028:048b]
InstallationDate: Installed on 2013-12-30 (46 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
MachineType: Dell Inc. Inspiron 1090
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=c1e96d08-afa4-498e-9a48-83908a2a2a08 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: Inspiron 1090
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A06
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd08/23/2011:svnDellInc.:pnInspiron1090:pvrA06:rvnDellInc.:rnInspiron1090:rvrA06:cvnDellInc.:ct8:cvrA06:
dmi.product.name: Inspiron 1090
dmi.product.version: A06
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Fri Feb 14 14:34:36 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   21569 
 vendor SEC
xserver.version: 2:1.14.5-1ubuntu2~saucy1

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


** Tags: amd64 apport-bug compiz-0.9 saucy third-party-packages ubuntu

** Attachment added: Captura de pantalla de 2014-02-14 14:58:31.png
   
https://bugs.launchpad.net/bugs/1280422/+attachment/3981076/+files/Captura%20de%20pantalla%20de%202014-02-14%2014%3A58%3A31.png

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

Title:
  black background when the dash is open

Status in “unity” package in Ubuntu:
  New

Bug description:
  al abrir el dash, este se torna oscuro en todo momento, y es incómodo
  trabajar asi aveces.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Feb 14 14:50:01 2014
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:048b]
 Subsystem: Dell Device [1028:048b]
  InstallationDate: Installed on 2013-12-30 (46 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Inspiron 1090
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=c1e96d08-afa4-498e-9a48-83908a2a2a08 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: Inspiron 1090
  dmi.board.vendor: Dell Inc.
  

[Desktop-packages] [Bug 1276175] [NEW] package shared-mime-info 1.1-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134

[Adrian Leonardo]

Public bug reported:

recien instalo ubuntu porque decidi dejar de lado mi win 7 pirata de
mocosoft pero no puedo instalar las actualizaciones que etan disponibles
necesito saber que hacer tambien tengo problemas con firefox se cierra
solo cuando estoi navegando por la web

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: shared-mime-info 1.1-0ubuntu5
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
Date: Tue Feb  4 09:10:32 2014
DuplicateSignature: package:shared-mime-info:1.1-0ubuntu5:subprocess installed 
post-installation script returned error exit status 134
ErrorMessage: subprocess installed post-installation script returned error exit 
status 134
InstallationDate: Installed on 2014-02-03 (0 days ago)
InstallationMedia: It
MarkForUpload: True
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.1-0ubuntu5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 134
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 need-duplicate-check saucy

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

Title:
  package shared-mime-info 1.1-0ubuntu5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 134

Status in “shared-mime-info” package in Ubuntu:
  New

Bug description:
  recien instalo ubuntu porque decidi dejar de lado mi win 7 pirata de
  mocosoft pero no puedo instalar las actualizaciones que etan
  disponibles necesito saber que hacer tambien tengo problemas con
  firefox se cierra solo cuando estoi navegando por la web

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: shared-mime-info 1.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  Date: Tue Feb  4 09:10:32 2014
  DuplicateSignature: package:shared-mime-info:1.1-0ubuntu5:subprocess 
installed post-installation script returned error exit status 134
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 134
  InstallationDate: Installed on 2014-02-03 (0 days ago)
  InstallationMedia: It
  MarkForUpload: True
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.1-0ubuntu5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 134
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1276175/+subscriptions

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

[Desktop-packages] [Bug 1220328] Re: package fglrx-pxpress 0.3~hybrid0.0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[leonardo]

need help intel/redonATI 5000 serie HP-G62-NEEDBOOK

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

Title:
  package fglrx-pxpress 0.3~hybrid0.0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in “fglrx-pxpress” package in Ubuntu:
  Fix Released

Bug description:
  this error popped up when installing mongodb on ubuntu 12.04.3

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: fglrx-pxpress 0.3~hybrid0.0.1
  ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.4
  AptOrdering:
   mongodb-10gen: Install
   fglrx-pxpress: Configure
   mongodb-10gen: Configure
  Architecture: amd64
  Date: Tue Sep  3 22:06:39 2013
  DuplicateSignature: package:fglrx-pxpress:0.3~hybrid0.0.1:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: fglrx-pxpress
  Title: package fglrx-pxpress 0.3~hybrid0.0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-pxpress/+bug/1220328/+subscriptions

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

[Desktop-packages] [Bug 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c

[Leonardo Lazarte]

The standard for obtaining c-cedilla was working ok on my installation
until updating to 13.10. Unfortunately, it is now broken and I could not
find a way to write this letter, although I tried all the suggestions in
this thread.

** Package changed: gtk+2.0 (Ubuntu) = ubuntu

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

Title:
  cedilla appears as accented c (ć instead of ç) when typing 'c

Status in Ubuntu:
  Confirmed

Bug description:
  
  When typing in a US-international keyboard with dead-keys (or 
UK-international), 
  typing 'c results in an accented c instead of a cedilla.

  There is a workaround, which is editing the

  /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules

  file and changing the line

  cedilla Cedilla gtk20 /usr/share/locale
  az:ca:co:fr:gv:oc:pt:sq:tr:wa

  to

  cedilla Cedilla gtk20 /usr/share/locale
  az:ca:co:fr:gv:oc:pt:sq:tr:wa:en

  (add the 'en' at the end).

  However, every time some update on this file is applied, one looses the 
change,
  and we get back to the accented c. That means having to modify the file again,
  logout and login.

  For me this is no problem. But for my brother, mom, dad, etc, it is always 
something
  that at least makes me less proud of having convinced them to use Ubuntu, 
because
  they don't know what to do each time this happens.

  I think we really need a configurable keyboard layout, or at least (and that 
would
  be very easy), the inclusion of alternate layouts on install that for the 
dead-key
  options (as US-deadkey and UK-deakey), alternate layouts as 
US-deadkey-cedilla.

  This change is relevant for at least Portuguese and French.

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

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

[Desktop-packages] [Bug 1238346] Re: on bootup wrong keyboard layout is recognized

[Leonardo Donelli]

Same problem with Italian and English (USA) layout.
After booting up Italian layout is showed in the panel and selected, but the 
real keyboard layout is actually English (USA).
Selecting the Italian layout in the indicator (even though it's already 
selected) correctly sets the layout.

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

Title:
  on bootup wrong keyboard layout is recognized

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  This is a regression. 
  I have two keyboard layouts activated, the Dvorak and the English US. The 
Dvorak should be the default keyboard. That is the way I have it set up, and it 
 shows up in the task bar on top as En1, which is the Dvorak.
  However, when I start to type, it starts in QUERTY. 
  ??
  To correct this, I go to the task bar (where it shows EN1, or Dvorak), 
re-select the Dvorak, and then everything is fine. 
  ??

  I have another minor problem which should probably go on another bug, but 
happened at the same time. 
  CTL-ALT-T doesn't bring up the terminal any more. No matter what keyboard I'm 
using.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.1+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Oct 10 21:20:39 2013
  InstallationDate: Installed on 2013-08-12 (60 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130811)
  MarkForUpload: True
  SourcePackage: unity
  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/1238346/+subscriptions

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

[Desktop-packages] [Bug 848164] Re: Auto connect to 3G network only works after manually enabling mobile broadband after modem inserted/bootup/resume

[Leonardo Borda]

@mariusko

Hi, did you have a chance to test the upstream patch ?

Leonardo

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

Title:
  Auto connect to 3G network only works after manually enabling mobile
  broadband after modem inserted/bootup/resume

Status in NetworkManager:
  Confirmed
Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not connect to my 3G provider at login, even
  though it is configured for automatic connection.

  What I expect:
  - When selecting the option connect automatically in the network-setting 
for a mobile connection, it should connect automatically, like it has until 
Ubuntu 11.04.

  What happens:
  - When I plug in the modem (USB; e.g. UMTS-Stick), it appears as available 
connection, but does not connect;

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: network-manager 0.9.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.22.1-0ubuntu2
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Mon Sep 12 20:32:01 2011
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.6
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  Keyfiles: Error: [Errno 2] No such file or directory
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to oneiric on 2011-09-12 (0 days ago)

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

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