date:20181213

Launchpad has imported 5 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=28882.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2010-07-01T21:56:30+00:00 E-tim-w wrote:

Created attachment 36674
gdb trace of xorg-server seg fault

I'm running LXDE on an Arch Linux system and after a recent upgrade, now
xorg-server exits with a segmentation fault whenever I try to run
lxterminal (the terminal application in the LXDE suite). It happens
every time and immediately after invoking the program (before a window
even appears). I haven't been able to reproduce it with any other
application.


I'm attaching a gdb backtrace collected according to these instructions:

http://wiki.x.org/wiki/Development/Documentation/ServerDebugging?highlight=(segmentation)|(fault)

Since it looks like I only get one attachment, see below for an excerpt
from Xorg.0.log with a backtrace. There's also a gdb trace from
lxterminal showing that it exits without a seg fault.


Here's some version info for my system:

lxterminal 0.1.7-1
lxde-common 0.5.0-1

kernel 2.6.34-ARCH


$ X -version

X.Org X Server 1.8.0
Release Date: 2010-04-02
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.34-ARCH i686 
Current Operating System: Linux deimos 2.6.34-ARCH #1 SMP PREEMPT Sat Jun 19 
13:06:16 CEST 2010 i686
Kernel command line: 
root=/dev/disk/by-uuid/97258355-411c-456d-9ff4-d686b0a3408d ro
Build Date: 01 July 2010  10:29:43PM
 
Current version of pixman: 0.18.2


### excerpt from Xorg.0.log:

[  4480.061] 
Backtrace:
[  4480.061] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80df05b]
[  4480.062] 1: /usr/bin/X (0x8048000+0x63da5) [0x80abda5]
[  4480.062] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb788340c]
[  4480.062] 3: /usr/lib/xorg/modules/libfb.so (image_from_pict+0x3b8) 
[0xb72e6a58]
[  4480.062] 4: /usr/lib/xorg/modules/libfb.so (fbComposite+0x121) [0xb72e6c51]
[  4480.062] 5: /usr/bin/X (0x8048000+0xc7053) [0x810f053]
[  4480.062] 6: /usr/bin/X (CompositePicture+0x290) [0x8103710]
[  4480.062] 7: /usr/bin/X (0x8048000+0x12f0a2) [0x81770a2]
[  4480.062] 8: /usr/bin/X (0x8048000+0x12eea8) [0x8176ea8]
[  4480.063] 9: /usr/bin/X (0x8048000+0x12eea8) [0x8176ea8]
[  4480.063] 10: /usr/bin/X (0x8048000+0x9885f) [0x80e085f]
[  4480.063] 11: /usr/bin/X (BlockHandler+0x58) [0x80921f8]
[  4480.063] 12: /usr/bin/X (WaitForSomething+0x10c) [0x80a7fec]
[  4480.063] 13: /usr/bin/X (0x8048000+0x214d0) [0x80694d0]
[  4480.063] 14: /usr/bin/X (0x8048000+0x1a4b5) [0x80624b5]
[  4480.063] 15: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb75c5c76]
[  4480.064] 16: /usr/bin/X (0x8048000+0x1a0a1) [0x80620a1]
[  4480.064] Segmentation fault at address 0x20
[  4480.064] 
Fatal server error:
[  4480.064] Caught signal 11 (Segmentation fault). Server aborting
[  4480.064] 


### gdb launch of lxterminal:

Reading symbols from /usr/bin/lxterminal...done.
(gdb) run
Starting program: /usr/bin/lxterminal 
[Thread debugging using libthread_db enabled]
[New Thread 0xb58c0b70 (LWP 23639)]
[Thread 0xb58c0b70 (LWP 23639) exited]

Program exited with code 01.
(gdb)

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/705078/comments/0


On 2010-07-04T11:06:21+00:00 E-tim-w wrote:

Created attachment 36745
gdb trace with debug symbols for libpixman

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/705078/comments/1


On 2010-07-04T11:09:17+00:00 E-tim-w wrote:

Created attachment 36746
gdb stack trace with code context for the calls

gdb short stack trace with the full function source code (w/line
numbers) for each routine in the trace

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/705078/comments/2


On 2010-07-06T08:54:51+00:00 Soren-sandmann wrote:

Apparently, the server calls set_has_client_clip() with a NULL image:

   #0  0xb75cb7bc in pixman_image_set_has_client_clip (image=0x0, 
client_clip=1) at pixman-image.c:530
   No locals.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/705078/comments/3


On 2018-12-13T22:23:55+00:00 Gitlab-migration wrote:

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/402.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-

[Desktop-packages] [Bug 996801] Re: Keybord gets sluggish after a while (after upgrade from 11.10 to 12.04)

Launchpad has imported 22 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=52611.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2012-07-28T06:06:47+00:00 Jonathan Nieder wrote:

Hi,

As described at  and
, some users accidentally
holding down shift too long end up pressing some other modifiers and
then are confused when applications stop accepting input.  Restarting
the X server fixes it, as does holding down shift again if you know to
do so.

Some people reporting running into this scenario:

 Vincent Lefevre
 Wookey
 Bjørn Mork

They are bright people, and if they find this counterintuitive, I expect
many others will as well.  A common way to run into this is to hold down
shift while performing some action with the mouse that takes at least
10 seconds.

Julien Cristau pointed reporters to the blog entry

 http://who-t.blogspot.fr/2012/06/xkb-slowkeys.html

so it looks like this usability problem is known, but there doesn't seem
to be a bug filed for it.

Of course, fixing it is tricky.  The same annoying keyboard shortcut is
used on Windows, although there the result is an annoying dialog box
popping up instead of the keyboard seeming to just stop working.  (I don't
suggest copying that. :))  Making sure this feature remains discoverable
might require some coordination with Desktop Environment authors, to put
an appropriate entry in a keyboard layout switcher on the panel, for
example (sorry, I'm out of touch with the DE world).

Of course, as long as the education problem is solved somehow, the
appropriate fix on the X side is obvious.  The keyboard shortcut needs
to be harder to accidentally trip.  Perhaps it could be made configurable
to allow people to experiment to find a good one.

Sorry for the ramble, and hope that helps,
Jonathan

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
evdev/+bug/996801/comments/24

On 2012-07-28T06:17:19+00:00 Jonathan Nieder wrote:

(In reply to comment #0)
> As described at  and
> , some users accidentally
> holding down shift too long end up pressing some other modifiers and
> the

Um, I mixed up Sticky Keys and Slow Keys, sorry.  So modifiers are not
involved --- the point is that the keyboard really does stop accepting
normal input unless you hold down each key for a while.

Another quick datum: on Mac OS X, holding down the Return key for
4 seconds produces a beep.  Continuing to hold it for 4 more seconds
turns on Slow Keys.  Enter seems like a less common key to hold down
than Shift and the beep provides useful feedback, so one nice approach
might be to copy them.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
evdev/+bug/996801/comments/25

On 2012-07-30T19:14:53+00:00 Alan Coopersmith wrote:

(In reply to comment #0)
> the appropriate fix on the X side is obvious.  The keyboard shortcut needs
> to be harder to accidentally trip.

Unfortunately, that's rather inappropriate for reasons that should also be
obvious - making it harder to activate makes it harder for the people who
need this functionality (because they have motor control issues with their
hands) to enable it on their own.

I absolutely agree that the desktop environments should provide more feedback
and notification here, as I've had to help a number of people who hit this
and had no idea why, but we can't change that in the X server.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
evdev/+bug/996801/comments/26

On 2012-07-30T19:18:45+00:00 Jonathan Nieder wrote:

(In reply to comment #2)
> (In reply to comment #0)

>> the appropriate fix on the X side is obvious.  The keyboard shortcut needs
>> to be harder to accidentally trip.
>
> Unfortunately, that's rather inappropriate for reasons that should also be
> obvious - making it harder to activate makes it harder for the people who
> need this functionality

Perhaps you missed the word "accidentally" and the example of using
the "enter" key instead of shift.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
evdev/+bug/996801/comments/27

On 2012-07-30T23:18:26+00:00 Vincent-fdt wrote:

(In reply to comment #2)
> I absolutely agree that the desktop environments should provide more feedback
> and notification here,

Not everyone uses a desktop environment. But

[Desktop-packages] [Bug 782406] Re: LibreOffice Writer Document Compare (regression)

2018-12-13 Thread VanillaMozilla

Sorry, I forgot to mention that I have a 642 word document with 4
changes totalling 6 words, and yet the whole document is marked as
changed, until I changed the Comparison option.  I even changed the two
documents to plain text, and it still marked the whole document as
changed.

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

Title:
  LibreOffice Writer Document Compare (regression)

Status in libreoffice package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: libreoffice

  Comparing two files has reverted to the old OOo behaviour of flagging
  entire long sequences of paragraphs as different, when in fact they
  are actually identical except maybe for just one or two minor
  typographical differences.

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

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

[Desktop-packages] [Bug 782406] Re: LibreOffice Writer Document Compare (regression)

2018-12-13 Thread VanillaMozilla

This problem occurs on some documents but not others.

I had success in fixing the problem (I have tried it on only one
document) by changing Tools > Options > LibreOffice Writer > Comparison
from "Auto" to "By word".

That may narrow the bug down a bit.  I can supply an example privately
and file another bug report if necessary, but will do so only if someone
will take a look at it.

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

Title:
  LibreOffice Writer Document Compare (regression)

Status in libreoffice package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: libreoffice

  Comparing two files has reverted to the old OOo behaviour of flagging
  entire long sequences of paragraphs as different, when in fact they
  are actually identical except maybe for just one or two minor
  typographical differences.

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

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

[Desktop-packages] [Bug 1808123] Re: Fullscreen view lands on another monitor

2018-12-13 Thread Olivier Tilloy

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=122085
   Importance: Unknown
   Status: Unknown

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

Title:
  Fullscreen view lands on another monitor

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  New

Bug description:
  As described above. I work in the classroom with my notebook, to which I have 
connected a beamer. Sometimes I write things down in the Writer and show it via 
the beamer. I would like to use the fullscreen mode here. 
  Unfortunately, the fullscreen mode is always displayed on the internal 
monitor, even if the window with the Writer maximized was previously displayed 
on the beamer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 12 10:44:00 2018
  InstallationDate: Installed on 2018-11-30 (11 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1808123/+subscriptions

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

[Desktop-packages] [Bug 1808398] Re: top right menu does not display when activated

Additional information that might matter... I have a second monitor
connected via HDMI output. Monitor is 1600x1200 and is rotated 90
degrees. It had problems on 18.04 with Wayland
(https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808226) and
I have attached the output of xrandr when run from Xorg.

This does matter. I rebooted with the second monitor not connected and
the problem with the menu does not occur.

** Attachment added: "xrandr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808398/+attachment/5222187/+files/xrandr.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/1808398

Title:
  top right menu does not display when activated

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  1) Install Ubuntu 18.04.1 via debbootstrap
  2) Install ubuntu-desktop package
  3) Install vanilla-desktop package
  4) Upgrade to 18.10 using the Software GUI
  5) Log into Ubuntu on Wayland
  6) Click right end of top bar, menu drops down.
  7) Mouse over menu, no visual feedback of focus (as with Ubuntu on Xorg)
  8) Interact with menu items - there is no visual feedback. For example 
   - sliding back and forth on the screen brightness slider causes the screen 
brightness to change as expected but the slider does not reflect changes. 
Clicking on the right end of the top bar causes the menu to deactivate but 
before it does, the slider position updates.
   - click on the user name and nothing appears to happen. Click below it where 
the submenu would appear causes the submenu to activate. (the logout dialog 
appears.)

  I'm not sure if steps 1-4 are required vs. just installing 18.10 but I
  list it in case this results from left over settings from 18.04
  installing via debbootstrap.

  hbarta@saugage:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10
  hbarta@saugage:~$ 

  hbarta@saugage:~$ apt-cache policy gnome-shell mutter xwayland gnome-menus 
libgnome-menu-3-0:amd64
  gnome-shell:
Installed: 3.30.1-2ubuntu1.18.10.1
Candidate: 3.30.1-2ubuntu1.18.10.1
Version table:
   *** 3.30.1-2ubuntu1.18.10.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.30.1-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  mutter:
Installed: 3.30.2-1~ubuntu18.10.1
Candidate: 3.30.2-1~ubuntu18.10.1
Version table:
   *** 3.30.2-1~ubuntu18.10.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.30.1-1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  xwayland:
Installed: 2:1.20.1-3ubuntu2.1
Candidate: 2:1.20.1-3ubuntu2.1
Version table:
   *** 2:1.20.1-3ubuntu2.1 500
  500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:1.20.1-3ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  gnome-menus:
Installed: 3.13.3-11ubuntu2
Candidate: 3.13.3-11ubuntu2
Version table:
   *** 3.13.3-11ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  libgnome-menu-3-0:
Installed: 3.13.3-11ubuntu2
Candidate: 3.13.3-11ubuntu2
Version table:
   *** 3.13.3-11ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  hbarta@saugage:~$ 

  
  Expected behavior: menu provides visual feedback to clicks. Underlying action 
seems to happen but there is no hint of that or display of submenus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 13 11:41:23 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-12-13 (0 days ago)
  mtime.conffile..etc.logrotate.d.apport: 2018-12-12T13:31:49.347693

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

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

[Desktop-packages] [Bug 1808398] Re: top right menu does not display when activated

If you're using Intel graphics then I don't think this is going to be a
driver issue.

My first guess is that a gnome-shell extension has broken rendering for
the panel menu. Please uninstall (not just disable) all non-standard*
gnome-shell extensions and tell us if the problem persists without
extensions installed.

* non-standard means everything other than gnome-shell-extension-
appindicator and gnome-shell-extension-ubuntu-dock.

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

Title:
  top right menu does not display when activated

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  1) Install Ubuntu 18.04.1 via debbootstrap
  2) Install ubuntu-desktop package
  3) Install vanilla-desktop package
  4) Upgrade to 18.10 using the Software GUI
  5) Log into Ubuntu on Wayland
  6) Click right end of top bar, menu drops down.
  7) Mouse over menu, no visual feedback of focus (as with Ubuntu on Xorg)
  8) Interact with menu items - there is no visual feedback. For example 
   - sliding back and forth on the screen brightness slider causes the screen 
brightness to change as expected but the slider does not reflect changes. 
Clicking on the right end of the top bar causes the menu to deactivate but 
before it does, the slider position updates.
   - click on the user name and nothing appears to happen. Click below it where 
the submenu would appear causes the submenu to activate. (the logout dialog 
appears.)

  I'm not sure if steps 1-4 are required vs. just installing 18.10 but I
  list it in case this results from left over settings from 18.04
  installing via debbootstrap.

  hbarta@saugage:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10
  hbarta@saugage:~$ 

  hbarta@saugage:~$ apt-cache policy gnome-shell mutter xwayland gnome-menus 
libgnome-menu-3-0:amd64
  gnome-shell:
Installed: 3.30.1-2ubuntu1.18.10.1
Candidate: 3.30.1-2ubuntu1.18.10.1
Version table:
   *** 3.30.1-2ubuntu1.18.10.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.30.1-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  mutter:
Installed: 3.30.2-1~ubuntu18.10.1
Candidate: 3.30.2-1~ubuntu18.10.1
Version table:
   *** 3.30.2-1~ubuntu18.10.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.30.1-1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  xwayland:
Installed: 2:1.20.1-3ubuntu2.1
Candidate: 2:1.20.1-3ubuntu2.1
Version table:
   *** 2:1.20.1-3ubuntu2.1 500
  500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:1.20.1-3ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  gnome-menus:
Installed: 3.13.3-11ubuntu2
Candidate: 3.13.3-11ubuntu2
Version table:
   *** 3.13.3-11ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  libgnome-menu-3-0:
Installed: 3.13.3-11ubuntu2
Candidate: 3.13.3-11ubuntu2
Version table:
   *** 3.13.3-11ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  hbarta@saugage:~$ 

  
  Expected behavior: menu provides visual feedback to clicks. Underlying action 
seems to happen but there is no hint of that or display of submenus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 13 11:41:23 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-12-13 (0 days ago)
  mtime.conffile..etc.logrotate.d.apport: 2018-12-12T13:31:49.347693

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

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

[Desktop-packages] [Bug 1808398] Re: top right menu does not display when activated

second requested file

This is a Lenovo Y50 which also has an Nvidia 860m (IIRC) which does not
appear in the list of PCI devices so I must have disabled it in the BIOS
or it is no longer working.

Thank you for your help.

** Attachment added: "dpkg -l"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808398/+attachment/5222185/+files/allpackages.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/1808398

Title:
  top right menu does not display when activated

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  1) Install Ubuntu 18.04.1 via debbootstrap
  2) Install ubuntu-desktop package
  3) Install vanilla-desktop package
  4) Upgrade to 18.10 using the Software GUI
  5) Log into Ubuntu on Wayland
  6) Click right end of top bar, menu drops down.
  7) Mouse over menu, no visual feedback of focus (as with Ubuntu on Xorg)
  8) Interact with menu items - there is no visual feedback. For example 
   - sliding back and forth on the screen brightness slider causes the screen 
brightness to change as expected but the slider does not reflect changes. 
Clicking on the right end of the top bar causes the menu to deactivate but 
before it does, the slider position updates.
   - click on the user name and nothing appears to happen. Click below it where 
the submenu would appear causes the submenu to activate. (the logout dialog 
appears.)

  I'm not sure if steps 1-4 are required vs. just installing 18.10 but I
  list it in case this results from left over settings from 18.04
  installing via debbootstrap.

  hbarta@saugage:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10
  hbarta@saugage:~$ 

  hbarta@saugage:~$ apt-cache policy gnome-shell mutter xwayland gnome-menus 
libgnome-menu-3-0:amd64
  gnome-shell:
Installed: 3.30.1-2ubuntu1.18.10.1
Candidate: 3.30.1-2ubuntu1.18.10.1
Version table:
   *** 3.30.1-2ubuntu1.18.10.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.30.1-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  mutter:
Installed: 3.30.2-1~ubuntu18.10.1
Candidate: 3.30.2-1~ubuntu18.10.1
Version table:
   *** 3.30.2-1~ubuntu18.10.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.30.1-1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  xwayland:
Installed: 2:1.20.1-3ubuntu2.1
Candidate: 2:1.20.1-3ubuntu2.1
Version table:
   *** 2:1.20.1-3ubuntu2.1 500
  500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:1.20.1-3ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  gnome-menus:
Installed: 3.13.3-11ubuntu2
Candidate: 3.13.3-11ubuntu2
Version table:
   *** 3.13.3-11ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  libgnome-menu-3-0:
Installed: 3.13.3-11ubuntu2
Candidate: 3.13.3-11ubuntu2
Version table:
   *** 3.13.3-11ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  hbarta@saugage:~$ 

  
  Expected behavior: menu provides visual feedback to clicks. Underlying action 
seems to happen but there is no hint of that or display of submenus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 13 11:41:23 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-12-13 (0 days ago)
  mtime.conffile..etc.logrotate.d.apport: 2018-12-12T13:31:49.347693

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

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

[Desktop-packages] [Bug 1808398] Re: top right menu does not display when activated

first requested file

** Attachment added: "lspci -k"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808398/+attachment/5222182/+files/pci.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/1808398

Title:
  top right menu does not display when activated

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  1) Install Ubuntu 18.04.1 via debbootstrap
  2) Install ubuntu-desktop package
  3) Install vanilla-desktop package
  4) Upgrade to 18.10 using the Software GUI
  5) Log into Ubuntu on Wayland
  6) Click right end of top bar, menu drops down.
  7) Mouse over menu, no visual feedback of focus (as with Ubuntu on Xorg)
  8) Interact with menu items - there is no visual feedback. For example 
   - sliding back and forth on the screen brightness slider causes the screen 
brightness to change as expected but the slider does not reflect changes. 
Clicking on the right end of the top bar causes the menu to deactivate but 
before it does, the slider position updates.
   - click on the user name and nothing appears to happen. Click below it where 
the submenu would appear causes the submenu to activate. (the logout dialog 
appears.)

  I'm not sure if steps 1-4 are required vs. just installing 18.10 but I
  list it in case this results from left over settings from 18.04
  installing via debbootstrap.

  hbarta@saugage:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10
  hbarta@saugage:~$ 

  hbarta@saugage:~$ apt-cache policy gnome-shell mutter xwayland gnome-menus 
libgnome-menu-3-0:amd64
  gnome-shell:
Installed: 3.30.1-2ubuntu1.18.10.1
Candidate: 3.30.1-2ubuntu1.18.10.1
Version table:
   *** 3.30.1-2ubuntu1.18.10.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.30.1-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  mutter:
Installed: 3.30.2-1~ubuntu18.10.1
Candidate: 3.30.2-1~ubuntu18.10.1
Version table:
   *** 3.30.2-1~ubuntu18.10.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.30.1-1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  xwayland:
Installed: 2:1.20.1-3ubuntu2.1
Candidate: 2:1.20.1-3ubuntu2.1
Version table:
   *** 2:1.20.1-3ubuntu2.1 500
  500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:1.20.1-3ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  gnome-menus:
Installed: 3.13.3-11ubuntu2
Candidate: 3.13.3-11ubuntu2
Version table:
   *** 3.13.3-11ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  libgnome-menu-3-0:
Installed: 3.13.3-11ubuntu2
Candidate: 3.13.3-11ubuntu2
Version table:
   *** 3.13.3-11ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  hbarta@saugage:~$ 

  
  Expected behavior: menu provides visual feedback to clicks. Underlying action 
seems to happen but there is no hint of that or display of submenus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 13 11:41:23 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-12-13 (0 days ago)
  mtime.conffile..etc.logrotate.d.apport: 2018-12-12T13:31:49.347693

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

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

[Desktop-packages] [Bug 150709] Re: [rv200] initial mode is 1280x768 instead of preferred 1280x1024

Launchpad has imported 4 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=18066.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-10-14T16:17:10+00:00 Bryce Harrington wrote:

Created attachment 19655
Xorg.0.log

I'm forwarding this bug report from a Ubuntu user.

The user has a 19" Sony Trinitron E400 Monitor that reports invalid
EDID.  The recommended resolution for this monitor is 1280x1024, but it
defaults to 1280x768.  The user has tested with stock xorg.confs as well
as hand-customized configurations.  He is attempting to use an ATI RV200
QW [Radeon 7500] card; the motherboard has an onboard SiS630/730 card;
both graphics cards are showing invalid EDID, so we're guessing it's the
monitor that's buggy, and must need an xserver quirk.

19" Sony Trinitron E400 Information:
Horizontal Freq. 30-96 kHz
Vertical Freq. 48-120 Hz

ATI card:
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon RV200 QW 
[Radeon 7500] [1002:5157] (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Radeon 7500 [1002:013a]

qsomi@qsomi-desktop:~/Desktop$ sudo get-edid > edid.dat
get-edid: get-edid version 1.4.1

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
 Function supported
 Call successful

 VBE version 200
 VBE string at 0x0 "ATI RV200"

VBE/DDC service about to be called
 Report DDC capabilities

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
 Function supported
 Call successful

 Monitor and video card combination does not support DDC1 transfers
 Monitor and video card combination supports DDC2 transfers
 0 seconds per 128 byte EDID block transfer
 Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
 Read EDID

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
 Function supported
 Call failed

The EDID data should not be trusted as the VBE call failed
qsomi@qsomi-desktop:~/Desktop$ xxd edid.dat
000: ffa2 00ff  ff00 4dd9 9003 f24a 7b00 MJ{.
010: 2f0a 0102 0e25 1b96 eb0c c9a0 5747 9b27 /%..WG.'
020: 1248 4cff ff80 c280 a94f 8159 814f 7159 .HL..O.Y.OqY
030: 6159 4559 3159 863d 00c0 5100 3040 40a0 aYEY1Y.=..Q.0@@.
040: 1300 6008 1100 001e  00fd 0030 781e ..`..0x.
050: 601e 000a 2020 2020 2020  00fc 0053 `... .S
060: 4f4e 5920 4350 442d 4534 3030  00ff ONY CPD-E400
070: 0038 3038 3031 3134 0a20 2020 2020 00d8 .8080114. ..
http://launchpadlibrarian.net/17528516/edid.dat


With the onboard SiS 630/730:

qsomi@qsomi-desktop:~/Desktop$ sudo get-edid > edid.dat
get-edid: get-edid version 1.4.1

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
 Function supported
 Call successful

 VBE version 300
 VBE string at 0x0 "SiS"

VBE/DDC service about to be called
 Report DDC capabilities

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
 Function supported
 Call successful

 Monitor and video card combination does not support DDC1 transfers
 Monitor and video card combination does not support DDC2 transfers
 0 seconds per 128 byte EDID block transfer
 Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
 Read EDID

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
 Function supported
 Call failed

The EDID data should not be trusted as the VBE call failed
qsomi@qsomi-desktop:~/Desktop$ xxd edid.dat
000: ffa2 00ff  ff00 4dd9 9003 f24a 7b00 MJ{.
010: 2f0a 0102 0e25 1b96 eb0c c9a0 5747 9b27 /%..WG.'
020: 1248 4cff ff80 c280 a94f 8159 814f 7159 .HL..O.Y.OqY
030: 6159 4559 3159 863d 00c0 5100 3040 40a0 aYEY1Y.=..Q.0@@.
040: 1300 6008 1100 001e  00fd 0030 781e ..`..0x.
050: 601e 000a 2020 2020 2020  00fc 0053 `... .S
060: 4f4e 5920 4350 442d 4534 3030  00ff ONY CPD-E400
070: 0038 3038 3031 3134 0a20 2020 2020 00d8 .8080114. ..
http://launchpadlibrarian.net/17528747/edid.dat

Example tested with xserver 1.4.99.906-x:
xorg.conf:  http://launchpadlibrarian.net/16991298/xorg.conf
Xorg.0.log: http://launchpadlibrarian.net/16991306/Xorg.0.log
http://launchpadlibrarian.net/16991342/xrandr.txt

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/150709/comments/52


On 2008-10-17T13:40:29+00:00 Ajax-a wrote:

Well, if you decode that EDID as though it were legitimate (ignoring the
header), then it decodes more or less legitimately.  I suspect the BIOS
is just doing something wrong in EDID fetch, since neither radeon nor
sis will use the VBE method to

[Desktop-packages] [Bug 1684123]

2018-12-13 Thread Adamos-9

(In reply to Bruno Pagani from comment #4)
> @gene, Johnny B. Goode: From what I know, the “at” value matters, because
> they have meanings. Though from one generation to another this could be
> different values for the same register.
> 
> Also, @Johnny, in your case it’s a write instead of a read, so I would
> definitively open another issue.

In the end I opened 2 new issues with MMIO FAULT
#108980
#108982
Bug, in different variations, started in kernel 4.10 still exist. There is a 
thousands searchings for this bug in google.

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

Title:
  bus: MMIO read of  FAULT at 3e6684 [ IBUS ]

Status in Nouveau Xorg driver:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  This is the error i get when running xdiagnose:

  nouveau :06:00.0: bus: MMIO read of  FAULT at 3e6684 [
  IBUS ]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-0.3-generic 4.11.0-rc6
  Uname: Linux 4.11.0-0-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Apr 19 15:21:16 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.18, 4.10.0-19-generic, x86_64: installed
   virtualbox, 5.1.18, 4.11.0-0-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GM107 [GeForce GTX 750] [1458:362e]
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-0-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Wed Apr 19 10:21:15 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Laser Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "fbdev" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1808460] [NEW] terminal shuts down automatically on startup

2018-12-13 Thread sn0m

Public bug reported:

terminal shuts down immediately on startup. This started happening after the 
latest update.
Really annoying, had to use konsole to report this bug.
I also remove .bashrc but did not rectify it.
Thanks
Sokol

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 14 14:14:56 2018
InstallationDate: Installed on 2018-07-04 (162 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  terminal shuts down automatically on startup

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  terminal shuts down immediately on startup. This started happening after the 
latest update.
  Really annoying, had to use konsole to report this bug.
  I also remove .bashrc but did not rectify it.
  Thanks
  Sokol

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 14 14:14:56 2018
  InstallationDate: Installed on 2018-07-04 (162 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1808398] Re: top right menu does not display when activated

This may be related to offscreen-effect painting which is now used for
the menu and panel etc.

Can you please:

1. Run 'lspci -k > pci.txt' and send us the resulting file 'pci.txt'.

2. Run 'dpkg -l > allpackages.txt' and send us the resulting file
'allpackages.txt'.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  top right menu does not display when activated

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  1) Install Ubuntu 18.04.1 via debbootstrap
  2) Install ubuntu-desktop package
  3) Install vanilla-desktop package
  4) Upgrade to 18.10 using the Software GUI
  5) Log into Ubuntu on Wayland
  6) Click right end of top bar, menu drops down.
  7) Mouse over menu, no visual feedback of focus (as with Ubuntu on Xorg)
  8) Interact with menu items - there is no visual feedback. For example 
   - sliding back and forth on the screen brightness slider causes the screen 
brightness to change as expected but the slider does not reflect changes. 
Clicking on the right end of the top bar causes the menu to deactivate but 
before it does, the slider position updates.
   - click on the user name and nothing appears to happen. Click below it where 
the submenu would appear causes the submenu to activate. (the logout dialog 
appears.)

  I'm not sure if steps 1-4 are required vs. just installing 18.10 but I
  list it in case this results from left over settings from 18.04
  installing via debbootstrap.

  hbarta@saugage:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10
  hbarta@saugage:~$ 

  hbarta@saugage:~$ apt-cache policy gnome-shell mutter xwayland gnome-menus 
libgnome-menu-3-0:amd64
  gnome-shell:
Installed: 3.30.1-2ubuntu1.18.10.1
Candidate: 3.30.1-2ubuntu1.18.10.1
Version table:
   *** 3.30.1-2ubuntu1.18.10.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.30.1-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  mutter:
Installed: 3.30.2-1~ubuntu18.10.1
Candidate: 3.30.2-1~ubuntu18.10.1
Version table:
   *** 3.30.2-1~ubuntu18.10.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.30.1-1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  xwayland:
Installed: 2:1.20.1-3ubuntu2.1
Candidate: 2:1.20.1-3ubuntu2.1
Version table:
   *** 2:1.20.1-3ubuntu2.1 500
  500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:1.20.1-3ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  gnome-menus:
Installed: 3.13.3-11ubuntu2
Candidate: 3.13.3-11ubuntu2
Version table:
   *** 3.13.3-11ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  libgnome-menu-3-0:
Installed: 3.13.3-11ubuntu2
Candidate: 3.13.3-11ubuntu2
Version table:
   *** 3.13.3-11ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  hbarta@saugage:~$ 

  
  Expected behavior: menu provides visual feedback to clicks. Underlying action 
seems to happen but there is no hint of that or display of submenus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 13 11:41:23 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-12-13 (0 days ago)
  mtime.conffile..etc.logrotate.d.apport: 2018-12-12T13:31:49.347693

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

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

[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program

** Changed in: xorg-server
   Status: Confirmed => Unknown

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

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

Status in GNOME Settings Daemon:
  Fix Released
Status in GNOME Shell:
  Won't Fix
Status in Unity:
  Confirmed
Status in X.Org X server:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-settings-daemon package in Debian:
  New
Status in gnome-settings-daemon package in Fedora:
  In Progress
Status in gnome-settings-daemon package in openSUSE:
  Confirmed

Bug description:
  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.

  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1245473]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/258.

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

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

Status in GNOME Settings Daemon:
  Fix Released
Status in GNOME Shell:
  Won't Fix
Status in Unity:
  Confirmed
Status in X.Org X server:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-settings-daemon package in Debian:
  New
Status in gnome-settings-daemon package in Fedora:
  In Progress
Status in gnome-settings-daemon package in openSUSE:
  Confirmed

Bug description:
  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.

  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1808193] Missing required logs.

2018-12-13 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1808193

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Battery percentage changes suddenly depending on whether AC is plugged
  in

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  New

Bug description:
  The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% 
(Fully charged when plugged in) but when plugged out the battery shows 94%. 
Batteries are fine, no issues whatsoever with batteries.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1808193/+subscriptions

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

[Desktop-packages] [Bug 1808203] Re: ddfs

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  ddfs

Status in Ubuntu:
  Incomplete

Bug description:
  sdfsf

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Dec 12 21:07:13 2018
  DistUpgraded: 2018-12-12 20:39:45,935 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Wrestler [Radeon HD 7340] [104d:90ad]
  InstallationDate: Installed on 2016-04-24 (962 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Sony Corporation SVE1112M1EW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=40da7131-b99a-4e5b-9c5e-81ba4975e74c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-12-12 (0 days ago)
  dmi.bios.date: 08/22/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0120D8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0120D8:bd08/22/2012:svnSonyCorporation:pnSVE1112M1EW:pvrC60B8BEP:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVE1112M1EW
  dmi.product.version: C60B8BEP
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~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: Wed Dec 12 18:07:04 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1808419] Re: Screen Brightness problem

Firstly, please keep each bug report about a single issue. This bug
should be about the screen brightness only.

Next, please look in:

  Settings > Power

and turn off automatic dimming in case that is contributing to the
problem. If the problem still isn't fixed, can you tell us if the
brightness slider in the top-right menu works for you?

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

** Tags added: backlight nvidia

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

Title:
  Screen Brightness problem

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  When i switch on my laptop with Ubuntu. It starts with lowest brightness. 
Even it set to normal. When i set it again it returning to normal. But when 
after screen dimming it does not return again. So it doesnt recognize to my 
mouse or keyboard.
  Sorry for my English. I hope I could explain my problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 14 02:43:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-34-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04ca]
   NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GF108M [GeForce GT 525M] [1028:04ca]
  InstallationDate: Installed on 2018-09-30 (74 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=4a66061d-c599-4959-97d9-eee379ba8b99 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0HVRTT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0HVRTT:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1808275] Re: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] Changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped

Sound hardware sometimes remembers its state even if you switch between
operating systems. So please also try turning the machine off for a few
seconds and then on again.

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

Title:
  [, SigmaTel STAC9221D A2, Green Headphone Out, Front] Changed the
  sound output from analog output to digital output(S/PDIF) and it
  suddenly stopped

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  The green headphone out was working and I changed the sound output
  from analog output to digital output(S/PDIF) and it suddenly stopped
  and changing it back to Analog Output didn't restore the sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Wed Dec 12 23:10:39 2018
  InstallationDate: Installed on 2018-12-06 (7 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BX97510J.86A.1487.2007.0902.1724
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: D975XBX
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD27094-305
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBX97510J.86A.1487.2007.0902.1724:bd09/02/2007:svn:pn:pvr:rvnIntelCorporation:rnD975XBX:rvrAAD27094-305:cvn:ct2:cvr:

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

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

[Desktop-packages] [Bug 1808193] Re: Battery indicator shows false reading

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

** Summary changed:

- Battery indicator shows false reading
+ Battery percentage changes suddenly depending on whether AC is plugged in

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

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

Title:
  Battery percentage changes suddenly depending on whether AC is plugged
  in

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% 
(Fully charged when plugged in) but when plugged out the battery shows 94%. 
Batteries are fine, no issues whatsoever with batteries.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1808193/+subscriptions

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

[Desktop-packages] [Bug 1808323] Re: gfg

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  gfg

Status in Ubuntu:
  Incomplete

Bug description:
  gfg

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Dec 13 14:09:43 2018
  DistUpgraded: 2018-12-12 20:39:45,935 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Wrestler [Radeon HD 7340] [104d:90ad]
  InstallationDate: Installed on 2016-04-24 (963 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Sony Corporation SVE1112M1EW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=40da7131-b99a-4e5b-9c5e-81ba4975e74c ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-12-12 (0 days ago)
  dmi.bios.date: 08/22/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0120D8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0120D8:bd08/22/2012:svnSonyCorporation:pnSVE1112M1EW:pvrC60B8BEP:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVE1112M1EW
  dmi.product.version: C60B8BEP
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~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: Wed Dec 12 18:07:04 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal

Regarding:

% time seconds usecs/call calls errors syscall
-- --- --- - - 
 83.37 2.716542 2 1494072 clock_gettime

I believe that's 83.37% of the process' system time. It's not the
overall CPU usage of the function. If you use the 'time' command or
compare fields 14 and 15 in /proc/PID/stat then you will likely find the
process' system time is not a significant percentage of its overall time
used. Because that doesn't include the 'user' time which is a much
bigger fraction. So the above is 83.37% of a small fraction and should
be ignored.

Basically it means 'strace -c' is meaningless to regular users and
should be ignored.

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

Title:
  High CPU usage by gnome-shell when only running gnome-terminal

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Even when doing nothing but displaying a terminal screen with top
  running gnome-shell uses 10% of a CPU. That seems excessive. I
  disabled all extensions to try and make the test fair. Enabling the
  system monitor extension increases the load to 13-14%. It seems that
  the gnome-shell screen painting is highly CPU consuming even if screen
  updates are infrequent (1 a second for all these cases).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 29 11:38:05 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-27 (578 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago)

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

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

[Desktop-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

It appears the gnome-shell!278 fix is only in future version 3.31.3 at
the moment.

I've had the same issue with other laptops and would be surprised if
this was the only bug report.

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1808125] Re: Ubuntu 18.10 boot hangs with INTEL GRAPHICS at msg "Starting bpfilter"

You're welcome.

In this case the correct status is 'Invalid' since it's not a bug in the
default Ubuntu installation. That said, I may investigate changing the
default file we install so that it's more obvious and people are less
likely to make the same mistake if they want to change anything.

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

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

Title:
  Ubuntu 18.10 boot hangs with INTEL GRAPHICS at msg "Starting bpfilter"

Status in gdm3 package in Ubuntu:
  Invalid

Bug description:
  This is not a question, but I found no thread to report this bug and
  workaround on NON-NVIDIA-BASED systems:

  Ubuntu 18.10, kernel 4.18.0-12-generic, GNOME Shell 3.30.1 on X11,
  after a Dec 9 update:

  Boot hangs at message, "Starting bpfilter." Gnome Display Manager
  (login) fails to start. No keyboard response, tapping the power button
  just once immediately initiates power-down. Other users have reported
  successfully fixing this by removing nVidia drivers or disabling
  Wayland in GDM3 (uncommenting WaylandEnable=false in
  /etc/gdm3/custom.conf.)

  However, my HP laptop runs Intel graphics, and has no nVidia drivers
  installed.

  WORKAROUND
  I selected Enable Networking in Recovery Mode, then Drop to Shell Prompt 
(root,) and ran 

   apt update && apt install slim

  to install SLiM display manager. the installation prompted me to
  choose SLiM or GDM as the default, I chose SLiM, and was able to login
  finally (after rebooting 50+ times.)

  If you already have an alternate display manager installed, you can
  switch with "sudo dpkg-reconfigure gdm" and select the alt dm.

  This will probably be just a provisional workaround for the "bpfilter hang" 
on non-nVidia systems if all the other suggested solutions didn't work for you. 
BTW, I also tried LightDM a former Ubuntu DM, but got the identical bootup hang.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-05-07 (219 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: wl
  Package: gdm3 3.30.1-1ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-12-10T07:21:25.671742

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

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

Re: [Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

2018-12-13 Thread Tim Richardson

If you have this bug, what is the result of opening a terminal, and running
systemctl suspend
and waiting for a minute?

On Fri, 14 Dec 2018 at 08:24, Jeremy Walker <1600...@bugs.launchpad.net>
wrote:

> The importance on this ticket is incorrect: it should not be marked
> "low". According to https://dev.launchpad.net/BugTriage#importance)
> "Low" is defined as "legitimate but that is not scheduled for Canonical
> staff to fix in the next 6 months."
>
> This is a MAJOR issue.  As W-barath-hotmail noted it can cause some
> extremely serious side effects for anyone who relies on power
> management.  As such, this ticket should have an importance of "High"
> ("we believe we will work on in the next six months").  To ignore it for
> six or more months would be to deliberately cause serious user damage.
>
> Also, this bug is difficult for users to track down. It's not like
> problematic tabs flash red or something, so each user has to figure out
> on their own that not only is Chrome the source of the problem, but a
> specific tab within Chrome. As a result, the number of users affected by
> this bug is undoubtedly much higher than what's reflected on this page,
> as many affected users just aren't able to track the problem to this
> page.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1600622
>
> Title:
>   Screen doesn't lock or go to sleep when certain Chrome tabs are open
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions
>


-- 
Tim Richardson

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

Title:
  Screen doesn't lock or go to sleep when certain Chrome tabs are open

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy gnome-session-bin
  gnome-session-bin:
    Installed: 3.18.1.2-1ubuntu1.16.04.1
    Candidate: 3.18.1.2-1ubuntu1.16.04.1
    Version table:
   *** 3.18.1.2-1ubuntu1.16.04.1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.1.2-1ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I'm using gnome-session-flashback

  What happens:
  The screen doesn't lock when having certain pages in Chrome tabs

  Expected:
  The screen should lock after the configured timeout in settings.

  I've been having this issue sice before 14.04, which I recently
  upgraded (fresh install) to 16.04.

  After fresh install, the screen would turn down and lock the computer
  after 10 minutes (or whatever time I setup). At one point it stopped
  working. The screen never shuts down unless I manually lock the
  session with CTRL-ALT-L.

  I've followed the steps in
  https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure

  The culprit seems to be that Chrome issues some suspend inhibitions
  through dbus when doing certain operations. Many people find this
  problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
  pretty sure that Chrome is doing something else of what i've found
  out.

  1) Gnome screen saver works correctly. I can trigger it manually with:
  $ gnome-screensaver-command -a

  2) Gnome screen saver never receives the "session idle" status
  callback.

  3) When Chrome is not running, I can manually inhibit the idle status:
  $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" 
--inhibit-only --inhibit idle:suspend
  Inhibiting until Ctrl+C is pressed...

  4) I can query the inhibitors:
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return 
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 
reply_serial=2
     array [
    object path "/org/gnome/SessionManager/Inhibitor1686"
     ]
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetAppId
  ('test',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetReason
  ('manual idle inhibit',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetFlags
  (uint32 12,)

  12=4(suspend) + 8(idle)

  5) When testing, I can inhibit for 70 seconds, idle timeout being 60
  (1 minute). After these 70 seconds pass, the screen locks.

  6) Regarding Chrome, this is the information I get when querying the 
inhibitor:
  GetAppId: ('/usr/bin/google-chrome-stable',)

[Desktop-packages] [Bug 189198] Re: [RV200 QW 7500] video comes up garbled - monitor edid not 1.2 compliant, and X picks wrong preferred mode

** Changed in: xserver-xorg-driver-ati
   Status: Confirmed => Unknown

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

Title:
  [RV200 QW 7500] video comes up garbled - monitor edid not 1.2
  compliant, and X picks wrong preferred mode

Status in xserver-xorg-driver-ati:
  Unknown
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid

Bug description:
  When starting X, the server fails to show up a proper image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/189198/+subscriptions

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

[Desktop-packages] [Bug 227907] Re: using compiz' enhanced zoom plugin corrupts mouse pointers

** Changed in: xorg-server
   Status: Confirmed => Unknown

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

Title:
  using compiz' enhanced zoom plugin corrupts mouse pointers

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: compiz-fusion-plugins-main

  If i use the enhanced zoom plugin (by 'use' i mean actually zoom in
  and out, not just turn it on), thereafter my 'progress' and i believe
  'wait' mouse pointers are invisible. The only way I can figure to get
  them back is to restart X.

  If I happen to zoom in when the pointer is in the 'wait' state, it
  gets stuck in the wait state until I restart X.

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

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

[Desktop-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2018-12-13 Thread Alexandre Forte

This issue also affects Asus Vivobook 15 X510UR.

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 189198]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/360.

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

Title:
  [RV200 QW 7500] video comes up garbled - monitor edid not 1.2
  compliant, and X picks wrong preferred mode

Status in xserver-xorg-driver-ati:
  Unknown
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid

Bug description:
  When starting X, the server fails to show up a proper image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/189198/+subscriptions

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

[Desktop-packages] [Bug 227907]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/376.

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

Title:
  using compiz' enhanced zoom plugin corrupts mouse pointers

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: compiz-fusion-plugins-main

  If i use the enhanced zoom plugin (by 'use' i mean actually zoom in
  and out, not just turn it on), thereafter my 'progress' and i believe
  'wait' mouse pointers are invisible. The only way I can figure to get
  them back is to restart X.

  If I happen to zoom in when the pointer is in the 'wait' state, it
  gets stuck in the wait state until I restart X.

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

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

[Desktop-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

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

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

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

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

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

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

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

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

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1793427] Re: network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub-resolv.conf

2018-12-13 Thread Dariusz Olszewski

This might be a duplicate of: https://bugs.launchpad.net/ubuntu/+source
/network-manager/+bug/1778946

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

Title:
  network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub-
  resolv.conf

Status in network-manager-fortisslvpn package in Ubuntu:
  Confirmed
Status in network-manager-pptp package in Ubuntu:
  New

Bug description:
  (I'm not able to use ubuntu-bug as it fails with a 503 error trying to
  connect to the crash server)

  I'm using Ubuntu 18.04.1 on 64bit Intel with:

  network-manager1.10.6-2ubuntu1
  network-manager-fortisslvpn1.2.8-1build1
  network-manager-fortisslvpn-gnome  1.2.8-1build1
  network-manager-gnome  1.8.10-2ubuntu1

  systemd237-3ubuntu10.3

  When I connect then disconnect from my VPN using the network-manager-
  fortisslvpn VPN interface, it will break the permissions on
  /run/systemd/resolv/stub-resolv.conf such that I can't use DNS anymore
  until I fix the permissions.

  On my system I see:

  $ ls -al /etc/resolv.conf
  lrwxrwxrwx 1 root root 39 Oct 22  2017 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  When there's no VPN connection, I see:

  $ ls -al /run/systemd/resolve/
  total 8
  drwxr-xr-x  3 systemd-resolve systemd-resolve 100 Sep 19 23:05 ./
  drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../
  drwx--  2 systemd-resolve systemd-resolve  60 Sep 19 23:05 netif/
  -rw-r--r--  1 systemd-resolve systemd-resolve 714 Sep 19 23:05 resolv.conf
  -rw-r--r--  1 systemd-resolve systemd-resolve 783 Sep 19 19:31 
stub-resolv.conf

  Now I start the fortisslvpn VPN:

  $ ls -al /run/systemd/resolve/
  total 16
  drwxr-xr-x  3 systemd-resolve systemd-resolve 140 Sep 19 23:06 ./
  drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../
  drwx--  2 systemd-resolve systemd-resolve  80 Sep 19 23:06 netif/
  -rw-r--r--  1 systemd-resolve systemd-resolve 714 Sep 19 23:06 resolv.conf
  -rw-r--r--  1 systemd-resolve systemd-resolve 783 Sep 19 23:06 
stub-resolv.conf
  -rw---  1 rootroot783 Sep 19 19:31 
stub-resolv.conf.pppd-backup.ppp0
  -rw-r--r--  1 rootroot805 Sep 19 23:06 
stub-resolv.conf.tmp

  Note how the stub-resolv.conf.pppd-backup-ppp0 has 0600 file
  permissions.

  Now I stop the fortisslvpn VPN:

  $ ls -al /run/systemd/resolve/
  total 12
  drwxr-xr-x  3 systemd-resolve systemd-resolve 120 Sep 19 23:06 ./
  drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../
  drwx--  2 systemd-resolve systemd-resolve  60 Sep 19 23:06 netif/
  -rw-r--r--  1 systemd-resolve systemd-resolve 714 Sep 19 23:06 resolv.conf
  -rw---  1 rootroot783 Sep 19 19:31 
stub-resolv.conf
  -rw-r--r--  1 rootroot805 Sep 19 23:06 
stub-resolv.conf.tmp

  Now the stub-resolv.conf file hs 0600 permissions and my DNS is
  broken.

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

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

[Desktop-packages] [Bug 1793427] Re: network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub-resolv.conf

2018-12-13 Thread Dariusz Olszewski

** Project changed: network-manager-pptp => network-manager-pptp
(Ubuntu)

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

Title:
  network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub-
  resolv.conf

Status in network-manager-fortisslvpn package in Ubuntu:
  Confirmed
Status in network-manager-pptp package in Ubuntu:
  New

Bug description:
  (I'm not able to use ubuntu-bug as it fails with a 503 error trying to
  connect to the crash server)

  I'm using Ubuntu 18.04.1 on 64bit Intel with:

  network-manager1.10.6-2ubuntu1
  network-manager-fortisslvpn1.2.8-1build1
  network-manager-fortisslvpn-gnome  1.2.8-1build1
  network-manager-gnome  1.8.10-2ubuntu1

  systemd237-3ubuntu10.3

  When I connect then disconnect from my VPN using the network-manager-
  fortisslvpn VPN interface, it will break the permissions on
  /run/systemd/resolv/stub-resolv.conf such that I can't use DNS anymore
  until I fix the permissions.

  On my system I see:

  $ ls -al /etc/resolv.conf
  lrwxrwxrwx 1 root root 39 Oct 22  2017 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  When there's no VPN connection, I see:

  $ ls -al /run/systemd/resolve/
  total 8
  drwxr-xr-x  3 systemd-resolve systemd-resolve 100 Sep 19 23:05 ./
  drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../
  drwx--  2 systemd-resolve systemd-resolve  60 Sep 19 23:05 netif/
  -rw-r--r--  1 systemd-resolve systemd-resolve 714 Sep 19 23:05 resolv.conf
  -rw-r--r--  1 systemd-resolve systemd-resolve 783 Sep 19 19:31 
stub-resolv.conf

  Now I start the fortisslvpn VPN:

  $ ls -al /run/systemd/resolve/
  total 16
  drwxr-xr-x  3 systemd-resolve systemd-resolve 140 Sep 19 23:06 ./
  drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../
  drwx--  2 systemd-resolve systemd-resolve  80 Sep 19 23:06 netif/
  -rw-r--r--  1 systemd-resolve systemd-resolve 714 Sep 19 23:06 resolv.conf
  -rw-r--r--  1 systemd-resolve systemd-resolve 783 Sep 19 23:06 
stub-resolv.conf
  -rw---  1 rootroot783 Sep 19 19:31 
stub-resolv.conf.pppd-backup.ppp0
  -rw-r--r--  1 rootroot805 Sep 19 23:06 
stub-resolv.conf.tmp

  Note how the stub-resolv.conf.pppd-backup-ppp0 has 0600 file
  permissions.

  Now I stop the fortisslvpn VPN:

  $ ls -al /run/systemd/resolve/
  total 12
  drwxr-xr-x  3 systemd-resolve systemd-resolve 120 Sep 19 23:06 ./
  drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../
  drwx--  2 systemd-resolve systemd-resolve  60 Sep 19 23:06 netif/
  -rw-r--r--  1 systemd-resolve systemd-resolve 714 Sep 19 23:06 resolv.conf
  -rw---  1 rootroot783 Sep 19 19:31 
stub-resolv.conf
  -rw-r--r--  1 rootroot805 Sep 19 23:06 
stub-resolv.conf.tmp

  Now the stub-resolv.conf file hs 0600 permissions and my DNS is
  broken.

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

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

[Desktop-packages] [Bug 1793427] Re: network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub-resolv.conf

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

** Changed in: network-manager-pptp (Ubuntu)
   Status: New => Confirmed

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

Title:
  network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub-
  resolv.conf

Status in network-manager-fortisslvpn package in Ubuntu:
  Confirmed
Status in network-manager-pptp package in Ubuntu:
  New

Bug description:
  (I'm not able to use ubuntu-bug as it fails with a 503 error trying to
  connect to the crash server)

  I'm using Ubuntu 18.04.1 on 64bit Intel with:

  network-manager1.10.6-2ubuntu1
  network-manager-fortisslvpn1.2.8-1build1
  network-manager-fortisslvpn-gnome  1.2.8-1build1
  network-manager-gnome  1.8.10-2ubuntu1

  systemd237-3ubuntu10.3

  When I connect then disconnect from my VPN using the network-manager-
  fortisslvpn VPN interface, it will break the permissions on
  /run/systemd/resolv/stub-resolv.conf such that I can't use DNS anymore
  until I fix the permissions.

  On my system I see:

  $ ls -al /etc/resolv.conf
  lrwxrwxrwx 1 root root 39 Oct 22  2017 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  When there's no VPN connection, I see:

  $ ls -al /run/systemd/resolve/
  total 8
  drwxr-xr-x  3 systemd-resolve systemd-resolve 100 Sep 19 23:05 ./
  drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../
  drwx--  2 systemd-resolve systemd-resolve  60 Sep 19 23:05 netif/
  -rw-r--r--  1 systemd-resolve systemd-resolve 714 Sep 19 23:05 resolv.conf
  -rw-r--r--  1 systemd-resolve systemd-resolve 783 Sep 19 19:31 
stub-resolv.conf

  Now I start the fortisslvpn VPN:

  $ ls -al /run/systemd/resolve/
  total 16
  drwxr-xr-x  3 systemd-resolve systemd-resolve 140 Sep 19 23:06 ./
  drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../
  drwx--  2 systemd-resolve systemd-resolve  80 Sep 19 23:06 netif/
  -rw-r--r--  1 systemd-resolve systemd-resolve 714 Sep 19 23:06 resolv.conf
  -rw-r--r--  1 systemd-resolve systemd-resolve 783 Sep 19 23:06 
stub-resolv.conf
  -rw---  1 rootroot783 Sep 19 19:31 
stub-resolv.conf.pppd-backup.ppp0
  -rw-r--r--  1 rootroot805 Sep 19 23:06 
stub-resolv.conf.tmp

  Note how the stub-resolv.conf.pppd-backup-ppp0 has 0600 file
  permissions.

  Now I stop the fortisslvpn VPN:

  $ ls -al /run/systemd/resolve/
  total 12
  drwxr-xr-x  3 systemd-resolve systemd-resolve 120 Sep 19 23:06 ./
  drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../
  drwx--  2 systemd-resolve systemd-resolve  60 Sep 19 23:06 netif/
  -rw-r--r--  1 systemd-resolve systemd-resolve 714 Sep 19 23:06 resolv.conf
  -rw---  1 rootroot783 Sep 19 19:31 
stub-resolv.conf
  -rw-r--r--  1 rootroot805 Sep 19 23:06 
stub-resolv.conf.tmp

  Now the stub-resolv.conf file hs 0600 permissions and my DNS is
  broken.

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

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

[Desktop-packages] [Bug 1796607] Re: gnome-shell crashed with SIGSEGV in meta_compositor_switch_workspace(compositor=NULL) → meta_workspace_activate_with_focus → meta_workspace_activate → meta_x11_dis

Launchpad has imported 17 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1647015.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-11-06T14:10:28+00:00 brian wrote:

Description of problem:
alt-f2, r to restart the shell

Version-Release number of selected component:
gnome-shell-3.30.1-2.fc29

Additional info:
reporter:   libreport-2.9.6
backtrace_rating: 4
cmdline:/usr/bin/gnome-shell
crash_function: meta_compositor_switch_workspace
executable: /usr/bin/gnome-shell
journald_cursor: 
s=9b746aaa333c40b4a7a6884d140d0c1f;i=822eb9;b=c60ec25b4df94ff7af2342937ea36c84;m=6e982ad24;t=579ff3f8bdbb8;x=514352256855e16e
kernel: 4.18.16-300.fc29.x86_64
rootdir:/
runlevel:   N 5
type:   CCpp
uid:1001

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 meta_compositor_switch_workspace at compositor/compositor.c:832
 #1 meta_workspace_activate_with_focus at core/workspace.c:636
 #2 meta_workspace_activate at core/workspace.c:665
 #3 meta_x11_display_new at x11/meta-x11-display.c:1291
 #4 meta_display_open at core/display.c:746
 #5 meta_run at core/main.c:686

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1796607/comments/2


On 2018-11-06T14:10:34+00:00 brian wrote:

Created attachment 1502478
File: backtrace

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1796607/comments/3


On 2018-11-06T14:10:35+00:00 brian wrote:

Created attachment 1502479
File: cgroup

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1796607/comments/4


On 2018-11-06T14:10:37+00:00 brian wrote:

Created attachment 1502480
File: core_backtrace

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1796607/comments/5


On 2018-11-06T14:10:38+00:00 brian wrote:

Created attachment 1502481
File: cpuinfo

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1796607/comments/6


On 2018-11-06T14:10:39+00:00 brian wrote:

Created attachment 1502482
File: dso_list

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1796607/comments/7


On 2018-11-06T14:10:40+00:00 brian wrote:

Created attachment 1502483
File: environ

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1796607/comments/8


On 2018-11-06T14:10:41+00:00 brian wrote:

Created attachment 1502484
File: exploitable

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1796607/comments/9


On 2018-11-06T14:10:42+00:00 brian wrote:

Created attachment 1502485
File: limits

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1796607/comments/10


On 2018-11-06T14:10:44+00:00 brian wrote:

Created attachment 1502486
File: maps

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1796607/comments/11


On 2018-11-06T14:10:45+00:00 brian wrote:

Created attachment 1502487
File: mountinfo

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1796607/comments/12


On 2018-11-06T14:10:46+00:00 brian wrote:

Created attachment 1502488
File: open_fds

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1796607/comments/13


On 2018-11-06T14:10:47+00:00 brian wrote:

Created attachment 1502489
File: proc_pid_status

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1796607/comments/14


On 2018-11-06T14:10:49+00:00 brian wrote:

Created attachment 1502490
File: var_log_messages

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1796607/comments/15


On 2018-11-09T13:10:05+00:00 brian wrote:

Similar problem has been detected:

Restarted the shell with ALT-F2->r.

This is NOT supposed to KILL the entire session.

reporter:

[Desktop-packages] [Bug 1793427] [NEW] network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub-resolv.conf

You have been subscribed to a public bug:

(I'm not able to use ubuntu-bug as it fails with a 503 error trying to
connect to the crash server)

I'm using Ubuntu 18.04.1 on 64bit Intel with:

network-manager1.10.6-2ubuntu1
network-manager-fortisslvpn1.2.8-1build1
network-manager-fortisslvpn-gnome  1.2.8-1build1
network-manager-gnome  1.8.10-2ubuntu1

systemd237-3ubuntu10.3

When I connect then disconnect from my VPN using the network-manager-
fortisslvpn VPN interface, it will break the permissions on
/run/systemd/resolv/stub-resolv.conf such that I can't use DNS anymore
until I fix the permissions.

On my system I see:

$ ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 39 Oct 22  2017 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

When there's no VPN connection, I see:

$ ls -al /run/systemd/resolve/
total 8
drwxr-xr-x  3 systemd-resolve systemd-resolve 100 Sep 19 23:05 ./
drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../
drwx--  2 systemd-resolve systemd-resolve  60 Sep 19 23:05 netif/
-rw-r--r--  1 systemd-resolve systemd-resolve 714 Sep 19 23:05 resolv.conf
-rw-r--r--  1 systemd-resolve systemd-resolve 783 Sep 19 19:31 stub-resolv.conf

Now I start the fortisslvpn VPN:

$ ls -al /run/systemd/resolve/
total 16
drwxr-xr-x  3 systemd-resolve systemd-resolve 140 Sep 19 23:06 ./
drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../
drwx--  2 systemd-resolve systemd-resolve  80 Sep 19 23:06 netif/
-rw-r--r--  1 systemd-resolve systemd-resolve 714 Sep 19 23:06 resolv.conf
-rw-r--r--  1 systemd-resolve systemd-resolve 783 Sep 19 23:06 stub-resolv.conf
-rw---  1 rootroot783 Sep 19 19:31 
stub-resolv.conf.pppd-backup.ppp0
-rw-r--r--  1 rootroot805 Sep 19 23:06 
stub-resolv.conf.tmp

Note how the stub-resolv.conf.pppd-backup-ppp0 has 0600 file
permissions.

Now I stop the fortisslvpn VPN:

$ ls -al /run/systemd/resolve/
total 12
drwxr-xr-x  3 systemd-resolve systemd-resolve 120 Sep 19 23:06 ./
drwxr-xr-x 21 rootroot480 Sep 15 14:19 ../
drwx--  2 systemd-resolve systemd-resolve  60 Sep 19 23:06 netif/
-rw-r--r--  1 systemd-resolve systemd-resolve 714 Sep 19 23:06 resolv.conf
-rw---  1 rootroot783 Sep 19 19:31 stub-resolv.conf
-rw-r--r--  1 rootroot805 Sep 19 23:06 
stub-resolv.conf.tmp

Now the stub-resolv.conf file hs 0600 permissions and my DNS is broken.

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

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

-- 
network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub-resolv.conf
https://bugs.launchpad.net/bugs/1793427
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to network-manager-pptp in Ubuntu.

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

[Desktop-packages] [Bug 1806275] Re: Symbols arranged one above the other in portrait format

** Attachment added: "Bildschirmfoto vom 2018-12-13 23-19-19.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-system-monitor/+bug/1806275/+attachment/5222139/+files/Bildschirmfoto%20vom%202018-12-13%2023-19-19.png

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

Title:
  Symbols arranged one above the other in portrait format

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-system-monitor package in Ubuntu:
  New
Status in gnome-shell-extension-weather package in Ubuntu:
  New

Bug description:
  As described above. When I rotate my laptop and use it in portrait
  mode, the view toggles. Unfortunately, the symbols in the top bar of
  the shell are then arranged one above the other, so that they are no
  longer usable. I attach a photo to clarify what I mean.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 21:19:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-30 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1806275] Re: Symbols arranged one above the other in portrait format

I've reported the issue as well upstream: https://gitlab.gnome.org/GNOME
/gnome-shell/issues/852

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

Title:
  Symbols arranged one above the other in portrait format

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-system-monitor package in Ubuntu:
  New
Status in gnome-shell-extension-weather package in Ubuntu:
  New

Bug description:
  As described above. When I rotate my laptop and use it in portrait
  mode, the view toggles. Unfortunately, the symbols in the top bar of
  the shell are then arranged one above the other, so that they are no
  longer usable. I attach a photo to clarify what I mean.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 21:19:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-30 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1806275] Re: Symbols arranged one above the other in portrait format

Uninstalled and reinstalled the system monitor extension. The extension
is as well affected.

The shell should manage its extensions.

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell-extension-system-monitor (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Symbols arranged one above the other in portrait format

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-system-monitor package in Ubuntu:
  New
Status in gnome-shell-extension-weather package in Ubuntu:
  New

Bug description:
  As described above. When I rotate my laptop and use it in portrait
  mode, the view toggles. Unfortunately, the symbols in the top bar of
  the shell are then arranged one above the other, so that they are no
  longer usable. I attach a photo to clarify what I mean.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 21:19:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-30 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1808428] [NEW] Ping of a link local address with -I as non-root produces "Invalid argument"

2018-12-13 Thread Ivan Nejgebauer

Public bug reported:

iputils-ping 3:20161105-1ubuntu2 amd64 18.04.1 LTS

In the following, "c7" is a host with the link-local address 
fe80::5054:ff:fe45:1e87.
The mapping is in "/etc/hosts". It is reachable via the "enp2s0" interface on 
the local
machine. I have masked the local machine's MAC address.

1. As a regular (non-root) user, ping returns "Invalid argument":

$ ping -I enp2s0 c7
PING c7(c7 (fe80::5054:ff:fe45:1e87)) from fe80:::xxff:fexx:%enp2s0 
enp2s0: 56 data bytes
ping: sendmsg: Invalid argument
ping: sendmsg: Invalid argument
ping: sendmsg: Invalid argument

2. As root, ping works:

# ping -I enp2s0 c7
PING c7(c7 (fe80::5054:ff:fe45:1e87)) from fe80:::xxff:fexx:%enp2s0 
enp2s0: 56 data bytes
64 bytes from c7 (fe80::5054:ff:fe45:1e87%enp2s0): icmp_seq=1 ttl=64 time=0.285 
ms
64 bytes from c7 (fe80::5054:ff:fe45:1e87%enp2s0): icmp_seq=2 ttl=64 time=0.306 
ms
64 bytes from c7 (fe80::5054:ff:fe45:1e87%enp2s0): icmp_seq=3 ttl=64 time=0.307 
ms

3. Specifying the interface-qualified IPv6 address directly works:

$ ping fe80::5054:ff:fe45:1e87%enp2s0
PING fe80::5054:ff:fe45:1e87%enp2s0(fe80::5054:ff:fe45:1e87%enp2s0) 56 data 
bytes
64 bytes from fe80::5054:ff:fe45:1e87%enp2s0: icmp_seq=1 ttl=64 time=0.476 ms
64 bytes from fe80::5054:ff:fe45:1e87%enp2s0: icmp_seq=2 ttl=64 time=0.408 ms
64 bytes from fe80::5054:ff:fe45:1e87%enp2s0: icmp_seq=3 ttl=64 time=0.395 ms

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

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

Title:
  Ping of a link local address with -I as non-root produces "Invalid
  argument"

Status in iputils package in Ubuntu:
  New

Bug description:
  iputils-ping 3:20161105-1ubuntu2 amd64 18.04.1 LTS

  In the following, "c7" is a host with the link-local address 
fe80::5054:ff:fe45:1e87.
  The mapping is in "/etc/hosts". It is reachable via the "enp2s0" interface on 
the local
  machine. I have masked the local machine's MAC address.

  1. As a regular (non-root) user, ping returns "Invalid argument":

  $ ping -I enp2s0 c7
  PING c7(c7 (fe80::5054:ff:fe45:1e87)) from fe80:::xxff:fexx:%enp2s0 
enp2s0: 56 data bytes
  ping: sendmsg: Invalid argument
  ping: sendmsg: Invalid argument
  ping: sendmsg: Invalid argument

  2. As root, ping works:

  # ping -I enp2s0 c7
  PING c7(c7 (fe80::5054:ff:fe45:1e87)) from fe80:::xxff:fexx:%enp2s0 
enp2s0: 56 data bytes
  64 bytes from c7 (fe80::5054:ff:fe45:1e87%enp2s0): icmp_seq=1 ttl=64 
time=0.285 ms
  64 bytes from c7 (fe80::5054:ff:fe45:1e87%enp2s0): icmp_seq=2 ttl=64 
time=0.306 ms
  64 bytes from c7 (fe80::5054:ff:fe45:1e87%enp2s0): icmp_seq=3 ttl=64 
time=0.307 ms

  3. Specifying the interface-qualified IPv6 address directly works:

  $ ping fe80::5054:ff:fe45:1e87%enp2s0
  PING fe80::5054:ff:fe45:1e87%enp2s0(fe80::5054:ff:fe45:1e87%enp2s0) 56 data 
bytes
  64 bytes from fe80::5054:ff:fe45:1e87%enp2s0: icmp_seq=1 ttl=64 time=0.476 ms
  64 bytes from fe80::5054:ff:fe45:1e87%enp2s0: icmp_seq=2 ttl=64 time=0.408 ms
  64 bytes from fe80::5054:ff:fe45:1e87%enp2s0: icmp_seq=3 ttl=64 time=0.395 ms

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

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

[Desktop-packages] [Bug 1796607] Re: gnome-shell crashed with SIGSEGV in meta_compositor_switch_workspace(compositor=NULL) → meta_workspace_activate_with_focus → meta_workspace_activate → meta_x11_dis

Also reproducible on Fedora 29

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

** Also affects: gnome-shell (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1647015
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_compositor_switch_workspace(compositor=NULL) →
  meta_workspace_activate_with_focus → meta_workspace_activate →
  meta_x11_display_new → meta_display_open

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell package in Fedora:
  Unknown

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

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

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

[Desktop-packages] [Bug 1808123] Re: Fullscreen view lands on another monitor

I've filed an upstream bug:

https://bugs.documentfoundation.org/show_bug.cgi?id=122085

** Bug watch added: Document Foundation Bugzilla #122085
   https://bugs.documentfoundation.org/show_bug.cgi?id=122085

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

Title:
  Fullscreen view lands on another monitor

Status in libreoffice package in Ubuntu:
  New

Bug description:
  As described above. I work in the classroom with my notebook, to which I have 
connected a beamer. Sometimes I write things down in the Writer and show it via 
the beamer. I would like to use the fullscreen mode here. 
  Unfortunately, the fullscreen mode is always displayed on the internal 
monitor, even if the window with the Writer maximized was previously displayed 
on the beamer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 12 10:44:00 2018
  InstallationDate: Installed on 2018-11-30 (11 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1808420] Re: gnome-system-monitor from Snap does not hide /dev/loop* mounts

2018-12-13 Thread Nope

** Attachment added: "system_resources.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1808420/+attachment/5222128/+files/system_resources.png

** Description changed:

- The `gnome-system-monitor` package preinstalled with Ubuntu 18.04
- appears to have a problem with excluding `/dev/loop*` mounts from the
- File System tab.
- 
- This is a screenshot of what it shows on my system:
- 
- https://i.imgur.com/SHwXcsR.png
- 
- As you can see, there's a lot of `/dev/loop*` entries, and a lot of
+ The gnome-system-monitor package preinstalled with Ubuntu 18.04 appears
+ to have a problem with excluding /dev/loop* mounts from the File System
+ tab.
+ 
+ Attached is a screenshot of what it shows on my system.
+ 
+ As you can see, there's a lot of /dev/loop* entries, and a lot of
  duplication of available disk space percentage.
  
- This is a pastebin of `$ mount`: https://paste.ubuntu.com/p/T4ZKz99CdK/
+ This is a pastebin of $ mount:
+ 
+ sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
+ proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
+ udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=8101140k,nr_inodes=2025285,mode=755)
+ devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
+ tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1627500k,mode=755)
+ /dev/nvme0n1p3 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
+ securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
+ tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
+ tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
+ tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
+ cgroup on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
+ cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
+ pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
+ efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
+ cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
+ cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
+ cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
+ cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
+ cgroup on /sys/fs/cgroup/rdma type cgroup 
(rw,nosuid,nodev,noexec,relatime,rdma)
+ cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
+ cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
+ cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
+ cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
+ cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
+ cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
+ mqueue on /dev/mqueue type mqueue (rw,relatime)
+ debugfs on /sys/kernel/debug type debugfs (rw,relatime)
+ systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=45,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=22759)
+ hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
+ sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
+ fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
+ configfs on /sys/kernel/config type configfs (rw,relatime)
+ nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
+ /var/lib/snapd/snaps/gnome-3-26-1604_74.snap on /snap/gnome-3-26-1604/74 type 
squashfs (ro,nodev,relatime,x-gdu.hide)
+ /var/lib/snapd/snaps/telegram-desktop_384.snap on /snap/telegram-desktop/384 
type squashfs (ro,nodev,relatime,x-gdu.hide)
+ /var/lib/snapd/snaps/gnome-3-26-1604_70.snap on /snap/gnome-3-26-1604/70 type 
squashfs (ro,nodev,relatime,x-gdu.hide)
+ /var/lib/snapd/snaps/gnome-calculator_180.snap on /snap/gnome-calculator/180 
type squashfs (ro,nodev,relatime,x-gdu.hide)
+ /var/lib/snapd/snaps/core_6034.snap on /snap/core/6034 type squashfs 
(ro,nodev,relatime,x-gdu.hide)
+ /var/lib/snapd/snaps/gnome-calculator_238.snap on /snap/gnome-calculator/238 
type squashfs (ro,nodev,relatime,x-gdu.hide)
+ /var/lib/snapd/snaps/skype_63.snap on /snap/skype/63 type squashfs 
(ro,nodev,relatime,x-gdu.hide)
+ /var/lib/snapd/snaps/gnome-characters_103.snap on /snap/gnome-characters/103 
type squashfs (ro,nodev,relatime,x-gdu.hide)
+ /var/lib/snapd/snaps/core_5897.snap on /snap/core/5897 type squashfs 
(ro,nodev,relatime,x-gdu.hide)
+ /var/lib/snapd/snaps/gnome-characters_139.snap on /snap/gnome-characters/139 
type squashfs (ro,nodev,relatime,x-gdu.hide)
+ /var/lib/snapd/snaps/gnome-system-monitor_57.snap on 
/snap/gnome-system-monitor/57 type squashfs (ro,nodev,relatime,x-gdu.hide)
+ /var/lib/snapd/snaps/gnome-system-monitor_51.snap on

[Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

2018-12-13 Thread Jeremy Walker

The importance on this ticket is incorrect: it should not be marked
"low". According to https://dev.launchpad.net/BugTriage#importance)
"Low" is defined as "legitimate but that is not scheduled for Canonical
staff to fix in the next 6 months."

This is a MAJOR issue.  As W-barath-hotmail noted it can cause some
extremely serious side effects for anyone who relies on power
management.  As such, this ticket should have an importance of "High"
("we believe we will work on in the next six months").  To ignore it for
six or more months would be to deliberately cause serious user damage.

Also, this bug is difficult for users to track down. It's not like
problematic tabs flash red or something, so each user has to figure out
on their own that not only is Chrome the source of the problem, but a
specific tab within Chrome. As a result, the number of users affected by
this bug is undoubtedly much higher than what's reflected on this page,
as many affected users just aren't able to track the problem to this
page.

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

Title:
  Screen doesn't lock or go to sleep when certain Chrome tabs are open

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy gnome-session-bin
  gnome-session-bin:
    Installed: 3.18.1.2-1ubuntu1.16.04.1
    Candidate: 3.18.1.2-1ubuntu1.16.04.1
    Version table:
   *** 3.18.1.2-1ubuntu1.16.04.1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.1.2-1ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I'm using gnome-session-flashback

  What happens:
  The screen doesn't lock when having certain pages in Chrome tabs

  Expected:
  The screen should lock after the configured timeout in settings.

  I've been having this issue sice before 14.04, which I recently
  upgraded (fresh install) to 16.04.

  After fresh install, the screen would turn down and lock the computer
  after 10 minutes (or whatever time I setup). At one point it stopped
  working. The screen never shuts down unless I manually lock the
  session with CTRL-ALT-L.

  I've followed the steps in
  https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure

  The culprit seems to be that Chrome issues some suspend inhibitions
  through dbus when doing certain operations. Many people find this
  problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
  pretty sure that Chrome is doing something else of what i've found
  out.

  1) Gnome screen saver works correctly. I can trigger it manually with:
  $ gnome-screensaver-command -a

  2) Gnome screen saver never receives the "session idle" status
  callback.

  3) When Chrome is not running, I can manually inhibit the idle status:
  $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" 
--inhibit-only --inhibit idle:suspend
  Inhibiting until Ctrl+C is pressed...

  4) I can query the inhibitors:
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return 
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 
reply_serial=2
     array [
    object path "/org/gnome/SessionManager/Inhibitor1686"
     ]
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetAppId
  ('test',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetReason
  ('manual idle inhibit',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetFlags
  (uint32 12,)

  12=4(suspend) + 8(idle)

  5) When testing, I can inhibit for 70 seconds, idle timeout being 60
  (1 minute). After these 70 seconds pass, the screen locks.

  6) Regarding Chrome, this is the information I get when querying the 
inhibitor:
  GetAppId: ('/usr/bin/google-chrome-stable',)
  GetReason: ('Uploading data to 10.200.0.163',)
  GetFlags: (uint32 4,)

  The flags just inhibits suspend, not locking or entering powersaving
  mode.

  This inhibitor seems to stay for 10-15 seconds, then goes away for
  another 30-60 seconds. The screen NEVER locks when this tab is open.
  No matter the inhibitor is present or not.

  I'm not sure where to go on. If it's a Chrome bug it must be using
  other mechanisms to prevent the idle timeout. Any ideas on what to
  look for?

  Julian.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1808420] [NEW] gnome-system-monitor from Snap does not hide /dev/loop* mounts

2018-12-13 Thread Nope

Public bug reported:

The `gnome-system-monitor` package preinstalled with Ubuntu 18.04
appears to have a problem with excluding `/dev/loop*` mounts from the
File System tab.

This is a screenshot of what it shows on my system:

https://i.imgur.com/SHwXcsR.png

As you can see, there's a lot of `/dev/loop*` entries, and a lot of
duplication of available disk space percentage.

This is a pastebin of `$ mount`: https://paste.ubuntu.com/p/T4ZKz99CdK/

And this is a pastebin of my current `snap` version and `$ cat
/proc/self/mountinfo`: https://paste.ubuntu.com/p/3wvsFmnygw/

# How to reproduce

If your version of `gnome-system-monitor` is the default installed with
Ubuntu 18.04, you should already have this problem. If not, try removing
the current version `sudo apt remove gnome-system-monitor`, and
installing it from the snap store `sudo snap install gnome-system-
monitor` to have the problem show up.

It could be helpful to look into `$ cat /run/mount/utab` (I'm mentioning
this only because it was suggested to me to mention it). Unfortunately I
didn't do that before removing the snap package, so I don't have the
output available.

# Expected behaviour

I would expect to only see the actual partitions in my system, in my
case: `/`, `/home`, and `/boot/efi`, since I have `/home` on its own
partition.

# Workaround

A workaround to get rid of this problem is to remove the snap package
and install it via apt `sudo snap remove gnome-system-monitor && sudo
apt install gnome-system-monitor`. It worked for me, and after that I
only had the three partitions mentioned above showing up in the File
System tab.

Plus, I do have the output for `$ cat /run/mount/utab` this time:
https://paste.ubuntu.com/p/tJwqjDW6T6/

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

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

Title:
  gnome-system-monitor from Snap does not hide /dev/loop* mounts

Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  The `gnome-system-monitor` package preinstalled with Ubuntu 18.04
  appears to have a problem with excluding `/dev/loop*` mounts from the
  File System tab.

  This is a screenshot of what it shows on my system:

  https://i.imgur.com/SHwXcsR.png

  As you can see, there's a lot of `/dev/loop*` entries, and a lot of
  duplication of available disk space percentage.

  This is a pastebin of `$ mount`:
  https://paste.ubuntu.com/p/T4ZKz99CdK/

  And this is a pastebin of my current `snap` version and `$ cat
  /proc/self/mountinfo`: https://paste.ubuntu.com/p/3wvsFmnygw/

  # How to reproduce

  If your version of `gnome-system-monitor` is the default installed
  with Ubuntu 18.04, you should already have this problem. If not, try
  removing the current version `sudo apt remove gnome-system-monitor`,
  and installing it from the snap store `sudo snap install gnome-system-
  monitor` to have the problem show up.

  It could be helpful to look into `$ cat /run/mount/utab` (I'm
  mentioning this only because it was suggested to me to mention it).
  Unfortunately I didn't do that before removing the snap package, so I
  don't have the output available.

  # Expected behaviour

  I would expect to only see the actual partitions in my system, in my
  case: `/`, `/home`, and `/boot/efi`, since I have `/home` on its own
  partition.

  # Workaround

  A workaround to get rid of this problem is to remove the snap package
  and install it via apt `sudo snap remove gnome-system-monitor && sudo
  apt install gnome-system-monitor`. It worked for me, and after that I
  only had the three partitions mentioned above showing up in the File
  System tab.

  Plus, I do have the output for `$ cat /run/mount/utab` this time:
  https://paste.ubuntu.com/p/tJwqjDW6T6/

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

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

[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal

2018-12-13 Thread Pat Trainor

I see 9% consistently, and as with those above, clock_gettime seems to
be the culprit:

pat@wopr:~$ sudo strace -c -p 29333
[sudo] password for pat: 
strace: Process 29333 attached

^Cstrace: Process 29333 detached
% time seconds  usecs/call callserrors syscall
-- --- --- - - 
 83.372.716542   2   1494072   clock_gettime
  3.620.117823  32  3654   ioctl
  3.400.110891   3 40996 36714 recvmsg
  2.530.082418   6 13709   poll
[...]

Ubuntu 18.04, i7 4.0GHZ, 32GB RAM uname -a:
Linux wopr 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  High CPU usage by gnome-shell when only running gnome-terminal

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Even when doing nothing but displaying a terminal screen with top
  running gnome-shell uses 10% of a CPU. That seems excessive. I
  disabled all extensions to try and make the test fair. Enabling the
  system monitor extension increases the load to 13-14%. It seems that
  the gnome-shell screen painting is highly CPU consuming even if screen
  updates are infrequent (1 a second for all these cases).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 29 11:38:05 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-27 (578 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago)

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

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

[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal

2018-12-13 Thread Pat Trainor

In case the video is still suspected:

pat@wopr:~$ xrandr
Screen 0: minimum 8 x 8, current 9600 x 2160, maximum 16384 x 16384
VGA-0 disconnected (normal left inverted right x axis y axis)
LVDS-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 connected primary 1920x1080+3840+1080 (normal left inverted right x axis y 
axis) 344mm x 194mm
   1920x1080 60.02*+  47.99  
DP-1 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 600mm x 
340mm
   3840x2160 60.00*+  30.00  
   2560x1440 59.95  
   1920x1080 60.0059.94  
   1600x900  60.00  
   1280x1024 60.02  
   1280x800  59.81  
   1280x720  60.0059.94  
   1152x864  59.96  
   1024x768  60.00  
   800x600   60.32  
   720x480   59.94  
   640x480   59.9459.93  
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 connected 3840x2160+5760+0 (normal left inverted right x axis y axis) 
600mm x 340mm
   3840x2160 60.00 +  30.00* 
   2560x1440 59.95  
   1920x1080 60.0059.94  
   1600x900  60.00  
   1280x1024 60.02  
   1280x800  59.81  
   1280x720  60.0059.94  
   1152x864  59.96  
   1024x768  60.00  
   800x600   60.32  
   720x480   59.94  
   640x480   59.9459.93  
DP-4 disconnected (normal left inverted right x axis y axis)

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

Title:
  High CPU usage by gnome-shell when only running gnome-terminal

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Even when doing nothing but displaying a terminal screen with top
  running gnome-shell uses 10% of a CPU. That seems excessive. I
  disabled all extensions to try and make the test fair. Enabling the
  system monitor extension increases the load to 13-14%. It seems that
  the gnome-shell screen painting is highly CPU consuming even if screen
  updates are infrequent (1 a second for all these cases).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 29 11:38:05 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-27 (578 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago)

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

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

[Desktop-packages] [Bug 1808419] [NEW] Screen Brightness problem

2018-12-13 Thread Java

Public bug reported:

When i switch on my laptop with Ubuntu. It starts with lowest brightness. Even 
it set to normal. When i set it again it returning to normal. But when after 
screen dimming it does not return again. So it doesnt recognize to my mouse or 
keyboard.
Sorry for my English. I hope I could explain my problem.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: wl nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 14 02:43:24 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-34-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-36-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04ca]
 NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell GF108M [GeForce GT 525M] [1028:04ca]
InstallationDate: Installed on 2018-09-30 (74 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. Inspiron N5110
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=4a66061d-c599-4959-97d9-eee379ba8b99 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0HVRTT
dmi.board.vendor: Dell Inc.
dmi.board.version: A11
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0HVRTT:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron N5110
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** 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/1808419

Title:
  Screen Brightness problem

Status in xorg package in Ubuntu:
  New

Bug description:
  When i switch on my laptop with Ubuntu. It starts with lowest brightness. 
Even it set to normal. When i set it again it returning to normal. But when 
after screen dimming it does not return again. So it doesnt recognize to my 
mouse or keyboard.
  Sorry for my English. I hope I could explain my problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 14 02:43:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed
   bcmwl,

[Desktop-packages] [Bug 1808410] Re: package firefox-locale-en 63.0.3+build1-0ubuntu0.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at

2018-12-13 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package firefox-locale-en 63.0.3+build1-0ubuntu0.18.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in firefox package in Ubuntu:
  New

Bug description:
  error not working sometime when i open alot of apps and my mouse
  cannot move.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: firefox-locale-en 63.0.3+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   thavorn1353 F...m pulseaudio
   /dev/snd/controlC0:  gdm 988 F pulseaudio
thavorn1353 F pulseaudio
  BuildID: 20181116154524
  Channel: Unavailable
  Date: Fri Dec 14 02:35:44 2018
  Dependencies:
   
  DuplicateSignature:
   package:firefox-locale-en:63.0.3+build1-0ubuntu0.18.04.1
   Unpacking mysql-server (5.7.24-0ubuntu0.18.04.1) ...
   dpkg: error processing package firefox-locale-en (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-08 (96 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 172.20.10.1 dev enp0s20f0u2c4i2 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s20f0u2c4i2 scope link metric 1000 
   172.20.10.0/28 dev enp0s20f0u2c4i2 proto kernel scope link src 172.20.10.2 
metric 100
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox-locale-en 63.0.3+build1-0ubuntu0.18.04.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)
  dmi.bios.date: 03/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UQK.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UQK
  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.:bvrX556UQK.309:bd03/02/2017:svnASUSTeKCOMPUTERINC.:pnX556UQK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UQK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X556UQK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1808410] [NEW] package firefox-locale-en 63.0.3+build1-0ubuntu0.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before

2018-12-13 Thread Lorn Thavorn

Public bug reported:

error not working sometime when i open alot of apps and my mouse cannot
move.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: firefox-locale-en 63.0.3+build1-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   thavorn1353 F...m pulseaudio
 /dev/snd/controlC0:  gdm 988 F pulseaudio
  thavorn1353 F pulseaudio
BuildID: 20181116154524
Channel: Unavailable
Date: Fri Dec 14 02:35:44 2018
Dependencies:
 
DuplicateSignature:
 package:firefox-locale-en:63.0.3+build1-0ubuntu0.18.04.1
 Unpacking mysql-server (5.7.24-0ubuntu0.18.04.1) ...
 dpkg: error processing package firefox-locale-en (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-09-08 (96 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
IpRoute:
 default via 172.20.10.1 dev enp0s20f0u2c4i2 proto dhcp metric 100 
 169.254.0.0/16 dev enp0s20f0u2c4i2 scope link metric 1000 
 172.20.10.0/28 dev enp0s20f0u2c4i2 proto kernel scope link src 172.20.10.2 
metric 100
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
RunningIncompatibleAddons: False
SourcePackage: firefox
Title: package firefox-locale-en 63.0.3+build1-0ubuntu0.18.04.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)
dmi.bios.date: 03/02/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X556UQK.309
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X556UQK
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.:bvrX556UQK.309:bd03/02/2017:svnASUSTeKCOMPUTERINC.:pnX556UQK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UQK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X556UQK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  package firefox-locale-en 63.0.3+build1-0ubuntu0.18.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in firefox package in Ubuntu:
  New

Bug description:
  error not working sometime when i open alot of apps and my mouse
  cannot move.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: firefox-locale-en 63.0.3+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   thavorn1353 F...m pulseaudio
   /dev/snd/controlC0:  gdm 988 F pulseaudio
thavorn1353 F pulseaudio
  BuildID: 20181116154524
  Channel: Unavailable
  Date: Fri Dec 14 02:35:44 2018
  Dependencies:
   
  DuplicateSignature:
   package:firefox-locale-en:63.0.3+build1-0ubuntu0.18.04.1
   Unpacking mysql-server (5.7.24-0ubuntu0.18.04.1) ...
   dpkg: error processing package firefox-locale-en (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-08 (96 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 172.20.10.1 dev enp0s20f0u2c4i2 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s20f0u2c4i2 scope link metric 1000 
   172.20.10.0/28 dev

[Desktop-packages] [Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts

** Changed in: xorg-server
   Status: Confirmed => Unknown

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts

Status in gnome-control-center:
  Unknown
Status in X.Org X server:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press  (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  For users being affected by this problem, the easiest solution for now is to 
add this PPA in your repositories:
  https://launchpad.net/~oded-geek/+archive/xorg-patches

  Practical summary of this bug for ubuntu developers (since reading 120 
comments is impractical for most):
  This problem is a really old (since 2004) issue of the xkb part of xorg; the 
main discussion was made upstream in freedesktop-bugs #865. There has been a 
patch from Ilya Murav'jov for upstream (#55), and attached here (#61).
  Upstream xorg has refused to apply the patch, mainly because it "explicitly 
contradicts the (xkb) spec"  (#84, #91).
  This patch has been reported to work for many people without any problems, 
and there is also a PPA by Oded Arbel (#95) where he maintains a patched 
version of the ubuntu xorg.
  The proper resolution of this bug would be to apply this patch to the 
upstream xorg, or at minimum to the official ubuntu xorg package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/36812/+subscriptions

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

[Desktop-packages] [Bug 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)

** Changed in: xorg-server
   Status: Confirmed => Unknown

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts (reopen)

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New

Bug description:
  From duplicate bug 1720364 report.

  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
  2. Set-up two keyboard layouts - English and Russian
  3. Set  as keyboard layout switcher in mate-control-center
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma, write some text, try to navigate in it with 
.

  Expected results:
   switches keyboard layout, shortcuts starting from 
 work normally.

  Actual results:
   switches keyboard layout, shortcuts starting from 
 do not work.

  Notes:
  1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
  2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.

  ---
  Original description below:

  This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04
  Zesty Zapus.

  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  Apparently, the bug has reappeared after the patch that used to fix
  the problem (208_switch_on_release.diff) has been removed from X.Org
  1.19 packages. There is an updated patch in the upstream ticket
  https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the
  attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.19.3-1ubuntu1
  Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 17 17:46:35 2017
  InstallationDate: Installed on 2015-05-01 (716 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago)

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

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

[Desktop-packages] [Bug 36812]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/258.

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts

Status in gnome-control-center:
  Unknown
Status in X.Org X server:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press  (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  For users being affected by this problem, the easiest solution for now is to 
add this PPA in your repositories:
  https://launchpad.net/~oded-geek/+archive/xorg-patches

  Practical summary of this bug for ubuntu developers (since reading 120 
comments is impractical for most):
  This problem is a really old (since 2004) issue of the xkb part of xorg; the 
main discussion was made upstream in freedesktop-bugs #865. There has been a 
patch from Ilya Murav'jov for upstream (#55), and attached here (#61).
  Upstream xorg has refused to apply the patch, mainly because it "explicitly 
contradicts the (xkb) spec"  (#84, #91).
  This patch has been reported to work for many people without any problems, 
and there is also a PPA by Oded Arbel (#95) where he maintains a patched 
version of the ubuntu xorg.
  The proper resolution of this bug would be to apply this patch to the 
upstream xorg, or at minimum to the official ubuntu xorg package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/36812/+subscriptions

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

[Desktop-packages] [Bug 1683383]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/258.

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts (reopen)

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New

Bug description:
  From duplicate bug 1720364 report.

  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
  2. Set-up two keyboard layouts - English and Russian
  3. Set  as keyboard layout switcher in mate-control-center
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma, write some text, try to navigate in it with 
.

  Expected results:
   switches keyboard layout, shortcuts starting from 
 work normally.

  Actual results:
   switches keyboard layout, shortcuts starting from 
 do not work.

  Notes:
  1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
  2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.

  ---
  Original description below:

  This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04
  Zesty Zapus.

  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  Apparently, the bug has reappeared after the patch that used to fix
  the problem (208_switch_on_release.diff) has been removed from X.Org
  1.19 packages. There is an updated patch in the upstream ticket
  https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the
  attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.19.3-1ubuntu1
  Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 17 17:46:35 2017
  InstallationDate: Installed on 2015-05-01 (716 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago)

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

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

[Desktop-packages] [Bug 1798861] Re: Tooltips flicker constantly in GTK3 applications

** Changed in: gtk+3.0 (Debian)
   Status: Confirmed => Fix Released

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

Title:
  Tooltips flicker constantly in GTK3 applications

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  Tooltips are flicker constantly (i.e. repeatedly shown and the hidden
  again) in GTK3 applications under XFCE.

  It is a regression in the recent GTK 3.24.

  This is the upstream report and fix:
  https://gitlab.gnome.org/GNOME/gtk/issues/1371
  
https://gitlab.gnome.org/GNOME/gtk/commit/9b7d886b723132eade2e76f3fd179cf81b7601f2

  A workaround for XFCE is as follows:

  Open Settings Editor.
  Set xsettings -> Gtk -> CursorThemeSize to 16.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgtk-3-0 3.24.1-1ubuntu2
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Oct 19 12:23:53 2018
  InstallationDate: Installed on 2017-02-01 (624 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1798861/+subscriptions

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

[Desktop-packages] [Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised

2018-12-13 Thread LYUDMILA RVANOVA

** Also affects: libfprint
   Importance: Undecided
   Status: New

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

Title:
  [04f3:0903] Elan Microelectronics Corp fingerprint reader not
  recognised

Status in libfprint:
  New
Status in libfprint package in Ubuntu:
  Confirmed

Bug description:
  Running "fprint-demo" with this hardware installed reports "No devices
  found".

  This is the integrated reader in new ASUS ZenBook UX390UA laptops.

  lsusb -v output here: http://paste.ubuntu.com/23464942/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libfprint0 1:0.6.0-2
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Nov 12 15:59:17 2016
  InstallationDate: Installed on 2016-11-08 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: libfprint
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1808203] Re: ddfs

2018-12-13 Thread Leonidas S. Barbosa

** Information type changed from Private Security to Public

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

Title:
  ddfs

Status in xorg package in Ubuntu:
  New

Bug description:
  sdfsf

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Dec 12 21:07:13 2018
  DistUpgraded: 2018-12-12 20:39:45,935 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Wrestler [Radeon HD 7340] [104d:90ad]
  InstallationDate: Installed on 2016-04-24 (962 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Sony Corporation SVE1112M1EW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=40da7131-b99a-4e5b-9c5e-81ba4975e74c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-12-12 (0 days ago)
  dmi.bios.date: 08/22/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0120D8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0120D8:bd08/22/2012:svnSonyCorporation:pnSVE1112M1EW:pvrC60B8BEP:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVE1112M1EW
  dmi.product.version: C60B8BEP
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~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: Wed Dec 12 18:07:04 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1786344] Re: Default IBus input method ignored in live session

2018-12-13 Thread Ping-Wu

Ubuntu 18.10. Initial install in en_US.  When I tried to create a new
user with zh_CN environment, I only had the option of choosing
中国（香港）“China (Hong Kong)".  This should be corrected to allow users to
choose "China".

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

Title:
  Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
  input Chinese character. From Settings -> Regions and Languages, selected
  Intelligent Pinyin, also could not input Chinese.

  ---

  18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
  Languages，选择 智能拼音，也无法输入中文。

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

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

[Desktop-packages] [Bug 1808398] [NEW] top right menu does not display when activated

Public bug reported:

1) Install Ubuntu 18.04.1 via debbootstrap
2) Install ubuntu-desktop package
3) Install vanilla-desktop package
4) Upgrade to 18.10 using the Software GUI
5) Log into Ubuntu on Wayland
6) Click right end of top bar, menu drops down.
7) Mouse over menu, no visual feedback of focus (as with Ubuntu on Xorg)
8) Interact with menu items - there is no visual feedback. For example 
 - sliding back and forth on the screen brightness slider causes the screen 
brightness to change as expected but the slider does not reflect changes. 
Clicking on the right end of the top bar causes the menu to deactivate but 
before it does, the slider position updates.
 - click on the user name and nothing appears to happen. Click below it where 
the submenu would appear causes the submenu to activate. (the logout dialog 
appears.)

I'm not sure if steps 1-4 are required vs. just installing 18.10 but I
list it in case this results from left over settings from 18.04
installing via debbootstrap.

hbarta@saugage:~$ lsb_release -rd
Description:Ubuntu 18.10
Release:18.10
hbarta@saugage:~$ 

hbarta@saugage:~$ apt-cache policy gnome-shell mutter xwayland gnome-menus 
libgnome-menu-3-0:amd64
gnome-shell:
  Installed: 3.30.1-2ubuntu1.18.10.1
  Candidate: 3.30.1-2ubuntu1.18.10.1
  Version table:
 *** 3.30.1-2ubuntu1.18.10.1 500
500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
100 /var/lib/dpkg/status
 3.30.1-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
mutter:
  Installed: 3.30.2-1~ubuntu18.10.1
  Candidate: 3.30.2-1~ubuntu18.10.1
  Version table:
 *** 3.30.2-1~ubuntu18.10.1 500
500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
100 /var/lib/dpkg/status
 3.30.1-1 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
xwayland:
  Installed: 2:1.20.1-3ubuntu2.1
  Candidate: 2:1.20.1-3ubuntu2.1
  Version table:
 *** 2:1.20.1-3ubuntu2.1 500
500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 
Packages
500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
100 /var/lib/dpkg/status
 2:1.20.1-3ubuntu2 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
gnome-menus:
  Installed: 3.13.3-11ubuntu2
  Candidate: 3.13.3-11ubuntu2
  Version table:
 *** 3.13.3-11ubuntu2 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status
libgnome-menu-3-0:
  Installed: 3.13.3-11ubuntu2
  Candidate: 3.13.3-11ubuntu2
  Version table:
 *** 3.13.3-11ubuntu2 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status
hbarta@saugage:~$ 


Expected behavior: menu provides visual feedback to clicks. Underlying action 
seems to happen but there is no hint of that or display of submenus.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
Uname: Linux 4.18.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 13 11:41:23 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to cosmic on 2018-12-13 (0 days ago)
mtime.conffile..etc.logrotate.d.apport: 2018-12-12T13:31:49.347693

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


** Tags: amd64 apport-bug cosmic wayland-session

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

Title:
  top right menu does not display when activated

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  1) Install Ubuntu 18.04.1 via debbootstrap
  2) Install ubuntu-desktop package
  3) Install vanilla-desktop package
  4) Upgrade to 18.10 using the Software GUI
  5) Log into Ubuntu on Wayland
  6) Click right end of top bar, menu drops down.
  7) Mouse over menu, no visual feedback of focus (as with Ubuntu on Xorg)
  8) Interact with menu items - there is no visual feedback. For example 
   - sliding back and forth on the screen brightness slider causes the screen 
brightness to change as expected but the slider does not reflect changes. 
Clicking on the right end of the top bar causes the menu to deactivate but 
before it does, the slider position updates.
   - click on the user name and nothing appears to happen. Click below it where 
the submenu would appear causes the submenu to

[Desktop-packages] [Bug 1808397] [NEW] Evince does not show content of inserted text comments

2018-12-13 Thread Karl Kastner

Public bug reported:

Evince does not display the content of text inserted by acrobat reader
annotations. It does show the blue triangles and opens a box when one
clicks on a triangle, but the inserted text is not displayed in the box.
In contrast, the content of yellow sticky notes is properly displayed.
Okular properly displays the content of the inserted text, so it is not
an inaccessible proprietary feature. Example file is attached.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: evince 3.30.1-1ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
Uname: Linux 4.18.0-12-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Dec 11 16:05:32 2018
InstallationDate: Installed on 2015-11-05 (1132 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: evince
UpgradeStatus: Upgraded to cosmic on 2018-10-18 (53 days ago)

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


** Tags: amd64 apparmor apport-bug cosmic

** Attachment added: "16.pdf"
   https://bugs.launchpad.net/bugs/1808397/+attachment/5222039/+files/16.pdf

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

Title:
  Evince does not show content of inserted text comments

Status in evince package in Ubuntu:
  New

Bug description:
  Evince does not display the content of text inserted by acrobat reader
  annotations. It does show the blue triangles and opens a box when one
  clicks on a triangle, but the inserted text is not displayed in the
  box. In contrast, the content of yellow sticky notes is properly
  displayed. Okular properly displays the content of the inserted text,
  so it is not an inaccessible proprietary feature. Example file is
  attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.1-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec 11 16:05:32 2018
  InstallationDate: Installed on 2015-11-05 (1132 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (53 days ago)

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

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

[Desktop-packages] [Bug 1804685] Re: Icon View Captions display in the wrong positions

2018-12-13 Thread Dan Green

How do I "nominate to Bionic"?  I appreciate it's a simple fix, just
don't know the process to get Canonical to patch

Thanks,

Dan

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

Title:
  Icon View Captions display in the wrong positions

Status in nautilus package in Ubuntu:
  Fix Committed

Bug description:
  In the Preferences for Nautilus, under the Views tab, the user has the
  option to select information to appear in the "First", "Second", and
  "Third" position beneath icons.  However, in icon view,  whatever the
  user selects to appear in the "First" position will appear in the
  second location beneath the icon.  Whatever the user selects to appear
  in the "Second" position will appear in the third, or bottom,
  position.  Whatever the user selects to appear in the "Third" position
  will appear in the first, or top, position.

  I'm on

  Ubuntu 18.04.1 LTS
  Nautilus 3.26.4-0~ubuntu18.04.2

  Thanks!

  Upstream bugs:
  https://gitlab.gnome.org/GNOME/nautilus/issues/343
  https://gitlab.gnome.org/GNOME/nautilus/issues/766

  Upstream Fix:
  
https://gitlab.gnome.org/GNOME/nautilus/commit/86080e646a81679761e09aee4071abf68a2dac3b

  Steps to reproduce:
  1. Change to 100% zoom
  2. Go to Preferences > Icon View Captions
  3. There are three captions: First, Second & Third
  I expect to see that the 1st caption is displayed just below the file/folder 
name, 2nd is below 1st and 3rd is below 2nd.

  Current behaviour:
  The order of the captions is mixed up.
  The current order is this:
  - File/Folder Name
  - Third caption
  - First caption
  - Second caption

  Expected behaviour:
  - File/Folder Name
  - First caption
  - Second caption
  - Third caption

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

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

[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-13 Thread chovy

yes, i also got `command not found` when running `fakeroot`

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions

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

[Desktop-packages] [Bug 1808147] Re: autopkgtests fail on s390x

2018-12-13 Thread Olivier Tilloy

I have uploaded 1:6.1.3-0ubuntu8 to disco with this tentative fix:
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=b11b80afb8947d08aa2ea182a7c7371597432305

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

Title:
  autopkgtests fail on s390x

Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  libreoffice autopkgtests on s390x started failing reliably on
  2018-12-11.

  This corresponds to when a new version of autopkgtest was deployed to
  the production infrastructure: https://lists.ubuntu.com/archives
  /ubuntu-devel/2018-December/040564.html

  The failing test is "smoketest". It has the "skippable" restriction,
  which was previously unknown, and as a result the test was skipped
  altogether. "skippable" is now a valid and understood restriction, so
  the test is being run, but it fails:

  […]
  mkdir -p 
/tmp/autopkgtest.A1jy64/build.urp/src/workdir/CustomTarget/i18npool/textconversion/
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libcollator_data.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libdict_ja.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libdict_zh.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libindex_data.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/liblocaledata_en.so
  /tmp/autopkgtest.A1jy64/build.urp/src/solenv/gbuild/Package.mk:82: *** 
Something depends on package test_unittest which does not exist..  Stop.
  make[1]: *** Waiting for unfinished jobs
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libtextconv_dict.so
  [build PKG] test_unittest
  make[1]: Leaving directory '/tmp/autopkgtest.A1jy64/build.urp/src'
  make: *** [Makefile:112: i18npool.all] Error 2
  autopkgtest [13:27:33]: test smoketest: ---]
  autopkgtest [13:27:34]: test smoketest:  - - - - - - - - - - results - - - - 
- - - - - -
  smoketestFAIL non-zero exit status 1

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

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

[Desktop-packages] [Bug 1796265] Re: Ubuntu Dock is missing after unlocking screen

2018-12-13 Thread pureblood

I have what looks like the same issue. When I lock my screen with
"Super+L" the first time it goes into a flickering screen and the second
time it locks the session. Then I login again, one of my shell
extensions does not work anymore (PutWindows), and to make it work again
I have to uninstall and install it again. I also have the issue that the
Ubuntu dock does not auto-hide anymore unless I restart the session. I
am not sure whether these problems are all connected. I use Xorg on
Ubuntu 18.10. All these problems arose after updating from Ubuntu 18.04.

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

Title:
  Ubuntu Dock is missing after unlocking screen

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

Bug description:
  After locking the screen, unlocking it again does not return me to a
  properly working gnome-shell. I can see the desktop background and the
  top panel (which is responsive). However I cannot access the
  activities overview, and the Ubuntu dock is missing.

  One time I noticed that the search field from the activities overview
  was visible, and it was possible to search for an application. The
  search did return results, and it was possible to start applications,
  but they did not show up on the screen.

  In some cases I could run gnome-shell -r, but this would end the whole
  session and return me to the login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  5 12:44:13 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-03 (458 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-10-05 (0 days ago)

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

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

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

apport information

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

Title:
  Battery indicator shows false reading

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% 
(Fully charged when plugged in) but when plugged out the battery shows 94%. 
Batteries are fine, no issues whatsoever with batteries.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1808193/+subscriptions

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

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

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1808193/+attachment/5222032/+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/1808193

Title:
  Battery indicator shows false reading

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% 
(Fully charged when plugged in) but when plugged out the battery shows 94%. 
Batteries are fine, no issues whatsoever with batteries.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1808193/+subscriptions

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

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

apport information

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

Title:
  Battery indicator shows false reading

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% 
(Fully charged when plugged in) but when plugged out the battery shows 94%. 
Batteries are fine, no issues whatsoever with batteries.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1808193/+subscriptions

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

[Desktop-packages] [Bug 1808193] Re: Battery indicator shows false reading

apport information

** Tags added: apport-collected cosmic

** Description changed:

- The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows
- 100% (Fully charged when plugged in) but when plugged out the battery
- shows 94%. Batteries are fine, no issues whatsoever with batteries.
+ The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% 
(Fully charged when plugged in) but when plugged out the battery shows 94%. 
Batteries are fine, no issues whatsoever with batteries.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 18.10
+ InstallationDate: Installed on 2018-12-10 (3 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
+ Tags:  cosmic
+ Uname: Linux 4.18.0-12-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  Battery indicator shows false reading

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% 
(Fully charged when plugged in) but when plugged out the battery shows 94%. 
Batteries are fine, no issues whatsoever with batteries.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1808193/+subscriptions

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

[Desktop-packages] [Bug 1799430] Re: Icon dock visible on lock screen

2018-12-13 Thread R_volkmann

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

** This bug has been marked a duplicate of bug 1769383
   Ubuntu dock/launcher is shown on the lock screen

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

Title:
  Icon dock visible on lock screen

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When locking the machine with alt-L the icon dock is still visible.

  After Login, the dock does not get adjusted to the top menu.

  In rare cases, the dock does not respond any more. This requires a
  reboot of the machine

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: mutter 3.30.1-1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 23 12:59:27 2018
  InstallationDate: Installed on 2018-04-30 (176 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

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

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

[Desktop-packages] [Bug 1455097] Please test proposed package

2018-12-13 Thread Łukasz Zemczak

Hello Alex, or anyone else affected,

Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 in a few hours, and then
in the -proposed repository.

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

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

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

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

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

Title:
  /etc/pm/sleep.d/ is no more processed

Status in aiccu package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in ifplugd package in Ubuntu:
  New
Status in lizardfs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  New
Status in pm-utils package in Ubuntu:
  Won't Fix
Status in toshset package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed

Bug description:
  [Impact (unattended-upgrades)]

   * Unattended-upgrades does not gracefully stop installing updates
  when the system goes to hibernation potentially letting the system to
  hibernate in a state where the system can't resume from.

  [Test Case (unattended-upgrades)]

   * Configure the system to have several 20+ packages upgradable by
  unattended-upgrades. One easy way of setting this up is starting with
  a system where packages from -security are installed but packages from
  -updates are not and enabling -updates in u-u:

# echo 'Unattended-Upgrade::Allowed-Origins::
  "${distro_id}:${distro_codename}-updates";' > /etc/apt/apt.conf.d
  /51unattended-upgrades-updates-too

  * Pre-download upgrades
# unattended-upgraded --download-only

  * Trigger unattended-upgrades run:
#  service apt-daily-upgrade start

  * Hibernate, then resume the system and watch unattended-upgrades
  being gracefully stopped, checking /var/log/unattended-upgrades
  /unattended-upgrades.log. There should be packages left to be
  upgraded.

  [Regression Potential (unattended-upgrades)]

   * The added hook for unattended-upgrades may block the system from
  hibernation for 25 minutes if unattended-upgrades (or most likely a
  package upgrades) hangs. There is a better solution proposed based on
  systemd's inhibitor interface at https://github.com/mvo5/unattended-
  upgrades/issues/162 .

  [Original Bug Text]

  I added a new script in /etc/pm/sleep.d/ that worked fine before the
  upgrade to vivid. I was wondering why it doesn't work and I find out
  that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last
  logs from pm-suspend were on Apr 28, when I upgraded from utopic to
  vivid.

  The laptop suspends and wakes fine, it just seems that no pm scripts
  are run after suspend/powersave.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pm-utils 1.4.1-15
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 14 15:36:26 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-03-12 (792 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1624644] Please test proposed package

2018-12-13 Thread Łukasz Zemczak

Hello Jarno, or anyone else affected,

Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 in a few hours, and then
in the -proposed repository.

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

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

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

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

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-manager source package in Xenial:
  Fix Released
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades, the fix comes in an update of u-u) Run
  unattended-upgrades manually and observe the removal of the
  autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by

[Desktop-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually

2018-12-13 Thread Jeff Campbell

I have a Sony MDR-XB950N1 and I'm seeing the same thing

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

Title:
  Bluetooth headphones only use A2DP when connected manually

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+subscriptions

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

[Desktop-packages] [Bug 1808147] Re: autopkgtests fail on s390x

2018-12-13 Thread Olivier Tilloy

** Changed in: libreoffice (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  autopkgtests fail on s390x

Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  libreoffice autopkgtests on s390x started failing reliably on
  2018-12-11.

  This corresponds to when a new version of autopkgtest was deployed to
  the production infrastructure: https://lists.ubuntu.com/archives
  /ubuntu-devel/2018-December/040564.html

  The failing test is "smoketest". It has the "skippable" restriction,
  which was previously unknown, and as a result the test was skipped
  altogether. "skippable" is now a valid and understood restriction, so
  the test is being run, but it fails:

  […]
  mkdir -p 
/tmp/autopkgtest.A1jy64/build.urp/src/workdir/CustomTarget/i18npool/textconversion/
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libcollator_data.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libdict_ja.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libdict_zh.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libindex_data.so
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/liblocaledata_en.so
  /tmp/autopkgtest.A1jy64/build.urp/src/solenv/gbuild/Package.mk:82: *** 
Something depends on package test_unittest which does not exist..  Stop.
  make[1]: *** Waiting for unfinished jobs
  S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir &&  
touch $W/Headers/Library/libtextconv_dict.so
  [build PKG] test_unittest
  make[1]: Leaving directory '/tmp/autopkgtest.A1jy64/build.urp/src'
  make: *** [Makefile:112: i18npool.all] Error 2
  autopkgtest [13:27:33]: test smoketest: ---]
  autopkgtest [13:27:34]: test smoketest:  - - - - - - - - - - results - - - - 
- - - - - -
  smoketestFAIL non-zero exit status 1

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

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

[Desktop-packages] [Bug 1808352] [NEW] Context menus spawn in a way that causes unintended clicks when using Firefox CSD

2018-12-13 Thread Douglas H. Silva

Public bug reported:

HOW TO REPRODUCE
1 - First, open Firefox, enable Client Side Decoration, restart the program.
2 - Open some webpage, make sure you navigate a bit, leaving behind pages that 
can be returned to.
3 - Then right click anywhere on the current page. On my system, the context 
menu 'back' button appears right beneath the mouse cursor, and a click is 
automatically inserted there, making the page 'go back' everytime you right 
click with the mouse.

Running Xubuntu 18.04.1 LTS
Firefox 64.0

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 64.0+build3-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  dsilva 1420 F pulseaudio
 /dev/snd/controlC0:  dsilva 1420 F pulseaudio
BuildID: 20181207224003
Channel: Unavailable
CurrentDesktop: XFCE
Date: Thu Dec 13 12:35:17 2018
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2018-12-13 (0 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
IpRoute:
 default via 10.0.0.1 dev wlp6s0 proto dhcp metric 600 
 10.0.0.0/24 dev wlp6s0 proto kernel scope link src 10.0.0.102 metric 600 
 169.254.0.0/16 dev wlp6s0 scope link metric 1000
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=64.0/20181207224003
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/27/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 09WGNT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/27/2018:svnDellInc.:pnInspiron5458:pvr:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5458
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  Context menus spawn in a way that causes unintended clicks when using
  Firefox CSD

Status in firefox package in Ubuntu:
  New

Bug description:
  HOW TO REPRODUCE
  1 - First, open Firefox, enable Client Side Decoration, restart the program.
  2 - Open some webpage, make sure you navigate a bit, leaving behind pages 
that can be returned to.
  3 - Then right click anywhere on the current page. On my system, the context 
menu 'back' button appears right beneath the mouse cursor, and a click is 
automatically inserted there, making the page 'go back' everytime you right 
click with the mouse.

  Running Xubuntu 18.04.1 LTS
  Firefox 64.0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 64.0+build3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1420 F pulseaudio
   /dev/snd/controlC0:  dsilva 1420 F pulseaudio
  BuildID: 20181207224003
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Dec 13 12:35:17 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-12-13 (0 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.0.0.1 dev wlp6s0 proto dhcp metric 600 
   10.0.0.0/24 dev wlp6s0 proto kernel scope link src 10.0.0.102 metric 600 
   169.254.0.0/16 dev wlp6s0 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=64.0/20181207224003
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.

[Desktop-packages] [Bug 1808275] Re: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] Changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped

2018-12-13 Thread Paul

I have tried rebooting multiple times after all the suggestions that I
could find on this issue on the net. It still doesn't seem to work.

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

Title:
  [, SigmaTel STAC9221D A2, Green Headphone Out, Front] Changed the
  sound output from analog output to digital output(S/PDIF) and it
  suddenly stopped

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  The green headphone out was working and I changed the sound output
  from analog output to digital output(S/PDIF) and it suddenly stopped
  and changing it back to Analog Output didn't restore the sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Wed Dec 12 23:10:39 2018
  InstallationDate: Installed on 2018-12-06 (7 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BX97510J.86A.1487.2007.0902.1724
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: D975XBX
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD27094-305
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBX97510J.86A.1487.2007.0902.1724:bd09/02/2007:svn:pn:pvr:rvnIntelCorporation:rnD975XBX:rvrAAD27094-305:cvn:ct2:cvr:

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

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

[Desktop-packages] [Bug 1332623] Re: Thunar behaves inconsistently with USB flash drive FAT32 partitions

2018-12-13 Thread MDE

As I recall, this bug is about getting the error message "destination is
read-only" on a drive which has become read-only one time during a login
session despite remounting or inserting other drives which get the same
device name.

If you don't see this error message, then your bug is a different one.
Reading https://forum.xfce.org/viewtopic.php?pid=50502#p50502 I see no
similarities between the two cases.

I didn't verify the fix with the updated glib packages available in
bionic (2.56.x), but will do in the following days.

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

Title:
  Thunar behaves inconsistently with USB flash drive FAT32 partitions

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  Fix Released

Bug description:
  I installed Xubuntu 14.04 and performed no customizations or
  reconfigurations.

  Observation:  Thunar 1.6.3 ("File Manager" from menu) on Xubuntu 14.04 
handles write permission to inserted USB flash drives inconsistently:
  * I am able to create a nil file on the flash drive with Thunar and edit it.  
Clearly, the flash drive is not read-only.
  * Using Thunar, I cannot copy an existing file (E.g. ~/.profile) and paste it 
on the flash drive - "destination is read-only" (not true!).
  * However, in a terminal window, `cp` with the flash drive as a destination 
succeeds.

  I tried this on drives by different manufacturers and with differing
  capacities and on two different Xubuntu 14.04 installations.

  There might be a configuration change for Thunar to allow paste to
  flash drives.  If so, this should be enabled when Thunar is installed
  as this behaviour is what users expect.

  Note: I created the FAT32 partition with `gparted` on Linux.  I also
  got the same results after creating a FAT32 partition using an MACOSX
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: thunar 1.6.3-1ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jun 20 11:30:40 2014
  InstallationDate: Installed on 2014-06-19 (1 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: thunar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1332623/+subscriptions

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

[Desktop-packages] [Bug 1273524] Re: LXDE guest session shows error message "no session for pid "

2018-12-13 Thread Markus Kwaśnicki

Sadly, I confirm this bug still exists in Lubuntu 18.04.1 :-(

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

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Triaged
Status in Light Display Manager:
  Triaged
Status in Light Display Manager 1.18 series:
  Triaged
Status in lightdm package in Ubuntu:
  Confirmed
Status in lxsession package in Ubuntu:
  Triaged
Status in lightdm source package in Xenial:
  Confirmed
Status in lxsession source package in Xenial:
  Confirmed

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2018-12-13 Thread Colin Watson

I've hidden comment #24 on this bug due to a privacy request. Here's
the redacted text of that comment (from ~archenroot-gmail):

Another related bug is available on related bug in Arch:
https://bugs.archlinux.org/task/49157

Interesting is suggestion about possible HDMI vs sound conflicts:

Comment by [redacted] - Monday, 08 August 2016, 14:28 GMT
When I changed video drivers, the problem seemed to morph into a different
problem.

When I use nouveau/intel with bumblebee, it seems that plugging
headphones in constantly works like it should. Headphones show up as
headphones and the computer seems to recognize both. BUT... there is no
sound from the headphones, even after a restart. I am starting to
believe that this is an issue with either the nvidia driver, or
bumblebee/optimus. I think I had read in the past that the sound is
conflicting with the HDMI port or something like that. I reverted back
to nvidia due to compatibility issues with nouveau (or I'm just not
reading all the necessary documentation) and this original problem came
back.

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

Title:
[XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
while

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I'm experiencing a strange behavior with a headphone jack on my
laptop.

I have an external audio speaker connected to it. When I disconnect the
speaker and reconnect it again it stops working.
Even more, laptop audio stops working too. And after the reboot, I don't even
see any of the audio devices.

I've googled a lot and tried different fixes from forums with no luck.
After a while, I've accidentally discovered that putting the laptop to
the sleep mode and rebooting system after brings audio back to live.
Even more, if speakers were attached during this sleep-reboot
procedure, they are starting to work as well.

However, after the next reboot speakers are not working again. And if
I will plug them out and in - problem with completely missing audio
returns.

P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
hibernation made me believe that it's somehow related. But after
uninstalling this package nothing really changed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: kop3224 F...m pulseaudio
/dev/snd/controlC0: kop3224 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 26 12:17:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Встроенное аудио - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after
a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+subscriptions

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

[Desktop-packages] [Bug 1808344] [NEW] Various bugs printing pdf files

2018-12-13 Thread John Skottis

Public bug reported:

I want to report multiple issues encountered so far on Ubuntu 18.10
regarding printing PDF files.

My configuration:
- Computer: Dell XPS 15 9530
- OS: Ubuntu 18.10
- Printer: Samsung M2825ND Xpress Mono Laser Printer
- PDF Readers Tested: Various (Evince, Foxit, Okular)
- PDF Creator Tested: Word, LibreOffice, GhostScript, PDFTex, Acrobat PDFMaker, 
...
- PDF Sizes Tested: Various
- PDF Versions Tested: Various


Issues:
- Printing 1 page per physical page encounter a lot problems while printing 2 
pages per physical page produces issues less often
- Sometimes playing around with print setting (such as scaling, centering) 
solves the issue sometimes it creates it and sometimes does nothing 
- Printing calc file directly from LibreOffice is not possible

Error:
- PCL-6 error (don't remember the exact code right now but can provide it if 
needed)

Notes:
- My guess is that this is an error related to the printer drivers but since I 
don't have another printer to test on can't verify.
- Another guess is that the PDF produces PDF that use feature that are not 
properly handled on linux
- Turning Markdown text to PDF using PDFlatex causes a printing error whereas 
turning the same Markdown to html and printing through Chrome causes no issue
- If you need more logs please instruct me what I need to to help

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: cups 2.2.8-5ubuntu1.1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 13 13:35:13 2018
InstallationDate: Installed on 2018-09-21 (82 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180920)
Lpstat:
 device for M262x-282x: 
usb://Samsung/M262x%20282x%20Series?serial=ZD2JBJCF6000LMA
 device for MG3500-series: usb://Canon/MG3500%20series?serial=68152B=1
MachineType: Dell Inc. XPS 15 9530
Papersize: a4
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/M262x-282x.ppd', 
'/etc/cups/ppd/MG3500-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/M262x-282x.ppd: Permission denied
 grep: /etc/cups/ppd/MG3500-series.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=41f390ce-33d0-4b6a-96a1-fef284448f69 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/29/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: XPS 15 9530
dmi.board.vendor: Dell Inc.
dmi.board.version: A10
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd01/29/2018:svnDellInc.:pnXPS159530:pvrA10:rvnDellInc.:rnXPS159530:rvrA10:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: XPS 15 9530
dmi.product.sku: XPS 15 9530
dmi.product.version: A10
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug cosmic wayland-session

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

Title:
  Various bugs printing pdf files

Status in cups package in Ubuntu:
  New

Bug description:
  I want to report multiple issues encountered so far on Ubuntu 18.10
  regarding printing PDF files.

  My configuration:
  - Computer: Dell XPS 15 9530
  - OS: Ubuntu 18.10
  - Printer: Samsung M2825ND Xpress Mono Laser Printer
  - PDF Readers Tested: Various (Evince, Foxit, Okular)
  - PDF Creator Tested: Word, LibreOffice, GhostScript, PDFTex, Acrobat 
PDFMaker, ...
  - PDF Sizes Tested: Various
  - PDF Versions Tested: Various

  
  Issues:
  - Printing 1 page per physical page encounter a lot problems while printing 2 
pages per physical page produces issues less often
  - Sometimes playing around with print setting (such as scaling, centering) 
solves the issue sometimes it creates it and sometimes does nothing 
  - Printing calc file directly from LibreOffice is not possible

  Error:
  - PCL-6 error (don't remember the exact code right now but can provide it if 
needed)

  Notes:
  - My guess is that this is an error related to the printer drivers but since 
I don't have another printer to test on can't verify.
  - Another guess is that the PDF produces PDF that use feature that are not 
properly handled on linux
  - Turning Markdown text to PDF using PDFlatex causes a printing error whereas 
turning the same Markdown to html and printing through Chrome causes no issue
  - If you need more logs please instruct me what I need to to help

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: cups 2.2.8-5ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date:

[Desktop-packages] [Bug 1807744] Re: Print to File writes to incorrect file

2018-12-13 Thread KarlRelton

Submitted upstream:
https://bugs.documentfoundation.org/show_bug.cgi?id=122075

** Bug watch added: Document Foundation Bugzilla #122075
   https://bugs.documentfoundation.org/show_bug.cgi?id=122075

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

Title:
  Print to File writes to incorrect file

Status in libreoffice package in Ubuntu:
  New

Bug description:
  This bug only occurs when using the GTK3 dialogues (libreoffice-gtk3
  installed).

  Under certain conditions print to file over-writes an existing pdf
  file in the chosen folder which doesn't match the name chosen by the
  user (and without any warning or confirmation dialog).

  Steps to reproduce are:
  1) Create an empty directory (folder)
  2) Put in directory a dummy pdf (e.g. touch sample.pdf)
  3) Open libreoffice and create a writer document with a few words
  4) Save the libreoffice document to the directory as a regular writer doc 
(e.g. 'test.odt')
  5) Do 'File -> Print' and choose 'Print to File'
  6) In the (gtk3) File-chooser dialog:
6a) navigate to the folder created in step 2
6b) select 'Any Type' in the 'types of file shown' selector
6c) click on the file name 'test.odt'
6d) in the 'Name' text field, then edit the name from 'test.odt' to 
'test_2.pdf'
6e) then press 'Enter' (or click on 'Select')
  7) Observe that in the folder there is no file 'test_2.pdf'. However the 
dummy file 'sample.pdf' has been over-written and contains the pdf that 
resulted from the 'print to file' operation

  -->What should of happened is that the file 'test_2.pdf' should have
  been created as a pdf of the writer document.

  --
  Some notes:

  - Occurs in Libreoffice 6.1.2.1 (Build ID: 1:6.1.2-0ubuntu1.1) and older 
versions
  - Only occurs using the gtk3 file browser. Native libreoffice is okay (not 
tested old gtk2 code)
  - Only occurs if you first click on 'Any Type'. If you simply type a file 
name without first going to 'Any Type' it doesn't manifest the bug
  - Only occurs if the file name you type has the '.pdf' extension. If you do a 
name without it, then it doesn't manifest the bug

  lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

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

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

[Desktop-packages] [Bug 1799430] Re: Icon dock visible on lock screen

2018-12-13 Thread R_volkmann

Fresh 18.10 install, everything updated. Happens quite often, but not
always (30% ?).

I have installed following extra extensions: Unite, Caffeine.
Nvidia Graphics driver is installed.

It looks exactly the same as in @korg's photos, including previews. Apps can be 
started by clicking. 
I'm totally with @jleni's comment (#14), Imho, this is quite a huge security 
issue.

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

Title:
  Icon dock visible on lock screen

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When locking the machine with alt-L the icon dock is still visible.

  After Login, the dock does not get adjusted to the top menu.

  In rare cases, the dock does not respond any more. This requires a
  reboot of the machine

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: mutter 3.30.1-1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 23 12:59:27 2018
  InstallationDate: Installed on 2018-04-30 (176 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

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

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

[Desktop-packages] [Bug 586313] Re: Does not save/remember columns in search results

Upstream bug showing "RESOLVED FIXED" on 2016-11-24
Tested ok with Ubuntu 18.04 and nautilus 3.26.4
Marking "Fix Released" to close

** Changed in: nautilus (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Does not save/remember columns in search results

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: nautilus

  Nautilus does not remember/save which columns to show in a search results 
window. To reproduce:
  Do a search, choose View->Columns and choose e.g. Location. Location is shown 
in the search results. Choose View->Columns again and you will see Location 
unchecked. Either way, close the search windows and open a new one; columns are 
reset to defaults.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: nautilus 1:2.30.1-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  Architecture: i386
  Date: Thu May 27 13:32:04 2010
  ProcEnviron:
   LANG=de_DE.utf8
   SHELL=/bin/bash
  SourcePackage: nautilus

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

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

[Desktop-packages] [Bug 680771] Re: Cannot determine file location after search in Nautilus

Upstream bug showing "RESOLVED FIXED" on 2013-06-21
Search now uses list view to display file and path
Tested ok Ubuntu 18.04 and nautilus 3.26.4
Marking "Fix Released" to close

** Changed in: nautilus (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: hundredpapercuts
   Status: Triaged => Fix Released

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

Title:
  Cannot determine file location after search in Nautilus

Status in One Hundred Papercuts:
  Fix Released
Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  When searching for a file in Nautilus and then right-click to view
  Properties to determine the location, the full path to the file is
  obscured by the size of the Properties window. The Properties window
  cannot be sized, neither can the file path text be scrolled to the
  left to reveal the full path.

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

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

[Desktop-packages] [Bug 302977] Re: Create folder with correct name, instead of rename

Upstream bug showing "RESOLVED FIXED" on 2016-09-06
Tested ok with Ubuntu 18.04 and nautilus 3.26.4
Marking "Fix Released" to close

** Changed in: nautilus (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Create folder with correct name, instead of rename

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: nautilus

  When creating a new folder, nautilus creates a folder named "untitled 
folder", and then rename it.
  I have access to a FTP server where I can upload files, but can't delete or 
rename them. With nautilus, I can only create the folder named "untitled 
folder", renaming it or trying to create another folder fails. The only way I 
can create a folder with another name is to create the folder in a regular 
place, and then copy it.

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

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

[Desktop-packages] [Bug 1258305] Re: Duplicate results of "Search files" should show corresponding folder somehow

Upstream bug showing "RESOLVED FIXED" on 2016-02-10
Search now uses list view to display file and path
Tested ok with Ubuntu 18.04 and nautilus 3.26.4
Closing by marking "Fix Released"

** Changed in: nautilus (Ubuntu)
   Status: New => Fix Released

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

Title:
  Duplicate results of "Search files" should show corresponding folder
  somehow

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  The new search functionality of Nautilus by ad-hoc searching files when you 
start typing is loved by some and hated by others - I don't want to discuss 
this here.
  But the new search method lacks an important feature: it is not possible to 
distinguish two files (or folders) that are in different folders.
  Let me give an example.
  Create a new folder "test123" in your $HOME directory. Create another 
"test123" in "Downloads".
  Now navigate to your $HOME dir and start typing "test". Immediately nNautilus 
shows you the two entries "test123" (and maybe others if you have files/folders 
with similar names).
  But it is not distinguishable which of the two folders is "~/test123" and 
which is "~/Downloads/test123".

  Possible solution: Nautilus should show the folder containing this
  item as tooltip of the item.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu2.1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Dec  5 21:03:25 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'1210x705+1562+222'"
  InstallationDate: Installed on 2013-11-27 (8 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1277811] Re: Nautilus Breadcrumb Vibrate (move right and left fastly) on Hover

Upstream bug showing "RESOLVED FIXED" on 2017-08-29
Could not reproduce on Ubuntu 18.04 so closing by marking "Fix Released"

** Changed in: nautilus (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Nautilus Breadcrumb Vibrate (move right and left fastly) on Hover

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  A. System Description
  Description:  Ubuntu 13.10
  Release:  13.10
  nautilus:
Installed: 1:3.8.2-0ubuntu2.2
Candidate: 1:3.8.2-0ubuntu2.2
Version table:
   *** 1:3.8.2-0ubuntu2.2 0
  500 http://archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.8.2-0ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

  B. Bug
  1. Reproduce
  - Open nautilus
  - Go to a deep directory structure (location which produce long address)
  - Move the mouse to the button with left arrow on breadcrumb (to navigate up 
level location)
  NOTE : Just hover on it, not clicking.
  - If you're lucky, the breadcrumb will display between previous (part which 
is hidden on the left) and current display. 

  2. What you expected to happen
  - Nothing happened

  3. What happened instead
  - It is vibrating annoyingly makes difficult to navigate.

  4. Factor
  - I think this is related to the length of location address and nautilus 
width. A correct combination can produce this.

  Will add the picture (maybe hard to get, its moving though), when it
  happened again.

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

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

[Desktop-packages] [Bug 1808323] [NEW] gfg

2018-12-13 Thread Denis Serenko

Public bug reported:

gfg

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Dec 13 14:09:43 2018
DistUpgraded: 2018-12-12 20:39:45,935 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Wrestler [Radeon HD 7340] [104d:90ad]
InstallationDate: Installed on 2016-04-24 (963 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: Sony Corporation SVE1112M1EW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=40da7131-b99a-4e5b-9c5e-81ba4975e74c ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-12-12 (0 days ago)
dmi.bios.date: 08/22/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R0120D8
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0120D8:bd08/22/2012:svnSonyCorporation:pnSVE1112M1EW:pvrC60B8BEP:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: SVE1112M1EW
dmi.product.version: C60B8BEP
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~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: Wed Dec 12 18:07:04 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.8
xserver.video_driver: radeon

** 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/1808323

Title:
  gfg

Status in xorg package in Ubuntu:
  New

Bug description:
  gfg

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Dec 13 14:09:43 2018
  DistUpgraded: 2018-12-12 20:39:45,935 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Wrestler [Radeon HD 7340] [104d:90ad]
  InstallationDate: Installed on 2016-04-24 (963 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Sony Corporation SVE1112M1EW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=40da7131-b99a-4e5b-9c5e-81ba4975e74c ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-12-12 (0 days ago)
  dmi.bios.date: 08/22/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0120D8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0120D8:bd08/22/2012:svnSonyCorporation:pnSVE1112M1EW:pvrC60B8BEP:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVE1112M1EW
  dmi.product.version:

[Desktop-packages] [Bug 1642965] Comment bridged from LTC Bugzilla

2018-12-13 Thread bugproxy

--- Comment From jac...@de.ibm.com 2018-12-13 06:13 EDT---
And the next version comes in:

Package: firefox
Status: install ok installed
Priority: optional
Section: web
Installed-Size: 168434
Maintainer: Ubuntu Mozilla Team 
Architecture: s390x
Version: 64.0+build3-0ubuntu0.16.04.1
Replaces: kubuntu-firefox-installer
Provides: gnome-www-browser, iceweasel, www-browser
Depends: lsb-release, libatk1.0-0 (>= 1.12.4), libc6 (>= 2.18), 
libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.10.0), libdbus-1-3 (>= 1.9.14), 
libdbus-glib-1-2 (>= 0.78), libffi6 (>= 3.0.4), libfontconfig1 (>= 2.11.94), 
libfreetype6 (>= 2.3.5), libgcc1 (>= 1:4.2), libgdk-pixbuf2.0-0 (>= 2.22.0), 
libglib2.0-0 (>= 2.30.0), libgtk-3-0 (>= 3.4), libpango-1.0-0 (>= 1.22.0), 
libpangocairo-1.0-0 (>= 1.14.0), libstartup-notification0 (>= 0.8), libstdc++6 
(>= 4.6), libx11-6, libx11-xcb1, libxcb-shm0, libxcb1, libxext6, libxrender1, 
libxt6
Recommends: xul-ext-ubufox, libcanberra0, libdbusmenu-glib4, libdbusmenu-gtk3-4
Suggests: fonts-lyx
Conffiles:
/etc/apparmor.d/usr.bin.firefox 2c5033f33fe1c0e5b9f27ecbbb6ff74f
/etc/apport/blacklist.d/firefox d41d8cd98f00b204e9800998ecf8427e
/etc/apport/native-origins.d/firefox 7c26b75c7c2b715c89cc6d85338252a4
/etc/firefox/syspref.js 09e457e65435a1a043521f2bd19cd2a1
/etc/firefox/firefox.js a49602f3ce5871da8a5c58579411e971 obsolete
Description: Safe and easy web browser from Mozilla
Firefox delivers safe, easy web browsing. A familiar user interface,
enhanced security features including protection from online identity theft,
and integrated search let you get the most out of the web.
Xul-Appid: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}

firefox:
Installed: 64.0+build3-0ubuntu0.16.04.1
Candidate: 64.0+build3-0ubuntu0.16.04.1
Version table:
*** 64.0+build3-0ubuntu0.16.04.1 500
500 http://de.ports.ubuntu.com/ubuntu-ports xenial-updates/main s390x Packages
500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main s390x Packages

But alas, still crashing:

Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
NS_ABORT_OOM (aSize=) at 
/build/firefox-cC5WSS/firefox-64.0+build3/xpcom/base/nsDebugImpl.cpp:628
628 /build/firefox-cC5WSS/firefox-64.0+build3/xpcom/base/nsDebugImpl.cpp: 
No such file or directory.
(gdb) info stack
#0  NS_ABORT_OOM (aSize=) at 
/build/firefox-cC5WSS/firefox-64.0+build3/xpcom/base/nsDebugImpl.cpp:628
#1  0x03fff41bf24c in nsTSubstring::AllocFailed (aLength=, this=0x3ffdb30)
at /build/firefox-cC5WSS/firefox-64.0+build3/xpcom/string/nsTSubstring.h:1172
#2  nsTString::ReplaceSubstring (this=this@entry=0x3ffdb30, 
aTarget=..., aNewValue=...)
at 
/build/firefox-cC5WSS/firefox-64.0+build3/xpcom/string/nsTStringObsolete.cpp:275
#3  0x03fff41bf2f6 in nsTString::ReplaceSubstring 
(this=this@entry=0x3ffdb30,
aTarget=aTarget@entry=0x3fff831482e ";", 
aNewValue=aNewValue@entry=0x3fff805c8e0 "%3b")
at 
/build/firefox-cC5WSS/firefox-64.0+build3/xpcom/string/nsTStringObsolete.cpp:252
#4  0x03fff42bda3c in net_GetURLSpecFromActualFile (aFile=, 
result=...)
at /build/firefox-cC5WSS/firefox-64.0+build3/netwerk/base/nsURLHelperUnix.cpp:45
#5  0x03fff42829ea in mozilla::FileLocation::GetURIString 
(this=this@entry=0x3fffd6ed5f0, aResult=...)
at /build/firefox-cC5WSS/firefox-64.0+build3/xpcom/build/FileLocation.cpp:118
#6  0x03fff49c2988 in nsZipArchive::OpenArchive 
(this=this@entry=0x3fffd6fa000, aZipHandle=0x3fffd6ed5e0, aFd=aFd@entry=0x0)
at /build/firefox-cC5WSS/firefox-64.0+build3/modules/libjar/nsZipArchive.cpp:359
#7  0x03fff49c2ac6 in nsZipArchive::OpenArchive 
(this=this@entry=0x3fffd6fa000, aFile=)
at /build/firefox-cC5WSS/firefox-64.0+build3/modules/libjar/nsZipArchive.cpp:380
#8  0x03fff428626a in mozilla::Omnijar::InitOne (aPath=aPath@entry=0x0, 
aType=aType@entry=mozilla::Omnijar::GRE)
at /build/firefox-cC5WSS/firefox-64.0+build3/xpcom/build/Omnijar.cpp:87
#9  0x03fff4287c3a in mozilla::Omnijar::Init (aAppPath=0x0, aGrePath=0x0)
at /build/firefox-cC5WSS/firefox-64.0+build3/xpcom/build/Omnijar.cpp:111
#10 NS_InitXPCOM2 (aResult=0x3fffd685a38, aBinDirectory=, 
aAppFileLocationProvider=)
at /build/firefox-cC5WSS/firefox-64.0+build3/xpcom/build/XPCOMInit.cpp:612
#11 0x03fff428800c in NS_InitXPCOM2 (aResult=aResult@entry=0x3fffd685a38, 
aBinDirectory=,
aAppFileLocationProvider=) at 
/build/firefox-cC5WSS/firefox-64.0+build3/xpcom/build/XPCOMInit.cpp:748
#12 0x03fff70b6808 in ScopedXPCOMStartup::Initialize (this=0x3fffd685a38)
at /build/firefox-cC5WSS/firefox-64.0+build3/toolkit/xre/nsAppRunner.cpp:1484
#13 0x03fff70be23e in XREMain::XRE_main (this=this@entry=0x3ffe278, 
argc=argc@entry=1, argv=argv@entry=0x3fff7a8,
aConfig=...) at 
/build/firefox-cC5WSS/firefox-64.0+build3/toolkit/xre/nsAppRunner.cpp:4918
#14 0x03fff70be5ca in XRE_main (argc=, argv=0x3fff7a8, 
aConfig=...)
at /build/firefox-cC5WSS/firefox-64.0+build3/toolkit/xre/nsAppRunner.cpp:5014
#15 0x00016cb8 in do_main (argc=, argv=0x3fff7a8,

[Desktop-packages] [Bug 386953] Re: Focus is moved from desktop to window

Upstream bug showing "RESOLVED FIXED" on 2012-09-05
Tested ok Ubuntu 18.04 and nautilus 3.26.4
Marking "Fix Released" to close


** Changed in: nautilus (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Focus is moved from desktop to window

Status in One Hundred Papercuts:
  Invalid
Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Focus (aka the selection) is moved from desktop to a open folder
  window.

  To reproduce:
  - Create a file on your desktop
  - Open a Nautilus window (like; Places -> Home folder)
  - Select the new file on your desktop
  - Hold Shift down and press the delete key
  - In the dialogbox, press Cancel

  The focus is now moved from the desktop to the folder window. Which
  means if you press delete again (without shift), you will delete the
  first folder in the window! The same issue does not occure when the
  folder window is minimized.

  (Sorry for the vage description in the summary)


  //Mads Rosendahl (MadsRH)
  madsrh(a)gmail.com

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

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

[Desktop-packages] [Bug 363319] Re: Wait a couple seconds before switching tabs

Upstream bug showing "RESOLVED FIXED" on 2012-10-22
Tested ok with Ubuntu 18.04 and nautilus 3.26.4
Marking "Fix Released" to close


** Changed in: nautilus (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Wait a couple seconds before switching tabs

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: nautilus

  I often use tabs to move files from one folder to another. I open the
  first tab and drag the file to the second tab. Unfortunately, it also
  switches tabs: it opens the second tab, and forces me to switch back
  to the first manually.

  So please, make it that if I drag a file to a tab, I have to hover the
  mouse over the tab for a couple seconds before switching tabs: don't
  do it immediately.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia
  Package: nautilus 1:2.26.2-0ubuntu1
  ProcEnviron:
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  Uname: Linux 2.6.28-11-generic i686

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

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

[Desktop-packages] [Bug 298425] Re: gtk fileselector allow file bookmarks but nautilus doesn't use those correctly

Upstream bug showing "RESOLVED FIXED" on 2013-05-22
Tested ok in Ubuntu 18.04 and nautilus 3.26.4
Marking "Fix Released" to close

** Changed in: nautilus (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  gtk fileselector allow file bookmarks but nautilus doesn't use those
  correctly

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: nautilus

  When running gtk apps like GIMP, and choose File->Open, filechooser
  dialog pops up, drag a file lke "picture.png" into the "Places" panel.
  Now each time when u click this file in the "places" panel, will go to
  the directory where it is held and highlight that file.

  open nautilus now, and that file will also appear in the 'places' panel. 
However clicking it produces error 
  "not a directory" and does not go to that directory where file is held.

  Not consistent and confusing to user. Whats the point of having that
  item in 'nautilus' if cant acess it.

  somtimes also the file in 'places panel' is rendered as a folder icon
  too.

  ubuntu 8.10
  nautlius 1:2.24.1-0ubuntu1

  [screenshot attached]

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

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

[Desktop-packages] [Bug 362112] Re: Nautilus location bar buttons take us backwards in history, but not forwards

Upstream bug showing "RESOLVED FIXED" on 2017-08-18
Tested ok in Ubuntu 18.04 and nautilus 3.26.4
Marking as "Fix Released" to close

** Changed in: nautilus (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Nautilus location bar buttons take us backwards in history, but not
  forwards

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: nautilus

  Using Nautilus in "browser mode":

  1. Gnome Places --> Home Folder (for someuser).  This brings up a new 
Nautilus window.  History menus: Back:  .  Fwd: 
  2. Open the Music directory.  Back:  someuser.  Fwd: 
  3. Open a subdirectory of Music, e.g. Beach Boys.  Back: Music, someuser.  
Fwd: 
  4. Click the Location Bar Button "someuser".  Back: .  Fwd: Music, 
Beach Boys.
  5. Click on Location Bar Button "Beach Boys".  Back: someuser.  Fwd: 

  BUG: It seems inconsistent and strange that clicking on the location
  bar buttons that represent the directory path would take me backwards
  in the history.  It is then inconsistent and strange that clicking on
  the buttons that are ahead of the current button do NOT take me
  forward in the path.

  That is, when I click them for directories that are parents, grand-
  parents, etc. of the current/working directory, then I am actually
  somehow/someway navigating in the navigation history stacks.  But when
  I click on a child, grand-child, etc. in the location bar buttons,
  then I am actually starting a new path (clearing the fwd stack).

  Perhaps this is by design, but if so, then I think the rules for these
  buttons should be clearly stated in a design document.  Each
  step/behavior should be able to be conveyed (even if it is non-
  deterministic) in the Gnome Nautilus Help.

  
  ( Bonus Question: What happens after step 5 when you click on "Music" in the 
location bar buttons? )

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/bin/nautilus
  Package: nautilus 1:2.24.1-0ubuntu2
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  Uname: Linux 2.6.27-11-generic x86_64

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

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

[Desktop-packages] [Bug 236207] Re: some icons don't follow zoom settings

Upstream bug showing "RESOLVED FIXED" on 2016-12-11
Tested ok Ubuntu 18.04 and nautilus 3.26.4
Closing by marking "Fix Released"


** Changed in: nautilus (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  some icons don't follow zoom settings

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  This is a fresh install of Ubuntu 8.10 on a Dell Latitude D830. I am
  using one of the default included themes, Mist, however this problem
  exists for any default them I select.

  As you  can see from the included screen shoot, I have the icons sizes
  configured to show at 75% and the icons for the web link and the CHM
  file don't appear to follow the sizing suggestion. The only thing I
  have done after the install is change the icon zoom preference.

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

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

[Desktop-packages] [Bug 1662688] Re: Have drag and drop support for the dock

2018-12-13 Thread fcole90

I think a temporary fix could be for it to work like Dash to Panel,
which if hovered while dragging, activates the shell overview and hence
allows to drop on the chose window.

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

Title:
  Have drag and drop support for the dock

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  It would be useful if the dock in the AO supported drag and drop, that
  is so that one may drag a file to one of its docked applications and
  it may open it. Although this wouldn't necessarily be so useful for
  standard installs, users of extensions such as Dash to Dock would find
  this highly useful. So it would be nice if this feature were at least
  supported so that they could implement it as such extensions are
  becoming more and more popular day by day.

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

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

[Desktop-packages] [Bug 270676] Re: when opening a new tab, always switch to it