date:20190122

Those repeated messages are probably just a consequence of still having
debugging turned on. Maybe now is a good time to try with debugging
turned off in /etc/gdm3/custom.conf so as to generate smaller logs.

> Whenever I try to get the computer to recognize the CD image and to
boot from it, I have to spam "1" and "Enter" over and over and sometimes
it works. Have you run into this issue before?

No I haven't ever heard of that. Usually on a Macbook you just hold the
Option key at startup to select a boot device. Maybe you are seeing a
quirk of the old model or maybe you are experiencing a hardware fault.

In fact, if you can't get any Linux to work reliably then hardware
faults start to become a more realistic explanation. But I don't see any
solid evidence of a hardware fault yet.

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

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]

Status in gdm3 package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Ubuntu 18.04.1, on its first boot, the
  computer hung at a purple screen.  No login prompt was ever displayed.
  After holding the power button, the computer boot into Ubuntu without
  difficulty.  I applied the workaround described in bug 1727356,
  uncommenting WaylandEnable=False and rebooted the machine, but it
  again hung at the purple screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 10:59:26 2019
  InstallationDate: Installed on 2019-01-11 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441

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

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

[Desktop-packages] [Bug 1812359] Re: Login screen not appearing in bionic [SSD Intel Atom]

2019-01-22 Thread d a i s y

At last, I did switching of display manager from gdm to lightdm but
after login, nothing appeared on screen, only Ubuntu 18.04 wallpaper.

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

Title:
  Login screen not appearing in bionic [SSD Intel Atom]

Status in mutter package in Ubuntu:
  New

Bug description:
  I've tried the solution mentioned here
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/comments/72
  but it did not solve my issue.

  $ dpkg -s mutter
  Package: mutter
  Status: install ok installed
  Priority: optional
  Section: x11
  Installed-Size: 101
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 3.28.3-2~ubuntu18.04.2
  Provides: x-window-manager
  Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), 
libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 
3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 
3.21.4), zenity
  Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs
  Description: lightweight GTK+ window manager
   Mutter is a small window manager, using GTK+ and Clutter to do
   everything.
   .
   Mutter is the clutter-based evolution of Metacity, which, as the
   author says, is a "Boring window manager for the adult in you. Many
   window managers are like Marshmallow Froot Loops; Metacity is like
   Cheerios."
   .
   This package contains the core binaries.
  Original-Maintainer: Debian GNOME Maintainers 


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.3-2~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 18 15:02:22 2019
  InstallationDate: Installed on 2019-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 367341] Re: Still unable to connect to 1 particular POP server

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

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

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

Title:
  Still unable to connect to 1 particular POP server

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Binary package hint: thunderbird

  For years I have been reporting this same bug and I see, with this
  fresh install of Thunderbird on my Ubuntu machine, that it is STILL
  NOT CORRECTED.  Regrettably I don't have the prior thread for this
  complaint so I'll have to start "fresh".

  I have 5 e-mail accounts that are POP accessible. 1 at yahoo, 1 at sstar.com, 
1 at comcast.net and 2 at sursum-corda.com.
  Those on the sursum-corda.com server (which I operate) are inaccesible via 
Thunderbird.  Any attempt to connect and Thunderbird sends "CAPA" and posts 
this pop-up message: "Sending of username did not succeed. Mail server 10.0.0.3 
responded: CAPA".  Precisely what it has always done.

  Here is the log snippet from the POP server:
  ===cut
  * 08:17:07 (9) Incoming connection from 10.0.0.20 on 04/26/09.
  ] 08:17:07 (9) +OK Internet Rex POP3 server ready <3250.1240755427@mailserv>
  = 08:17:07 (9) AUTH  "=" 
is an incoming command from the client
  ] 08:17:07 (9) -ERR Unrecognised command.    "]" is a reply from 
the server  to the client
  = 08:17:07 (9) CAPA
  ] 08:17:07 (9) CAPA
  = 08:17:16 (9) USER marc
  ] 08:17:16 (9) +OK Need password.
  ! 08:18:17 (9) Connection closed: timeout receiving command.<<60 
seconds of waiting for Thunderbird
  ===cut

  At one time, one of the coders of Thunderbird said that he thought he had 
removed or altered the log-in algorithms 
  to correct for this anomaly; but apparently he had not, and the problem 
continues to this date.  Note that I am able to access that pop account from 
ANY other e-mail client, including: The Bat!, Outlook Express, Outlook, 
mail2web.com, PMMail/2, PMMail Pro, etc.

  It should be noted that SENDING mail from Thunderbird via the SMTP server at 
sursum-corda.com IS successful:
  ===cut=
  * 08:33:14 (9) Inbound connection from 10.0.0.20 at 04/26/09.
  ] 08:33:15 (9) 220 sursum-corda.com Internet Rex ESMTP daemon at your service.
  # 08:33:16 (9) EHLO [10.0.0.20]   
 LOG KEYS: "*" = information
  ] 08:33:16 (9) 250- sursum-corda.com Hello [10.0.0.20]
 "]" = outbound reply
  ] 08:33:16 (9) 250-8BITMIME   
  "#"=inbound command 
  ] 08:33:16 (9) 250-SIZE
  ] 08:33:16 (9) 250-AUTH CRAM-MD5 LOGIN
  ] 08:33:16 (9) 250 HELP
  # 08:33:25 (9) AUTH CRAM-MD5
   #   (line suppressed)
  ] 08:33:25 (9) 334 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
  ] 08:33:25 (9) 235 Authentication accepted.
  ===cut=

  Can someone please take up this coding issue and get it finally
  corrected?

  ProblemType: Bug
  Architecture: i386
  Dependencies:
   
  DistroRelease: Ubuntu 8.10
  NonfreeKernelModules: nvidia
  Package: mozilla-thunderbird None [modified: 
/var/lib/dpkg/info/mozilla-thunderbird.list]
  PackageArchitecture: all
  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: thunderbird
  Uname: Linux 2.6.27-14-generic i686

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

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

[Desktop-packages] [Bug 194191] Re: Cannot drag and drop bookmark to desktop

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

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

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

Title:
  Cannot drag and drop bookmark to desktop

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: mozilla-firefox

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=8.04
  DISTRIB_CODENAME=hardy
  DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

  Firefox 3.0~b3+nobinonly-0ubuntu2

  I'm having trouble dragging and dropping some bookmarks to the
  desktop. I bookmarked the following url:
  http://www.imdb.com/title/tt0118889/ and then tried to drag it to the
  desktop and expected to see a link (represented by a globe with and
  arrow and the name of the title of the bookmark) I get an error:

  Error while copying.
  There was an error getting information about "
  ".
  HTTP Error: Method Not Allowed

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

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

[Desktop-packages] [Bug 1264899] Re: typing anything into terminal causes traceback error

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

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

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

Title:
  typing anything into terminal causes traceback error

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  when typing anything into a terminal, I get the following error:$ asdf
  Traceback (most recent call last):
File "/usr/lib/python3.3/site.py", line 76, in 
  import re
File "/usr/lib/python3.3/re.py", line 122, in 
  import sre_compile
File "/usr/lib/python3.3/sre_compile.py", line 14, in 
  import sre_parse
File "/usr/lib/python3.3/sre_parse.py", line 17, in 
  from sre_constants import *
  TypeError: source code string cannot contain null bytes

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

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

[Desktop-packages] [Bug 1804486] Re: firefox 63.0 out of bounds read/or wrong firewall rule

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

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

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

Title:
  firefox 63.0 out of bounds read/or wrong firewall rule

Status in firefox package in Ubuntu:
  Expired

Bug description:
  On using the application knime the download was intercepted by firewall rules 
of the university network with the following error:
  File-Text_Mozilla-Firefox-HTTP-Index-Format-File-Out-Of-Bounds-Read

  This may be associated by
  https://www.mozilla.org/en-US/security/advisories/mfsa2017-10/#CVE-2017-5446

  Was the mitigation ported/used in firefox 63.0 ?
  Are security updates for common used programs (firefox 63.3 is current 
version) not supported on LTS anymore?

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

-- 
Mailing list: https://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 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed [Apple Macbook 2, 1 - Intel GMA 950]

2019-01-22 Thread Alexander A Theiler

Hey Daniel,

The other thing I noticed in the the boot logs are a seemingly futile
loop:

Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/usr/share/gdm/greeter/autostart'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/var/lib/gdm3/.config/autostart'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/usr/share/gdm/greeter/gnome/autostart'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/usr/local/share/gnome/autostart'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/usr/share/gnome/autostart'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/etc/xdg/autostart'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/var/lib/gdm3/.local/share/applications'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/usr/share/gdm/greeter/applications'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/usr/local/share/applications'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/usr/share/applications'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: found in XDG dirs:
'/etc/xdg/autostart/org.gnome.SettingsDaemon.Housekeeping.desktop'


This appears first at 11:38:36 in the first boot log, and then repeats
over and over and over until the machine turns off.  The same loop
appears in longhangprevboot2.txt and starts at 12:21:55.  What is the
machine trying to do here?  I suspect that this is what's happening in
the background when the computer hangs, and it may even describe why
it does not record the whole boot sequence for the 20 minutes after it
hangs.  Thoughts?


I have not used Ubuntu 16.04, nor Lubuntu 18.04.1.  I'll download
Lubuntu and see how that works out.  But, I am a little concerned
about getting it to install correctly.  Whenever I try to get the
computer to recognize the CD image and to boot from it, I have to spam
"1" and "Enter" over and over and sometimes it works.  Have you run
into this issue before?


Alex


On Tue, Jan 22, 2019 at 8:05 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> You're right - those logs are apparently from short boots.
>
> longhangprevboot.txt lasted less than 2 minutes and only 2 seconds
> between GLSL errors and the machine beginning to shutdown.
>
> longhangprevboot2.txt lasted 2 minutes and again was only 4 seconds
> between GLSL errors and the machine beginning shutting down.
>
> Maybe that's a hint at a bigger problem if the system clock is running
> slower than reality..?
>
> Do older releases like Ubuntu 16.04 work on it? How about Lubuntu
> 18.04.1?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1811599
>
> Title:
>   When booting, the computer hangs at a purple screen and no login
>   prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After a fresh install of Ubuntu 18.04.1, on its first boot, the
>   computer hung at a purple screen.  No login prompt was ever displayed.
>   After holding the power button, the computer boot into Ubuntu without
>   difficulty.  I applied the workaround described in bug 1727356,
>   uncommenting WaylandEnable=False and rebooted the machine, but it
>   again hung at the purple screen.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.28.3-0ubuntu18.04.3
>   ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
>   Uname: Linux 4.15.0-43-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Jan 13 10:59:26 2019
>   InstallationDate: Installed on 2019-01-11 (2 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gdm3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+subscriptions
>


-- 
Alexander A Theiler, MHS,

[Desktop-packages] [Bug 1812359] Re: Login screen not appearing in bionic

2019-01-22 Thread d a i s y

I am running Ubuntu on SSD. I've done fresh installation of Ubuntu downloaded 
from here: http://cdimage.ubuntu.com/bionic/daily-live/current/ but no change
and tried all the previous solution of commenting out WaylandEnable=false and 
installing haveged.

SSD information:
/dev/sda:

ATA device, with non-removable media
Model Number:   SMARTSTATION
Serial Number:  0208201520019   
Firmware Revision:  1.094.12
Transport:  Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, 
SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0


** Summary changed:

- Login screen not appearing in bionic
+ Login screen not appearing in bionic [SSD Intel Atom]

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

Title:
  Login screen not appearing in bionic [SSD Intel Atom]

Status in mutter package in Ubuntu:
  New

Bug description:
  I've tried the solution mentioned here
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/comments/72
  but it did not solve my issue.

  $ dpkg -s mutter
  Package: mutter
  Status: install ok installed
  Priority: optional
  Section: x11
  Installed-Size: 101
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 3.28.3-2~ubuntu18.04.2
  Provides: x-window-manager
  Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), 
libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 
3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 
3.21.4), zenity
  Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs
  Description: lightweight GTK+ window manager
   Mutter is a small window manager, using GTK+ and Clutter to do
   everything.
   .
   Mutter is the clutter-based evolution of Metacity, which, as the
   author says, is a "Boring window manager for the adult in you. Many
   window managers are like Marshmallow Froot Loops; Metacity is like
   Cheerios."
   .
   This package contains the core binaries.
  Original-Maintainer: Debian GNOME Maintainers 


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.3-2~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 18 15:02:22 2019
  InstallationDate: Installed on 2019-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1743976] Re: gnome-shell is wasting CPU repainting unchanging panels

Confirmed ubuntu-dock 0.9.1ubuntu18.04.3 no longer shows any
(additional) CPU penalty when a window is updating while touching or
under the dock.

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

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

Title:
  gnome-shell is wasting CPU repainting unchanging panels

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Bionic:
  Fix Committed

Bug description:
  gnome-shell is wasting CPU repainting an unchanging panel and dock.
  Every time an app window changes all visible actors including the
  panel get repainted. But the panels mostly doesn't change, so should
  be cached via offscreen-redirect instead.

  [ Impact ]

  Ubuntu dock repaints the dock when a window changes

  [ Test case ]

  - Maximize a window
  - Change its content, by acting on it
  - Monitor gnome-shell CPU usage, and it should be lower than using previous 
dock version

  [ Possible regression ]

  The dock isn't repainted properly or it could produce artifacts in
  some scenarios

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

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

[Desktop-packages] [Bug 1812948] Re: bug search

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

Title:
  bug search

Status in Ubuntu:
  Incomplete

Bug description:
  just did a search and these bugs came up.I'm not sure haw they
  work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .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: Tue Jan 22 19:38:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 18.03.00, 4.15.0-43-generic, x86_64: installed
   nvidia, 390.77, 4.15.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 620] [10de:0f01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 620] [3842:2625]
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
   Bus 002 Device 004: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
   Bus 002 Device 002: ID 062a: Creative Labs Optical mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=c599b74a-de09-473c-b0e9-39538d42a83d ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: N68C-GS FX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/31/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 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.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 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: Tue Jan 22 17:27:30 2019
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 062a:MOUSE, id 8
   inputDELL DELL USB Keyboard KEYBOARD, id 9
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

To manage notifications about

[Desktop-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

** Tags removed: artful

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Bionic:
  New
Status in pulseaudio source package in Cosmic:
  New
Status in pulseaudio source package in Disco:
  Confirmed

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

2019-01-22 Thread Dave Chiluk

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

** Also affects: pulseaudio (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: pulseaudio (Ubuntu Disco)
   Importance: Low
 Assignee: Dave Chiluk (chiluk)
   Status: Confirmed

** Also affects: pulseaudio (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

** Changed in: pulseaudio (Ubuntu Cosmic)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

** Changed in: pulseaudio (Ubuntu Bionic)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Bionic:
  New
Status in pulseaudio source package in Cosmic:
  New
Status in pulseaudio source package in Disco:
  Confirmed

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1812948] [NEW] bug search

2019-01-22 Thread Alistair

Public bug reported:

just did a search and these bugs came up.I'm not sure haw they work

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
.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: Tue Jan 22 19:38:51 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 fwts-efi-runtime-dkms, 18.03.00, 4.15.0-43-generic, x86_64: installed
 nvidia, 390.77, 4.15.0-43-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 620] [10de:0f01] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GF108 [GeForce GT 620] [3842:2625]
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
 Bus 002 Device 004: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
 Bus 002 Device 002: ID 062a: Creative Labs Optical mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=c599b74a-de09-473c-b0e9-39538d42a83d ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/31/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: N68C-GS FX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/31/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 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.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 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: Tue Jan 22 17:27:30 2019
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputHID 062a:MOUSE, id 8
 inputDELL DELL USB Keyboard KEYBOARD, id 9
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.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/1812948

Title:
  bug search

Status in xorg package in Ubuntu:
  New

Bug description:
  just did a search and these bugs came up.I'm not sure haw they
  work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .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:

[Desktop-packages] [Bug 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed [Apple Macbook 2, 1 - Intel GMA 950]

You're right - those logs are apparently from short boots.

longhangprevboot.txt lasted less than 2 minutes and only 2 seconds
between GLSL errors and the machine beginning to shutdown.

longhangprevboot2.txt lasted 2 minutes and again was only 4 seconds
between GLSL errors and the machine beginning shutting down.

Maybe that's a hint at a bigger problem if the system clock is running
slower than reality..?

Do older releases like Ubuntu 16.04 work on it? How about Lubuntu
18.04.1?

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

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]

Status in gdm3 package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Ubuntu 18.04.1, on its first boot, the
  computer hung at a purple screen.  No login prompt was ever displayed.
  After holding the power button, the computer boot into Ubuntu without
  difficulty.  I applied the workaround described in bug 1727356,
  uncommenting WaylandEnable=False and rebooted the machine, but it
  again hung at the purple screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 10:59:26 2019
  InstallationDate: Installed on 2019-01-11 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441

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

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

[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04

2019-01-22 Thread echoxxzz

Kodi definitely works with the latest versions of Lirc and the problem
is very easy to fix so stop downgrading your systems to an older version
of Lirc

The problem is Kodi defaults to looking for a Lirc socket at /dev/lircd
which doesn’t exist anymore. In Lirc > 0.9.0 the socket is now defined
within the /etc/lirc/lirc_options.conf file and defaults to
/var/run/lirc/lircd.

To get Kodi working with the latest versions of Lirc do one of the
following:

1. Modify the /etc/lirc/lirc_options.conf file and change the output variable 
to /dev/lircd. You’ll need
to restart the lircd service or reboot.

2. Start Kodi with the -l argument and manually specify the Lirc socket.

e.g: kodi -l /var/run/lirc/lircd

3. Modify the /lib/systemd/system/lircd.service to create a symlink from 
/dev/lircd to
/var/run/lirc/lircd each time the lircd.service or system is restarted:

e.g: Edit the file so it looks like the following.

[Service]
Type=simple
ExecStart=/usr/sbin/lircd –nodaemon
ExecStartPost=/bin/ln -sf /var/run/lirc/lircd /dev/lircd

Reboot

Lastly, and this maybe a problem specific to my setup, but I kept
getting repeating remote button presses the first time I started Kodi
after a reboot. Launching Kodi a second time and the problem was gone. I
found that disabling the lircd-uinput service fixed the problem and now
Kodi starts up properly and my remote works perfectly.

e.g: sudo systemctl disable lircd-uinput.service

What I still cannot get working is the lirc-setup app (which replaces
dpkg-reconfigure lirc). I’ve tried doing pip3 install
/usr/share/lirc/lirc-0.10.0.tar.gz suggested elsewhere but just more
errors. I don’t really need it as I can manually edit the conf files;
not to mention the defaults (using the devinput driver) worked with my
MCEUSB remote.

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

Title:
  lirc broken on 18.04

Status in lirc package in Ubuntu:
  Invalid

Bug description:
  Lirc 0.10.0-2 is never configured after installation. Manually running
  "dpkg-reconfigure lirc " also does not do anything. I also noticed
  that /usr/share/lirc/remotes is empty, which is where I had my config
  file for Ubuntu 16.04.

  This was an upgrade install from 16.04.
  Searching the web indicates others have this problem. Some have reverted to 
the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I 
have been unsuccessful so far.

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

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

[Desktop-packages] [Bug 1789758] Re: bluetooth headphones a2dp profile does not function after suspend, only HSP

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

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

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

Title:
  bluetooth headphones a2dp profile does not function after suspend,
  only HSP

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2) $ apt-cache policy bluez
  bluez:
Installed: 5.48-0ubuntu3.1
Candidate: 5.48-0ubuntu3.1
Version table:
   *** 5.48-0ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.48-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) bluetooth headphones stay working in a2dp mode even after suspend

  4) bluetooth headphones connect but no sound will come out of a2dp
  mode, only in HSP profile

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 29 18:07:26 2018
  InstallationDate: Installed on 2018-05-26 (95 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180525)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9e84ffd4-d629-4dcd-a6c4-6648d1a34665 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: RKPPT10H.86A.0041.2015.0316.1442
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D53427RKE
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G87971-406
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0041.2015.0316.1442:bd03/16/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-406:cvn:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 48:51:B7:07:93:F5  ACL MTU: 1021:5  SCO MTU: 96:5
DOWN 
RX bytes:5617087 acl:790 sco:22622 events:634625 errors:0
TX bytes:540631745 acl:632348 sco:22584 commands:537 errors:0

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

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

[Desktop-packages] [Bug 1812867] Re: sound from bluetooth device is like vintage when quiting the hibernate

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

Oh, actually this has already been reported in bug 1789758.

** This bug has been marked a duplicate of bug 1789758
   bluetooth headphones a2dp profile does not function after suspend, only HSP

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

Title:
  sound from bluetooth device is like vintage when quiting the hibernate

Status in Ubuntu Budgie:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi
  I've just noticed this today, with my laptop and my desktop, both under 
Ubuntu Budgie 18.10, all last updates installed if it can help you. Using a USB 
Bluetooth key for both

  After using my wireless speaker (JBL GO for more precision if it's
  needed) within Bluetooth, I lock my computer when I leave my office.
  then I unlock my computer when I'm back to.

  Wanna play some music on the said device. Then I start to play
  music... with somewhat vintage effect on the sound.

  I shutdown the device, start it up and same thing.

  To get a working properly BT, I have to

  - unplug and plug the USB BT key
  - middle click two time on the Bluetooth logo at the top, likely to disable / 
enable it

  and then it work like a charm.

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

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

[Desktop-packages] [Bug 1812914] Re: X diagnostics

Can you please describe what problem you are experiencing?

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

** Changed in: xorg-server (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/1812914

Title:
  X diagnostics

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  This bug is from X Diagnostics

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jan 22 21:42:20 2019
  DistUpgraded: 2019-01-15 00:39:12,441 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 
/ 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Mobility Radeon HD 5650 [104d:9071]
  InstallationDate: Installed on 2016-10-08 (836 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 064e:a213 Suyin Corp. 
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Sony Corporation VPCEC1S1E
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic 
root=UUID=7c6080a7-1a0e-4121-94f1-42cba8e7b69c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2019-01-14 (7 days ago)
  dmi.bios.date: 07/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0300Y8
  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:bvnAmericanMegatrendsInc.:bvrR0300Y8:bd07/20/2010:svnSonyCorporation:pnVPCEC1S1E:pvrC6050X6T:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEC1S1E
  dmi.product.sku: N/A
  dmi.product.version: C6050X6T
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Tue Jan 22 21:23:19 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.1-3ubuntu2.1
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1812867] Re: sound from bluetooth device is like vintage when quiting the hibernate

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

It sounds like your Bluetooth audio is resuming with profile HSP/HFP
(low quality audio).

Next time it happens please look at your audio settings and tell us what
the current profile is. It should be A2DP for higher quality, and not
HSP/HFP.

** Package changed: bluez (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  sound from bluetooth device is like vintage when quiting the hibernate

Status in Ubuntu Budgie:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi
  I've just noticed this today, with my laptop and my desktop, both under 
Ubuntu Budgie 18.10, all last updates installed if it can help you. Using a USB 
Bluetooth key for both

  After using my wireless speaker (JBL GO for more precision if it's
  needed) within Bluetooth, I lock my computer when I leave my office.
  then I unlock my computer when I'm back to.

  Wanna play some music on the said device. Then I start to play
  music... with somewhat vintage effect on the sound.

  I shutdown the device, start it up and same thing.

  To get a working properly BT, I have to

  - unplug and plug the USB BT key
  - middle click two time on the Bluetooth logo at the top, likely to disable / 
enable it

  and then it work like a charm.

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

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

[Desktop-packages] [Bug 1812865] Re: Extracting an archive by right-clicking and selecting "Extract here" results in many extracted files to be 0 bytes in size

** Tags added: cosmic

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

Title:
  Extracting an archive by right-clicking and selecting "Extract here"
  results in many extracted files to be 0 bytes in size

Status in nautilus package in Ubuntu:
  New

Bug description:
  Download the linux-x64 zip from here
  (https://github.com/JustArchiNET/ArchiSteamFarm/releases/tag/3.4.2.2)
  to test. Extracting works fine with the unzip command. I am not aware
  of this bug occurring with zips different from the one provided.

  Ubuntu 18.10

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

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

[Desktop-packages] [Bug 1812830] Re: Does not change the screen resolution via hdmi

Please:

1. Run:  lspci -k > lspcik.txt
2. Run:  dmesg > dmesg.txt
3. Attach the files 'lspcik.txt' and 'dmesg.txt' here.


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

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

Title:
  Does not change the screen resolution via hdmi

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  1. I'm trying to change the resolution. 
  2. no resolution choice. 
  3. expect to see a choice of screen resolution. 
  I connect via hdmi lg 26le3300 . 
  cvt 1366 768 50
   xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
 1024x768 76.00* 00: 00.0 Host bridge: Intel Corporation 4th Gen Core 
processor DRAM Controller (rev 06)
  00: 01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core processor 
PCI Express x16 Controller (rev 06)
  00: 14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset 
Family USB xHCI (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00: 1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset 
Family USB EHCI #2 (rev 04)
  00: 1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 04)
  00: 1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family 
PCI Express Root Port #1 (rev d4)
  00: 1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family 
PCI Express Root Port #3 (rev d4)
  00: 1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset 
Family USB EHCI #1 (rev 04)
  00: 1f.0 ISA bridge: Intel Corporation B85 Express LPC Controller (rev 04)
  00: 1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset 
Family 6 - port SATA Controller 1 [AHCI mode] (rev 04)
  00: 1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset family SMBus 
Controller (rev 04)
  01: 00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 
1050] (rev a1)
  01: 00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio 
Controller (rev a1)
  03: 00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111 
/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 14:40:36 2019
  InstallationDate: Installed on 2018-01-28 (358 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1812867] [NEW] sound from bluetooth device is like vintage when quiting the hibernate

You have been subscribed to a public bug:

Hi
I've just noticed this today, with my laptop and my desktop, both under Ubuntu 
Budgie 18.10, all last updates installed if it can help you. Using a USB 
Bluetooth key for both

After using my wireless speaker (JBL GO for more precision if it's
needed) within Bluetooth, I lock my computer when I leave my office.
then I unlock my computer when I'm back to.

Wanna play some music on the said device. Then I start to play music...
with somewhat vintage effect on the sound.

I shutdown the device, start it up and same thing.

To get a working properly BT, I have to

- unplug and plug the USB BT key
- middle click two time on the Bluetooth logo at the top, likely to disable / 
enable it

and then it work like a charm.

** Affects: ubuntubudgie
 Importance: Undecided
 Status: New

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


** Tags: bluetooth music sound
-- 
sound from bluetooth device is like vintage when quiting the hibernate
https://bugs.launchpad.net/bugs/1812867
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to pulseaudio 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 1772677] Re: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

** Description changed:

  [Impact]
  
  I'm seeing a several gigs (more than 70GB) a day of
  org.gnome.Shell.desktop log entries.
  
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/602
  
  [Test Case]
- With 2 monitors connected, simply lock the screen and leave it locked for a 
while. The error messages will be logged into syslog until all the empty space 
is filled up.
  
- May or may not have any relation to using an SSD hard drive.
+ With 2 monitors connected, simply lock the screen and leave it locked
+ for a while. The error messages will be logged into syslog until all the
+ empty space is filled up.
  
- UNVERIFIED
- Connect multiple monitors, trigger some OSD windows, disconnect a monitor or 
just suspend the system.
- NEEDS MORE INFO
+ More info:
  https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/243
  
  [Regression Potential]
  
  Low. The fix (https://gitlab.gnome.org/GNOME/gnome-
  shell/merge_requests/243) is a minor correction to window destroy logic,
  written by the main Gnome Shell maintainer.
  
  [Original Description]
  
  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:
  
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), 
has been already finalized. Impossible to set any property to it.
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82

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

In my case I think it happens for any lock after gnome-shell (on Xorg)
has already crashed and restarted itself (the panels disappear and then
reappear). Thereafter screen locking is broken.

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

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

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Cosmic:
  Fix Committed
Status in gnome-shell source package in Disco:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Disco:
  Fix Released

Bug description:
  [Impact]
  When entering the lock-screen mode, gnome-shell disables all the extensions. 
It can happen that under certain conditions ubuntu-dock re-enables itself, 
causing the ubuntu-dock to appear in the lock-screen, exposing sensitive 
information. One possible way to reproduce this is to enable dash-to-dock and 
ubuntu-dock at the same time.

  [Test Case]
  1. Make sure ubuntu-dock is enabled
  2. Enable dash-to-dock too
  3. Lock the screen
  4. Make sure the dock does not appear on the lock screen
  5. Make sure there is no warning is the journal

  [Possible Regressions]
  Even if it's something we don't really support please make sure that you can 
use dash-to-dock without uninstalling ubuntu-dock.

  [Original Bug]

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

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

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

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

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

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

[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using i3wm

It doesn't take any effort if you use the default Gnome Shell, which is
a compositing window manager already.

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

Title:
  Tearing and/or flickering when using i3wm

Status in i3-wm package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  When using Intel graphics on my hybrid Nvidia laptop, videos in Totem
  have awful tearing/flickering which makes them essentially
  unwatchable.

  With default X settings, I get tearing across the top of the screen
  (but I also get very noticeable tearing in other applications); if I
  enable TearFree (which eliminates tearing in Chrome), the tearing
  turns into jagged black flickers which extend from the top of the
  screen right down to near the bottom of the screen on some frames.

  The flickers are visible in screenshots, so I have attached one.

  Ubuntu version: Ubuntu 18.04.1
  Totem version: 3.26.0-0ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/i3-wm/+bug/1811808/+subscriptions

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

[Desktop-packages] [Bug 1812125] Re: Xubuntu 18.04 LTS had no gvfs-bin installed by default, as a result until manually installed, icons get disarranged every reboot in other PC configurations

2019-01-22 Thread David Gil

Sorry, this is a duplicate bug but thanks for the reference.

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

Title:
  Xubuntu 18.04 LTS had no gvfs-bin installed by default, as a result
  until manually installed, icons get disarranged every reboot in other
  PC configurations

Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-bin 1.36.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jan 17 06:23:36 2019
  InstallationDate: Installed on 2019-01-16 (0 days ago)
  InstallationMedia: Moment Plus OS amd64 3.8.0 "Gratitude" (20181126)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

  (NOTE: This used a custom version of Xubuntu but the screenshot came
  direct from the official Xubuntu version "xubuntu-18.04.1-desktop-
  amd64.iso")

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

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

[Desktop-packages] [Bug 1770271] Re: VegaM support

2019-01-22 Thread Chih-Hsyuan Ho

@Timo,agreed. And we are not seeing any business need to support VegaM
in Xenial in near future (if ever.)

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

Title:
  VegaM support

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in mesa source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  VegaM is a new GPU.  Please include support for VegaM in the next LTS
  (16.04.x and 18.04.x) and non-LTS releases.

  Kernel support starts here (32 patches):
  https://patchwork.freedesktop.org/patch/218839/

  Mesa support:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e

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

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

[Desktop-packages] [Bug 1576844] Re: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

2019-01-22 Thread Juno

I have recently acquired an used Latitude model and I'm having the same
issue on Ubuntu 18.04. This  E6420 model has a trackpoint/pointing stick
on it, which works fine, moving the cursor around, but the pad won't
work for something between 30 seconds to over a minute. Everything else
is running fine during that touchpad freeze. I still have not updated
the BIOS.

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

Title:
  Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

Status in xorg package in Ubuntu:
  Confirmed

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

  Several times yesterday and today (April 28-29, 2016) the touchpad
  (trackpad) on the Dell XPS 13 9343 has frozen.  Other functions
  (keyboard, screen, etc.) have been fine but the pointer has been
  frozen in place.  Then after 1-3 minutes functionality returns.

  Thank you very much for your assistance and I'd be happy to provide
  more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:

  CompizPlugins: [core,composite,opengl,cube,rotate]
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Apr 29 16:09:32 2016
  DistUpgraded: 2016-04-27 15:53:13,798 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.2.0-36-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-08-06 (267 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (2 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 27 15:54:22 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5152
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1812381] Re: Color LaserJet Pro MFP M280nw cannot print colors

2019-01-22 Thread Bug Watch Updater

** Changed in: hplipsetupdebian
   Status: Unknown => Fix Released

** Changed in: hplip (Debian)
   Status: Unknown => Fix Released

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

Title:
  Color LaserJet Pro MFP M280nw cannot print colors

Status in HPLIP:
  New
Status in hplipsetupdebian:
  Fix Released
Status in hplip package in Ubuntu:
  New
Status in hplip package in Debian:
  Fix Released

Bug description:
  Ubuntu version: 18.10
  HPLIP version 3.18.7

  I just bought a Color LaserJet Pro MFP M280nw because HP supports
  printing from Linux.

  The installation was simple, quick and very easy.

  Printing a test page from the printer itself shows a beautiful image of a 
colorul ballon.
  However printing a test page from HPLIP only prints a grayscale test page 
where it usually prints a color test page.

  Further information: In the graphical HPLIP configuration tool (HP
  Device manager) in the Print Settings tab under the General section I
  can see a Output Mode drop-down box, but the drop-down box only has
  one option; "Grayscale".

  I cannot run hp-doctor due to this bug:
  https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1759278

  This has now also been reported on https://h30434.www3.hp.com/t5
  /Printer-Software-and-Drivers/HP-Color-LaserJet-Pro-MFP-M280nw-cannot-
  print-colors-using/m-p/6983569/highlight/true#M153283

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

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

[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using i3wm

2019-01-22 Thread Josh Holland

Ok, thanks; I guess I'll live with the tearing for now, then. I agree
that it seems a bit pointless/unlikely to spend time fixing this given
most people won't run into it now that compositors are so common.

Maybe I'll get around to configuring one at some point :)

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

Title:
  Tearing and/or flickering when using i3wm

Status in i3-wm package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  When using Intel graphics on my hybrid Nvidia laptop, videos in Totem
  have awful tearing/flickering which makes them essentially
  unwatchable.

  With default X settings, I get tearing across the top of the screen
  (but I also get very noticeable tearing in other applications); if I
  enable TearFree (which eliminates tearing in Chrome), the tearing
  turns into jagged black flickers which extend from the top of the
  screen right down to near the bottom of the screen on some frames.

  The flickers are visible in screenshots, so I have attached one.

  Ubuntu version: Ubuntu 18.04.1
  Totem version: 3.26.0-0ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/i3-wm/+bug/1811808/+subscriptions

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

[Desktop-packages] [Bug 1750069] Re: [MIR] xdg-desktop-portal-gtk

2019-01-22 Thread Seth Arnold

Security team ACK for promoting xdg-desktop-portal-gtk and xdg-desktop-
portal to main for bionic and xenial.

Thanks

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

Title:
  [MIR] xdg-desktop-portal-gtk

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gtk source package in Xenial:
  Incomplete
Status in xdg-desktop-portal-gtk source package in Bionic:
  Incomplete

Bug description:
  Availability
  
  Actively maintained in debian and we'll sync from debian again when 0.10 is 
avaiable.

  Built for all supported architectures.

  Rationale
  =
  Required for snaps.

  Security
  
  No known security issues, but due to the nature of this package, a security 
review is probably needed.

  
https://security-tracker.debian.org/tracker/source-package/xdg-desktop-portal-gtk
  https://launchpad.net/xdg-desktop-portal-gtk/+cve

  Quality assurance
  =
  - The Desktop Packages bug team is subscribed.

  https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xdg-desktop-portal-gtk
  https://github.com/flatpak/xdg-desktop-portal-gtk/issues

  Dependencies
  
  No universe binary dependencies

  Standards compliance
  
  4.1.3

  debhelper compat 10, dh 7 style simple rules

  Maintenance
  ===
  - Actively developed upstream. Last release was 0.10, this week.
  https://github.com/flatpak/xdg-desktop-portal-gtk/commits/master

  Well-maintained in Debian by Simon McVittie (Debian's Flatpak maintainer). 
Team-maintained.
  https://salsa.debian.org/debian/xdg-desktop-portal-gtk

  Background information
  ==
  This is needed to make xdg-desktop-portal useful in Ubuntu Desktop.  See 
xdg-desktop-portal MIR bug LP: #1749672

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069/+subscriptions

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

[Desktop-packages] [Bug 1749672] Re: [MIR] xdg-desktop-portal

2019-01-22 Thread Seth Arnold

Security team ACK for promoting xdg-desktop-portal-gtk and xdg-desktop-
portal to main for bionic and xenial.

Thanks

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

Title:
  [MIR] xdg-desktop-portal

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Xenial:
  Triaged
Status in xdg-desktop-portal source package in Bionic:
  Triaged

Bug description:
  Availability
  
  In sync with Debian.

  Built for all supported architectures.

  Rationale
  =
  Required for snaps.

  Security
  
  No known security issues, but due to the nature of this package, a security 
review is probably needed.

  https://security-tracker.debian.org/tracker/source-package/xdg-desktop-portal
  https://launchpad.net/xdg-desktop-portal/+cve

  Quality assurance
  =
  - The Desktop Packages bug team is subscribed.

  https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xdg-desktop-portal
  https://github.com/flatpak/xdg-desktop-portal/issues

  Upstream build tests (new) are run with dh_auto_test (failure would
  fail the build).

  autopkgtests are passing
  https://autopkgtest.ubuntu.com/packages/xdg-desktop-portal
  https://ci.debian.net/packages/x/xdg-desktop-portal/unstable/amd64/

  Dependencies
  
  No universe binary dependencies

  Standards compliance
  
  4.1.3

  debhelper compat 11, dh 7 style simple rules

  Maintenance
  ===
  - Actively developed upstream. Last release was 0.10 yesterday
  https://github.com/flatpak/xdg-desktop-portal/commits/master

  Well-maintained in Debian by Simon McVittie (Debian's Flatpak maintainer). 
Team-maintained.
  https://salsa.debian.org/debian/xdg-desktop-portal

  Background information
  ==
  xdg-desktop-portal was originally created to allow Flatpak apps to request 
access outside the sandbox. It's useful technology that can be used by Snap 
too, which simplifies work for app developers to support both next generation 
packaging formats. For instance, see 
https://blogs.gnome.org/alexl/2018/02/14/moving-a-portal/

  See also the MIR xdg-desktop-portal-gtk LP: #1750069.

  Presumably, we'll want to backport these packages to be snap
  dependencies in 16.04 LTS (maybe 14.04 LTS too).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672/+subscriptions

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

[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS

2019-01-22 Thread Jim Campbell

Hi All - I can test this on Xenial tomorrow (Jan 23). I'll report back
after testing.

Thanks to Brian for getting the package into xenial-proposed.

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

Title:
  geoip.ubuntu.com does not utilize HTTPS

Status in ubuntu-geoip package in Ubuntu:
  Fix Released
Status in ubuntu-geoip source package in Trusty:
  Triaged
Status in ubuntu-geoip source package in Xenial:
  Fix Committed
Status in ubuntu-geoip source package in Artful:
  Won't Fix

Bug description:
  Impact
  --
  It's better to use https where we can. There were concerns about location 
leakage for users using a proxy (such as Tor).

  Test Case
  -

  1) Install patches / patched package
  2) Confirm that the 'geoip url' is set to a correct 'https' value, and that 
this value is set as the default:
 `$ gsettings get com.ubuntu.geoip geoip-url` should display 
`https://geoip.ubuntu.com/lookup`
 `$ gsettings reset com.ubuntu.geoip geoip-url && gsettings get 
com.ubuntu.geoip geoip-url` should continue to display 
`https://geoip.ubuntu.com/lookup` (this will confirm that the `https` value is 
set as the default.
  3) Confirm that the the correct location is being retrieved by the Ubuntu 
geoip service:
 apt install geoclue-examples
 and then geoclue-test-gui
 . . . should show correct location information.

  Regression Potential
  
  As long as Canonical maintains https://geoip.ubuntu.com, things should be 
fine here. Minimal fix.

  Original Bug Report
  ---
  geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This 
can potentially be utilized by nation state adversaries to compromise user 
privacy. This service is called multiple times per day by the OS in order to 
track users.

  $ nc -zv geoip.ubuntu.com 80
  Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded!

  $ nc -zv -w 3 geoip.ubuntu.com 443
  nc: connect to geoip.ubuntu.com port 443 (tcp) timed out

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

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

[Desktop-packages] [Bug 1812247] Re: ssh-agent fails for ssh-add -c: agent refused operation

2019-01-22 Thread schamane

I have now removed the "marked as a duplicate of bug 1789523".

** This bug is no longer a duplicate of bug 1789523
   The ssh-agent launcher script fails to relaunch ssh-agent

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

Title:
  ssh-agent fails for ssh-add -c: agent refused operation

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means
  of `ssh-add -c` indicating that keys "should be subject to
  confirmation before being used for authentication. In Ubuntu 18.10
  this fails with the error

sign_and_send_pubkey: signing failed: agent refused operation

  To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt-
  get upgrade, log out and log back in (these steps are not required but
  we want to use an up-to-date system). Then:

  $ sudo apt-get install ssh-askpass-gnome
  (...)
  $ # verify that ssh-askpass shows a popup, confirm with Enter
  $ ssh-askpass ; echo $?

  0
  $ ssh-keygen
  (...)
  $ ssh-add -D
  All identities removed.
  $ ssh-copy-id $sshuser@$sshserver
  (...)
  Number of key(s) added: 1
  (...)
  $ ssh $sshuser@$sshserver uname -a
  Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 
GNU/Linux
  $ ssh-add -d
  Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu)
  $ ssh-add -c
  Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): 
  Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa)
  The user must confirm each use of the key
  $ ssh $sshuser@$sshserver uname -a
  sign_and_send_pubkey: signing failed: agent refused operation
  sshuser@server's password: [^C'ed]

  $ ssh-add -l
  2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc 
/home/ubuntu/.ssh/id_rsa (RSA)

  So, our key is loaded, ssh-askpass is working (also confirmed with
  `ssh-add -c 
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS

Hello xtsbdu3reyrbrmroezob, or anyone else affected,

Accepted ubuntu-geoip into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
geoip/1.0.2+14.04.20131125-0ubuntu2.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.

** Tags added: verification-needed verification-needed-xenial

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

Title:
  geoip.ubuntu.com does not utilize HTTPS

Status in ubuntu-geoip package in Ubuntu:
  Fix Released
Status in ubuntu-geoip source package in Trusty:
  Triaged
Status in ubuntu-geoip source package in Xenial:
  Fix Committed
Status in ubuntu-geoip source package in Artful:
  Won't Fix

Bug description:
  Impact
  --
  It's better to use https where we can. There were concerns about location 
leakage for users using a proxy (such as Tor).

  Test Case
  -

  1) Install patches / patched package
  2) Confirm that the 'geoip url' is set to a correct 'https' value, and that 
this value is set as the default:
 `$ gsettings get com.ubuntu.geoip geoip-url` should display 
`https://geoip.ubuntu.com/lookup`
 `$ gsettings reset com.ubuntu.geoip geoip-url && gsettings get 
com.ubuntu.geoip geoip-url` should continue to display 
`https://geoip.ubuntu.com/lookup` (this will confirm that the `https` value is 
set as the default.
  3) Confirm that the the correct location is being retrieved by the Ubuntu 
geoip service:
 apt install geoclue-examples
 and then geoclue-test-gui
 . . . should show correct location information.

  Regression Potential
  
  As long as Canonical maintains https://geoip.ubuntu.com, things should be 
fine here. Minimal fix.

  Original Bug Report
  ---
  geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This 
can potentially be utilized by nation state adversaries to compromise user 
privacy. This service is called multiple times per day by the OS in order to 
track users.

  $ nc -zv geoip.ubuntu.com 80
  Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded!

  $ nc -zv -w 3 geoip.ubuntu.com 443
  nc: connect to geoip.ubuntu.com port 443 (tcp) timed out

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

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

[Desktop-packages] [Bug 1226212] Re: No video thumbnails on sftp

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

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

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  No video thumbnails on sftp

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04
  ---
  $ sudo apt-cache policy nautilus
  nautilus:
Installed: 1:3.6.3-0ubuntu16
Candidate: 1:3.6.3-0ubuntu16
Version table:
   *** 1:3.6.3-0ubuntu16 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status
  ---

  Nautilus doesn't create video thumbnails on sftp since quantal (12.10)

  The following warning is thrown:

  (nautilus:32597): GnomeDesktop-WARNING **: Unable to create loader for mime 
type video/x-msvideo: Unrecognized image file format
  (nautilus:32597): GnomeDesktop-WARNING **: Error creating thumbnail for 
sftp://user@server/media/storage/file.avi: Unrecognized image file format

  
  Affects all video formats on sftp. Thumbnails are shown for local files and 
thumbnails are shown for images on sftp.
  All necessary codecs are installed on both machines. And they're both running 
ubuntu 13.04 (Issue first popped up after 12.10 upgrade)

  There appears to be a related bug: 
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1084869
  But the problem exists even if I switch to ffmpeg-thumbnailer

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

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

[Desktop-packages] [Bug 1310166] Re: Progress bar not showing status.

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

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

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Progress bar not showing status.

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  I was moving a file from my Ubuntu 14.04 system to a Fedora 17 system
  via sftp using nautilus.  The progress bar would show "Preparing to
  move file", and then the progress bar did not change.  The file did
  actually move.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sat Apr 19 22:26:18 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-04-18 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1282824] Re: Nautilus has problems mounting network locations when nautilus-open-terminal is installed

** No longer affects: nautilus (Ubuntu)

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

Title:
Nautilus has problems mounting network locations when nautilus-open-
terminal is installed

Status in nautilus-open-terminal package in Ubuntu:
New

Bug description:
At least in Ubuntu 13.10, when this extension (nautilus-open-terminal) is
installed, Nautilus has some serious problems when mounting SFTP locations, and
possibly other protocols like Samba as well (haven't tested that).
These problems occur, more specifically, when trying to mount the same SFTP
location a second time (after having mounted and unmounted it before).

The culprit seems to be this extension because, when the extension is not
installed or disabled, these problems don't occur.
I disabled the extension temporarily by renaming the file
/usr/lib/nautilus/extensions-3.0/libnautilus-open-terminal.so.
I also tested this using a Live DVD (Nautilus worked fine before installing
the extension).

More information below.

---

To test this problem, the ssh server must be installed and running,
and the nautilus-open-terminal extension must be installed (and not
disabled).

TEST CASE

1. Open Nautilus
2. Go to the location "sftp://localhost;, for example (Press Ctrl+L, write
the location and press enter)
3. Enter the ssh credentials if asked
4. The SFTP location should be mounted. Unmount it by pressing the respective
unmount "arrow" button in the sidebar
5. Try to mount it again by repeating step 2 (and maybe 3)

WHAT WAS EXPECTED

The SFTP location was mounted successfully again

WHAT HAPPENED

Nautilus crashed.
This is the error displayed in the terminal (when Nautilus is started from
the terminal):
ERROR:nautilus-bookmark.c:350:nautilus_bookmark_connect_file: assertion
failed: (!nautilus_file_is_gone (bookmark->details->file))

---

I also tested something else.

I configured avahi to publish my computer as an SSH and SFTP server.
The following commands should be enough to do this:
$ sudo cp /usr/share/doc/avahi-daemon/examples/s* /etc/avahi/services/
$ sudo restart avahi-daemon

My computer then appears in Nautilus Network "folder".
The first time my computer is double-clicked, it is mounted successfully
through SFTP.
But, on the second time (after unmounting), the following error message is
displayed in a dialog:

Could not display "".
The file is of an unknown type

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: nautilus-open-terminal 0.20-1
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Thu Feb 20 23:14:53 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-11-01 (111 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
MarkForUpload: True
SourcePackage: nautilus-open-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1361846] Re: nautilus stops reacting when sftp connection gets interrupted

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

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

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

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

Title:
  nautilus stops reacting when sftp connection gets interrupted

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce the error:
  - connect to LAN
  - open a nautilus window
  - connect to an sftp server (select directly forget password)
  - browse the directory
  - disconnect LAN
  - connect WLAN (same router)
  -> that means network is still connected but the sftp connection is now 
interrupted
  - double click a folder from the sftp server

  What should happen:
  - nautilus should open the sftp folder, re-connecting to the server, or at 
least show an error message that the connection got interrupted

  What happens instead:
  - nautilus does nothing, waiting forever for the server to respond
  - all other folders can be accessed
  - after closing the last nautilus window nautilus will not start any more 
until you logout and login again

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.3
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 26 21:37:53 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-10 (320 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (130 days ago)
  usr_lib_nautilus:
   deja-dup   30.0-0ubuntu4
   evince 3.10.3-0ubuntu10.1
   file-roller3.10.2.1-0ubuntu4.1
   nautilus-share 0.7.3-1ubuntu5
   totem  3.10.1-1ubuntu4

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

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

[Desktop-packages] [Bug 1521153] Re: Nautilus sftp freeze

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

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

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

Title:
  Nautilus sftp freeze

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  If something goes stuck on sftp transfer (or just directory load /
  refresh) nautlius may freeze hard.

  -On Ubuntu 12.04, the concerned directory windows freeze, and can be
  removed by ejecting the sftp mount. The related windows can't recover.
  This is not cool.

  -On Ubuntu 14.04.03 it is even worse: A frozen sftp freezes ALL
  nautilus windows, and if running gnome classic session, it even
  freezes the whole gnome-panel. This is just akward.

  I don't know where to blame this first, but this is definitely caused
  by several bad designs.

  -Nautilus should handle frozen sftp filesystems generously (timeouts,
  still respond to user while showing frozen state, eg darken the file
  list or something )

  -Nautilus should never freeze other windows except the ones concerned
  (was so in older nautlius as of Ubuntu 12.04)

  -gnome-panel should never freeze on nautlilus freeze.

  
  Sadly this was bad and got even worse... can we do the turn around?

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

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

[Desktop-packages] [Bug 1782511] Re: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all

2019-01-22 Thread MAI Anh Tuan

I can change sound volume, mute/unmute. It shows as everything works fine but 
actually no sound on builtin speaker.
Jack 3.5 works fine.
Bluetooth speaker works fine.

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

Title:
  [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  none

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 2209 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 18 22:19:23 2018
  InstallationDate: Installed on 2018-07-19 (0 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=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
   /dev/snd/controlC0:  gdm 961 F pulseaudio
ubuntu 2209 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX370UAR.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX370UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.303:bd11/16/2017:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX370UAR
  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/1782511/+subscriptions

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

[Desktop-packages] [Bug 1473943] Re: root directory inconsistencies in sftp mounts in file manager

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

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

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  root directory inconsistencies in sftp mounts in file manager

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  I have a Debian server on 192.168.1.2, and would like to mount its
  file system root using the File Manager.  So I select "Connect to
  Server" and enter

  sftp://root@192.168.1.2 (plus any number of trailing slashes!)

  The resulting network mount that appears in the Places column calls
  itself "root on 192.168.1.2" (as does the navigation button at the
  top) and the tool-tip says "sftp://192.168.1.2/root;.  As might be
  expected, I cannot navigate below /root (the root user's home
  directory) to the root of the file system.  (I would like to, but I
  haven't found a way of specifying the Server Address to achieve this.)

  But now the inconsistency.  If I bring up a file open dialogue in
  another application and click on the identically-named network mount
  in the Places column, this time it *does* open the file system root,
  and the navigation button is labelled "/ on 192.168.1.2".

  I would expect the File Manager and open file dialogues to display the
  same point in the remote hierarchy when the mount point is selected -
  preferably what the open file dialogue does as it is impossible to get
  to the remote server's file system root in the File Manager.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.7
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 13 11:52:15 2015
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 
'mime_type', 'where', 'date_accessed']"
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2014-04-24 (445 days ago)

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

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

[Desktop-packages] [Bug 1193058] Re: No way to get out of the home directory after connecting to server by ssh

Could you try if that's still an issue in newer Ubuntu versions?

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

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

Title:
  No way to get out of the home directory after connecting to server by
  ssh

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  By default I get logged to my /home/myname/ directory. And I cannot get 
anywhere out of it like in to /opt/apps because:
  - there is no move up button in the GUI, only the move back button
  - my home directory is the root item in the top navigation menu

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

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

[Desktop-packages] [Bug 1312735] Re: Nautilus asks for SSH login, even when it authenticates with a key file

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

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

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

Title:
  Nautilus asks for SSH login, even when it authenticates with a key
  file

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 14.04

  When there's a valid key file for authentication over SSH/SFTP,
  Nautilus first asks for the server login, but then proceeds to log in
  using the key file. It should probably be the other way around.

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

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

[Desktop-packages] [Bug 1299177] Re: Nautilus doesn't save server connection settings

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

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

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Nautilus doesn't save server connection settings

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  While connecting to remote SSH or FTP servers via Nautilus tool
  "Connect to server", there is option to forget or remember password.
  Whatever you choose, it will forget password.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 28 23:24:12 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2014-03-18 (10 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140317)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1452775] Re: Nautilus mixes up SSH handles of multiple connections to identical IP using different ports

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

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

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

Title:
   Nautilus mixes up SSH handles of multiple connections to identical IP
  using different ports

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  When connecting to one given IP on SSH multiple times using custom
  ports, e.g.

  127.0.0.1:22062 and
  127.0.0.1:22064

  and browsing them interchangeably, Nautilus will display the
  respective file lists and folder structures correctly in different
  tabs; however, when trying to open a file that exists in the file
  system at 22062 but not in 22064 Nautilus will report any file as
  missing within a correctly displayed folder on machine 22062 that does
  not exist at 22064 once one has accessed 22064 a single time before.
  In case the file does exist, Nautilus might display and later on write
  to either version (did not grasp the pattern yet) which leads to
  serious mess working on two different machines behind a common NAP
  using port masquerading as in stated scenario

  This bug is persistent throughout an entire unity session even after
  disconnecting from the remote machine as well as after terminating
  Nautilus so i suggest the bug might as well be based somewhere outside
  Nautilus where SSH connections are stacked or something.

  Might as well be security-related in case something is written to a
  place it shouldn't end up.

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

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

[Desktop-packages] [Bug 1397541] Re: Misleading permission error when trying to connect to another computer

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

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

Title:
  Misleading permission error when trying to connect to another computer

Status in nautilus package in Ubuntu:
  New

Bug description:
  I was trying to connect to another computer using ssh/sftp in nautilus
  in order to access its files. After typing the computer's address with
  the protocol and clicking "connect" I was shown this error:

  "Oops! Something went wrong. Don't have permission to access the
  requested location."

  It turned out I do not have the package openssh-server installed on
  the other computer. At the begginning I was irritated because I was
  sure it is a permission problem as the error stated. In my opinion
  Nautilus should be able to recognise there is no ssh server installed
  on the other computer and tell the user in the error what they should
  do to fix the reason behind it.

  OS: Ubuntu 14.10
  GNOME nautilus 3.10.1

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

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

[Desktop-packages] [Bug 1522628] Re: Regression: Nautilus on 14.04.3 stalls when handling while copying.

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

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

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

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

Title:
  Regression: Nautilus on 14.04.3 stalls when handling while copying.

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  When copying files from my ext4 harddrive to my external USB harddrive
  (btfs in that case), and simultanously browsing in the windows the
  copy was initated from, the copying may stall. I can still browse the
  drive sometimes. After that, any further file copy operation to that
  drive stalls to. top shows CPU is at idle, iotop shows no disk
  operations. Suddenly after some time (a minute sometimes) the
  operation continues. There are no other stalled mounts (like sftp),
  only the external drive.

  I can still access the external drive via terminal, anything is ok.

  There are no btrfs messages on dmesg.

  Problem occurs on Ubuntu 14.04.3 LTS. This worked reliable with Ubuntu
  12.04.

  I am reporting problem after problem for nautilus in the past days
  since I installed 14.04.  Ubuntu 14.04 is over a year old, what
  happened? Nautilus worked far more reliable on 12.04.

  Any recommendation of an usable filemanager that relies on proven
  code? Maybe Nemo?

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

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

[Desktop-packages] [Bug 1699095] Re: Nautilus deletes files in wrong tab

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

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

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

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

Title:
  Nautilus deletes files in wrong tab

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  This has now happened to me twice:

  When deleting files/folders by highlighting and pressing shift-delete,
  files in a different tab are deleted instead. In one case, instead of
  deleting 20 highlighted files in active tab, 20 000 files in another
  tab were deleted.

  Both times it has happened when connected to server via sftp. In both
  cases it has been files/folders in tabs to the right of active tab
  which have been deleted.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 20 11:24:39 2017
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'151'
   b'org.gnome.nautilus.window-state' b'geometry' b"'932x565+988+21'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2015-11-23 (574 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to xenial on 2017-03-20 (91 days ago)

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

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

[Desktop-packages] [Bug 1773063] Re: Unable to open files from Nautilus sftp mount in non-default Ubuntu programs

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

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

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

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

Title:
  Unable to open files from Nautilus sftp mount in non-default Ubuntu
  programs

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  When I mount a remote ssh file system using the 'nautilus connect to server' 
option, I would expect that when I right click the file to open with a 
particular program it should work seamlessly.  However, I am only able to do 
this with 'standard' ubuntu packages such as gedit or libre writer.
  If I try to open the file with Geany or Atom, the files fail to open.  Even 
when I try to open the files from the open dialog box inside of these programs 
the files don't open.

  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  nautilus:
Installed: 1:3.18.4.is.3.14.3-0ubuntu6
Candidate: 1:3.18.4.is.3.14.3-0ubuntu6
Version table:
   *** 1:3.18.4.is.3.14.3-0ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.18.4.is.3.14.3-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

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

[Desktop-packages] [Bug 1079566] Re: slow by opening local folder

The comments suggest it was fixed in newer nautilus versions

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

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => 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/1079566

Title:
  slow by opening local folder

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Since the I upgraded to Ubuntu 12.1, Nautilus file browser are very
  slow to open and then to navigate trough the local folders. If I
  execute Nautilus with "sudo" command it's much faster. It's work also
  normaly with remote folder like sftp (ssh).

  I try to disable the generating of the thumbnail, but still the same,
  and when I choice "Never" or "only local files it's take a very long
  time to save the option.

  Some times it's so long that a window is appear and tell me that I
  have to wait until the folder will be open. It's a very significantly
  diffirence between the ubuntu 12.0

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Fri Nov 16 08:09:41 2012
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'820x607+49+24'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'221'
  InstallationDate: Installed on 2010-11-02 (744 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2012-10-30 (16 days ago)

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

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

[Desktop-packages] [Bug 1087875] Re: nautilus crashes when connecting to SSH file server

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  nautilus crashes when connecting to SSH file server

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Mounting the SSH file server worked in Ubuntu 12.04 but crashes
  Nautilus in 12.10.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-20.31-generic 3.5.7.1
  Uname: Linux 3.5.0-20-generic i686
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: i386
  CrashCounter: 1
  Date: Sat Dec  8 01:16:57 2012
  ExecutablePath: /usr/bin/nautilus
  ExecutableTimestamp: 1349459689
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'800x550+65+189'"
  InstallationDate: Installed on 2011-12-30 (343 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MarkForUpload: True
  ProcCmdline: nautilus
  ProcCwd: /home/alpo
  SegvAnalysis:
   Segfault happened at: 0xb6a217da :movsbl (%ecx),%edx
   PC (0xb6a217da) ok
   source "(%ecx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   g_str_hash (v=0x0) at /build/buildd/glib2.0-2.34.1/./glib/ghash.c:1730
   g_hash_table_lookup_node (hash_return=, key=0x0, 
hash_table=0xa4fe400) at /build/buildd/glib2.0-2.34.1/./glib/ghash.c:401
   g_hash_table_lookup_extended (hash_table=0xa4fe400, 
lookup_key=lookup_key@entry=0x0, orig_key=orig_key@entry=0xbff62f78, 
value=value@entry=0xbff62f7c) at 
/build/buildd/glib2.0-2.34.1/./glib/ghash.c:1110
   modify_link_hash_table (file=file@entry=0xa57f688, 
modify_function=modify_function@entry=0x80fe720 ) 
at nautilus-file.c:563
   add_to_link_hash_table (file=0xa57f688) at nautilus-file.c:605
  Title: nautilus crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: Upgraded to quantal on 2012-12-07 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 908466] Re: IPv6 avahi servers are not discovered

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  IPv6 avahi servers are not discovered

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  When I click 'Browse Network' in nautilus, I get a list of computers
  advertising SFTP on my network.

  My laptop doesn't show up in the list.

  Here is the avahi output for my laptop (the MAC address has been removed):
  chris@chris-iMac:~$ avahi-browse -ta | grep M3
  +  wlan0 IPv6 chris@chris-Inspiron-M301ZiChat Presence
   local
  +   eth0 IPv6 chris@chris-Inspiron-M301ZiChat Presence
   local
  +  wlan0 IPv6 chris-Inspiron-M301Z  SFTP File 
Transfer   local
  +   eth0 IPv6 chris-Inspiron-M301Z  SFTP File 
Transfer   local
  +  wlan0 IPv6 chris-Inspiron-M301Z  SSH Remote 
Terminal  local
  +   eth0 IPv6 chris-Inspiron-M301Z  SSH Remote 
Terminal  local
  +  wlan0 IPv6 chris-Inspiron-M301Z  Apple File 
Sharing   local
  +   eth0 IPv6 chris-Inspiron-M301Z  Apple File 
Sharing   local
  +  wlan0 IPv6 chris-Inspiron-M301Z [**:**:**:**:**:**]  Workstation   
   local
  +   eth0 IPv6 chris-Inspiron-M301Z [**:**:**:**:**:**]  Workstation   
   local
  +  wlan0 IPv6 chris-Inspiron-M301Z  Remote Disk 
Management local
  +   eth0 IPv6 chris-Inspiron-M301Z  Remote Disk 
Management local

  
  Here is a computer that does show up:
  chris@chris-iMac:~$ avahi-browse -ta | grep michael
  +  wlan0 IPv6 michael-test  SFTP File 
Transfer   local
  +   eth0 IPv6 michael-test  SFTP File 
Transfer   local
  +   eth0 IPv4 michael-test  SFTP File 
Transfer   local
  +  wlan0 IPv6 michael-test  SSH Remote 
Terminal  local
  +   eth0 IPv6 michael-test  SSH Remote 
Terminal  local
  +   eth0 IPv4 michael-test  SSH Remote 
Terminal  local
  +  wlan0 IPv6 michael-test [**:**:**:**:**:**]  Workstation   
   local
  +   eth0 IPv6 michael-test [**:**:**:**:**:**]  Workstation   
   local
  +   eth0 IPv4 michael-test [**:**:**:**:**:**]  Workstation   
   local
  +  wlan0 IPv6 michael-test  Remote Disk 
Management local
  +   eth0 IPv6 michael-test  Remote Disk 
Management local
  +   eth0 IPv4 michael-test  Remote Disk 
Management local

  There are 2 differences (that I think are significant) between my
  laptop and the computers showing up. My laptop is only connected over
  wifi. My laptop is only showing up as IPv6 (presumably because of the
  wifi network).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.2.1-2ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6
  Uname: Linux 3.2.0-6-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  Date: Sat Dec 24 21:28:25 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to precise on 2011-12-24 (0 days ago)

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

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

[Desktop-packages] [Bug 567911] Re: 'connect to server' with ssh folder option does not accept ~

The UI described doesn't exist anymore, closing the bug

** Changed in: nautilus (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  'connect to server' with ssh folder option does not accept ~

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nautilus

  If the 'Folder' field is left blank, you're dropped in root.  This was
  confirmed on OS X 10.5, AIX 5.3.10 and RHEL 5.5.  This may be expected
  behaviour; however, I was expecting the user's home directory.
  Regardless, specifying ~ leads to an error.  A pop-up window with
  'Count not find sftp://server/~; appears.  If the protocol inhibits
  home access with the ~ character, a more helpful error would be
  appreciated.

  ProblemType: Bug
  Architecture: amd64
  Date: Wed Apr 21 09:52:54 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/nautilus
  Package: nautilus 1:2.28.1-0ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
  SourcePackage: nautilus
  Uname: Linux 2.6.31-20-generic x86_64

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

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

[Desktop-packages] [Bug 1812914] [NEW] X diagnostics

2019-01-22 Thread Jacques Basseck

Public bug reported:

This bug is from X Diagnostics

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
Uname: Linux 4.18.0-14-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Jan 22 21:42:20 2019
DistUpgraded: 2019-01-15 00:39:12,441 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 
6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Mobility Radeon HD 5650 [104d:9071]
InstallationDate: Installed on 2016-10-08 (836 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 064e:a213 Suyin Corp. 
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Sony Corporation VPCEC1S1E
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic 
root=UUID=7c6080a7-1a0e-4121-94f1-42cba8e7b69c ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to cosmic on 2019-01-14 (7 days ago)
dmi.bios.date: 07/20/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0300Y8
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:bvnAmericanMegatrendsInc.:bvrR0300Y8:bd07/20/2010:svnSonyCorporation:pnVPCEC1S1E:pvrC6050X6T:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: VPCEC1S1E
dmi.product.sku: N/A
dmi.product.version: C6050X6T
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
xserver.bootTime: Tue Jan 22 21:23:19 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.1-3ubuntu2.1
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug cosmic third-party-packages 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/1812914

Title:
  X diagnostics

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug is from X Diagnostics

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jan 22 21:42:20 2019
  DistUpgraded: 2019-01-15 00:39:12,441 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 
/ 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Mobility Radeon HD 5650 [104d:9071]
  InstallationDate: Installed on 2016-10-08 (836 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 064e:a213 Suyin Corp. 
   Bus 001 Device 002:

[Desktop-packages] [Bug 44441] Re: Can't execute over SSH.

upstream said they are not interested in providing that capability

** Changed in: nautilus (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  Can't execute over SSH.

Status in Nautilus:
  Won't Fix
Status in nautilus package in Ubuntu:
  Won't Fix

Bug description:
  Currently, nautilus is not capable of executing files or determining
  permissions over the network.  When going to the permissions tab it
  says "The permissions of ___ couldn't be determined".   Chmod is a
  pretty common operation.

  Also, there is no way to execute scripts/binary files.  When running an 
executable binary file, this error is displayed:
  Couldn't display (address)
  This error message isn't really that helpful at all.

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

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

[Desktop-packages] [Bug 343000] Re: Default portnumbers removed from Nautilus bookmarks

The new upstream report is
https://gitlab.gnome.org/GNOME/gvfs/issues/129

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

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

Title:
  Default portnumbers removed from Nautilus bookmarks

Status in Nautilus:
  Expired
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  Recently I changed /etc/ssh/ssh_config.  I changes port=22 --->
  port=nnn.  After I did this all my ssh bookmarks in the nautilus
  explorer stopped working.  I could still login to the ssh shell from a
  terminal but it required that I include the -p nnn option.  The
  servers still worked.  I can get the nautilus to connect to the ssh
  thought sftp interactive mode by including a port specification. I now
  use sftp://user@server:22/folder instead of sftp://user@server/folder.
  I thought I had solved my problem at this point.   This is not the
  case.  It seems that nautilus will delete the :22 from the bookmark.
  It will not delete any other port number number.  I assume  this is
  because :22 is default and nautilus thinks that this specification is
  redundant. However if you change you ssh_config, :22 is required.

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

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

[Desktop-packages] [Bug 1183948] Re: Can not read/write files to walkman (MTP)

Thanks (and sorry for the lack of activity), closing the bug then

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => 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/1183948

Title:
  Can not read/write files to walkman (MTP)

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  So today I connected walkamn to my ubuntu pc knowing that it used to work at 
least on every other versions of ubuntu I have tried, latest 12.10
  So I connected it and it showed files and folders as it used to but when I 
try to play something, it did not work, vlc even showed an error massage

  [CODE]File reading failed:VLC could not open the file 
"/run/user/levan/gvfs/mtp:host=%5Busb%3A001%2C006%5D/65537/7/6268". (Operation 
not supported)
  Your input can't be opened:
  VLC is unable to open the MRL 
'file:///run/user/levan/gvfs/mtp%3Ahost%3D%255Busb%253A001%252C006%255D/65537/7/6268'.
 Check the log for details.[/CODE]

  and I do not remember if it used to show the location of walkman as

  [CODE]mtp://[usb:001,006]/65537[/CODE]

  on other ubuntu for example (12.10) this thing used to work even
  better than on windows ??

  does not work in ubuntu 14.04 as well

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Fri May 24 21:41:48 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'867x571+198+354'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'121'
  InstallationDate: Installed on 2013-04-26 (28 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2019-01-22 Thread Efthimios Chaskaris

Is there a way to reliably reproduce the bug? Because, for me, it
happens randomly.

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

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

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Cosmic:
  Fix Committed
Status in gnome-shell source package in Disco:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Disco:
  Fix Released

Bug description:
  [Impact]
  When entering the lock-screen mode, gnome-shell disables all the extensions. 
It can happen that under certain conditions ubuntu-dock re-enables itself, 
causing the ubuntu-dock to appear in the lock-screen, exposing sensitive 
information. One possible way to reproduce this is to enable dash-to-dock and 
ubuntu-dock at the same time.

  [Test Case]
  1. Make sure ubuntu-dock is enabled
  2. Enable dash-to-dock too
  3. Lock the screen
  4. Make sure the dock does not appear on the lock screen
  5. Make sure there is no warning is the journal

  [Possible Regressions]
  Even if it's something we don't really support please make sure that you can 
use dash-to-dock without uninstalling ubuntu-dock.

  [Original Bug]

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

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

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

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

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

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

[Desktop-packages] [Bug 1782511] Re: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  none

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 2209 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 18 22:19:23 2018
  InstallationDate: Installed on 2018-07-19 (0 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=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
   /dev/snd/controlC0:  gdm 961 F pulseaudio
ubuntu 2209 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX370UAR.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX370UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.303:bd11/16/2017:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX370UAR
  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/1782511/+subscriptions

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

[Desktop-packages] [Bug 1782511] Re: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all

2019-01-22 Thread MAI Anh Tuan

It happens on my PC too
Ubuntu 18.04
HP Pavilion Power CB015NF
ALC295

alsa-info : http://www.alsa-
project.org/db/?f=7f12cf628a3c1d6dc471983775b8dc17162b263d

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

Title:
  [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  none

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 2209 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 18 22:19:23 2018
  InstallationDate: Installed on 2018-07-19 (0 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=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
   /dev/snd/controlC0:  gdm 961 F pulseaudio
ubuntu 2209 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX370UAR.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX370UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.303:bd11/16/2017:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX370UAR
  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/1782511/+subscriptions

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

[Desktop-packages] [Bug 1185703] Re: Nautilus crashes when I plug in my HTC One SV android phone

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

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

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

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

Title:
  Nautilus crashes when I plug in my HTC One SV android phone

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  The phone uses MTP I believe rather than USB mass storage, I assume
  the issue is associated with this.  I am using Ubuntu 13.04 and
  nautilus 3.6.3 with Gnome 3.

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

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

[Desktop-packages] [Bug 1299409] Re: Crash when moving files to mtp android device (after some time)

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

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

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

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

Title:
  Crash when moving files to mtp android device (after some time)

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Syslog shows:  Mar 29 11:15:41 Arbeits-PC kernel: [ 6791.820138]
  nautilus[7322]: segfault at 0 ip 7fa7dab4f0d9 sp 7fff8f2546b0
  error 4 in libgtk-3.so.0.1000.7[7fa7da96d000+4ff000]

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

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

[Desktop-packages] [Bug 1358076] Re: MTP harassment

The bug is years old without activity nor recent similar report, closing
as deprecate. You can open a new bug if that's still an issue though

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

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

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

Title:
  MTP harassment

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  I plugged my Android 4.4.4 device in to charge, and it was locked by a 
pattern. Files kept trying to mount it, spamming me with a dialog each time. 
The amount of dialogs between the spam increased until it became unbearable, as 
seen in the screencast here:
  https://dl.dropboxusercontent.com/u/84880/MTP%20harassment.mp4

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.3
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 18 12:11:26 2014
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 
'size', 'date_modified']"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'group', 'where', 'mime_type', 
'owner', 'permissions']"
  InstallationDate: Installed on 2012-03-23 (877 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2014-07-26 (22 days ago)

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

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

[Desktop-packages] [Bug 1812908] Re: Ubuntu Budgie no longer shows any menu categories after the upgrade

2019-01-22 Thread fossfreedom

Can confirm that a reversion of the Sundry menu changes in budgie-
desktop has no impact on this issue.

This is something very specific to the changes made gnome-menus - not
the ubuntu specific patches, but the debian modifications/upgrade

** Changed in: gnome-menus (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Ubuntu Budgie no longer shows any menu categories after the upgrade

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  After the upgrade, UB no longer displays any menu categories.

  I've recompiled the debian sid version and install the deb's.  That
  similarly does not work.

  Will try to revert the budgie-desktop Sundry menu category handling to
  see if that is the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-menus 3.31.4-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-0ubuntu19
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Jan 22 20:00:11 2019
  Dependencies:
   
  InstallationDate: Installed on 2019-01-21 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190121)
  SourcePackage: gnome-menus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1812903] Re: Please remove libproxy1-plugin-mozjs/s390x on disco

2019-01-22 Thread Jeremy Bicha

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

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

Title:
  Please remove libproxy1-plugin-mozjs/s390x on disco

Status in libproxy package in Ubuntu:
  New

Bug description:
  Please remove the NBS libproxy1-plugiin-mozjs from s390x.

  It does not show up on
  https://people.canonical.com/~ubuntu-archive/nbs.html

  But it does show at
  
https://people.canonical.com/~ubuntu-archive/proposed-migration/disco_uninst.txt

  The binary package is intentionally not built on s390x because mozjs60
  is not available on s390x currently.

  $ rmadison libproxy1-plugin-mozjs
   libproxy1-plugin-mozjs | 0.4.15-3 | disco/universe | s390x
   libproxy1-plugin-mozjs | 0.4.15-5 | disco/universe | amd64, arm64, armhf, 
i386, ppc64el

  $ rmadison libproxy
   libproxy | 0.4.15-2 | cosmic   | source
   libproxy | 0.4.15-5 | disco| source

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

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

[Desktop-packages] [Bug 1812903] [NEW] Please remove libproxy1-plugin-mozjs/s390x on disco

You have been subscribed to a public bug:

Please remove the NBS libproxy1-plugiin-mozjs from s390x.

It does not show up on
https://people.canonical.com/~ubuntu-archive/nbs.html

But it does show at
https://people.canonical.com/~ubuntu-archive/proposed-migration/disco_uninst.txt

The binary package is intentionally not built on s390x because mozjs60
is not available on s390x currently.

$ rmadison libproxy1-plugin-mozjs
 libproxy1-plugin-mozjs | 0.4.15-3 | disco/universe | s390x
 libproxy1-plugin-mozjs | 0.4.15-5 | disco/universe | amd64, arm64, armhf, 
i386, ppc64el

$ rmadison libproxy
 libproxy | 0.4.15-2 | cosmic   | source
 libproxy | 0.4.15-5 | disco| source

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


** Tags: bot-comment
-- 
Please remove libproxy1-plugin-mozjs/s390x on disco
https://bugs.launchpad.net/bugs/1812903
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to libproxy 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 1648183] Re: Crackling and popping sound when using headphones

2019-01-22 Thread MAI Anh Tuan

the solution of @robertjjoynt doesn't work on ubuntu 18.04
my pc is HP Pavilion Power 15CB
card 0: PCH [HDA Intel PCH], device 0: ALC295 Analog [ALC295 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

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

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

[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic

** Summary changed:

- MTP no more working on Bionic
+ MTP not working/very slow on Bionic

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

Title:
  MTP not working/very slow on Bionic

Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  Hi, unfortunately (for me) MTP android devices no more work on Ubuntu
  18.04.

  I have used MTP on 16.04 without problems, but on 18.04 it does not
  work. When I connect my Android devices (Samsung A5 and Samsung J3)
  and I try to list directories with many files (e.g. /DCIM/Camera) the
  window hangs until I disconnect the device. Same issue if I try to
  post the command "ls /var/run/1000/gvfs/".

  I have installed Ubuntu 18.04 on two different machines - an older HP
  laptop and a recent DELL laptop - and the issue is present on the all
  of them.

  I suspect a defect on the "libmtp". I tried many alternative solutions
  suggested by the net (e.g. jmtpfs and so on) but anyone worked.

  That's all!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-fuse 1.36.1-0ubuntu1.1
  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
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 06:20:07 2018
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1810211] Re: connected smartphone via usb MTP is very, very, very slow

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

** This bug has been marked a duplicate of bug 1792085
   MTP not working/very slow on Bionic

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

Title:
  connected smartphone via usb MTP is very, very, very slow

Status in nautilus package in Ubuntu:
  New

Bug description:
  Since Ubuntu 18.04 a connected smartphone via usb is very, very, very
  slow. If you want to copy some pictures from the smartphone to the
  computer you have to wait minutes for just list and show the names of
  the pictures. I tryed and tested this behaviour with Ubuntu 16.04 and
  there is no such failure. With Ubuntu 16.04 the connected smartphone
  works as expected, fast and reliable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu7
  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: Tue Jan  1 21:02:53 2019
  ExecutablePath: /usr/bin/nautilus
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1810086] Re: [SRU] Update to 0.18.1 in Bionic

Thanks for the report, we need to review the changes to see if those are
bugfixes only

** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  [SRU] Update to 0.18.1 in Bionic

Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  New

Bug description:
  0.18.1 is a bug-fix release and would be good to have it in Bionic
  LTS.

  * Bug fix and translation release
  - Use precise repeat one code rather than the previous estimate method
  - Fix laggy volume slider
  - Fix buggy click-to-seek
  - Use default GNOME Headerbar spacing

  It fixes the buggy seek slider.
  Steps to reproduce the bug in Bionic:
  1. Start Rhythmbox with alternative-toolbar enabled
  2. Play a track
  3. Drag the seek slider or click on it
  4. Use keyboard left & right buttons to seek
  5. Seeking does not work

  Version 0.18.1 fixes that bug among others.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1810086/+subscriptions

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

[Desktop-packages] [Bug 1812683] Re: rhythmbox crashes when trying to play music

The fix commited upstream looks like more a workaround, unsure it
qualifies for a SRU. Could you provide details on the gtk
call/api/functions that doesn't like the non english label? Maybe we can
come with a small python testcase and get the real gtk/binding issue
fixed instead?

(0.18.1 as a SRU is an option, is that version a bugfix only one? unsure
if the plugin has stable/unstable series?)

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

Title:
  rhythmbox crashes when trying to play music

Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  Confirmed

Bug description:
  Thread 1 "rhythmbox" received signal SIGSEGV, Segmentation fault.
  0x77183384 in gtk_tree_view_get_column ()
 from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  (gdb) bt
  #0  0x77183384 in gtk_tree_view_get_column () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #1  0x76ecd5fa in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #2  0x76ece792 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #3  0x76ecf445 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #4  0x7718d1fc in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #5  0x710bedae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
  #6  0x710be71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  #7  0x76be3ced in g_cclosure_marshal_generic_va () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #8  0x76be3346 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #9  0x76bfe9ff in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #10 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #11 0x7700f7fc in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #12 0x76be6008 in g_cclosure_marshal_VOID__BOXEDv () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #13 0x76be3346 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #14 0x76bfe9ff in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #15 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #16 0x7700c78e in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #17 0x7700dcdb in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #18 0x7701099e in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #19 0x76fde1e1 in gtk_event_controller_handle_event () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #20 0x7719d85b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #21 0x77b46642 in  () at 
/usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10
  #22 0x7705815b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #23 0x76be310d in g_closure_invoke () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #24 0x76bf605e in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #25 0x76bfe0af in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #26 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #27 0x7719fb04 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #28 0x770551ce in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #29 0x770572a8 in gtk_main_do_event () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #30 0x75323765 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #31 0x75353f82 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #32 0x76909387 in g_main_context_dispatch () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #33 0x769095c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #34 0x7690964c in g_main_context_iteration () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #35 0x737e7e3d in g_application_run () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #36 0x77aa0b09 in rb_application_run () at 
/usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10
  #37 0x4d57 in main ()

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 16:14:12 2019
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1812683/+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 1812101] Re: libreoffice-kde5 file dialog/picker doesn't add extension automatically

2019-01-22 Thread Bug Watch Updater

** Changed in: df-libreoffice
   Status: New => Confirmed

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.

  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.

  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension

  Actual Results:
  file are saved without .docx extension.

  Expected Results:
  file should be saved with the .docx extension

  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
  CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded

  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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

-- 
Mailing list: https://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 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed [Apple Macbook 2, 1 - Intel GMA 950]

2019-01-22 Thread Alexander A Theiler

Hey Daniel,

I've recorded two long hangs for you and your team to analyze.

Please find attached longhangprevboot.txt and longhangprevboot2.txt.

The only difference between the two is that longhangprevboot.txt followed
the following timeline:
normal mode -> restart to long hang -> restart to recovery mode and record
previous boot

Whereas, longhangprevboot2.txt followed the following:
normal mode -> restart to long hang -> restart to normal mode and record
previous boot

I let both of these boots hang for about 20 minutes before restarting the
machine.  Strangely, both logs don't seem to reflect that.  Unless they do,
and I simply didn't interpret the data correctly.  Ideas?

Thanks

Alex


On Mon, Jan 21, 2019 at 9:00 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Yes please for a new log.
>
> This bug is almost certainly fixable. We just need a complete log, and
> then a lot of patience to wait for some upstream developer to get around
> to figuring it out.
>
> If you can't wait and want to use the machine now then Lubuntu might be a
> better option:
>
> http://cdimage.ubuntu.com/lubuntu/releases/18.04/release/lubuntu-18.04.1-desktop-amd64.iso
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1811599
>
> Title:
>   When booting, the computer hangs at a purple screen and no login
>   prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After a fresh install of Ubuntu 18.04.1, on its first boot, the
>   computer hung at a purple screen.  No login prompt was ever displayed.
>   After holding the power button, the computer boot into Ubuntu without
>   difficulty.  I applied the workaround described in bug 1727356,
>   uncommenting WaylandEnable=False and rebooted the machine, but it
>   again hung at the purple screen.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.28.3-0ubuntu18.04.3
>   ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
>   Uname: Linux 4.15.0-43-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Jan 13 10:59:26 2019
>   InstallationDate: Installed on 2019-01-11 (2 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gdm3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+subscriptions
>


-- 
Alexander A Theiler, MHS, MS, PA-C
CAQ in Emergency Medicine


** Attachment added: "longhangprevboot.txt"
   
https://bugs.launchpad.net/bugs/1811599/+attachment/5231528/+files/longhangprevboot.txt

** Attachment added: "longhangprevboot2.txt"
   
https://bugs.launchpad.net/bugs/1811599/+attachment/5231529/+files/longhangprevboot2.txt

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

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]

Status in gdm3 package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Ubuntu 18.04.1, on its first boot, the
  computer hung at a purple screen.  No login prompt was ever displayed.
  After holding the power button, the computer boot into Ubuntu without
  difficulty.  I applied the workaround described in bug 1727356,
  uncommenting WaylandEnable=False and rebooted the machine, but it
  again hung at the purple screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 10:59:26 2019
  InstallationDate: Installed on 2019-01-11 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441

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

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

[Desktop-packages] [Bug 1812101]

2019-01-22 Thread Hans P Möller

Created attachment 148495
LO 6.2 Lubuntu 18.10 filepicker

Here it is screenshot of LO 6.2 with lubuntu 18.10. Filepicker doesn't
have the add extension checkbox

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.

  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.

  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension

  Actual Results:
  file are saved without .docx extension.

  Expected Results:
  file should be saved with the .docx extension

  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
  CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded

  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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

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

[Desktop-packages] [Bug 1812101]

2019-01-22 Thread Michael Weghorn

As your screenshots show, more custom controls are missing in the save
dialog when run on LXQt ("Save with password", "Encrypt with GPG key").

I just tested with LXQt on Debian testing and can confirm the behaviour
is the same with a current daily build of master and using the kde5 VCL
plugin. This is rather unfortunate, since kde5 is selected as the
default VCL plugin there...

All controls are there when using e.g. the gtk3 VCL plugin instead. Btw,
when using the plain qt5 VCL plugin, the controls are also there (but
the file extension is not added, regardless of whether the checkbox is
enabled...).

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.

  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.

  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension

  Actual Results:
  file are saved without .docx extension.

  Expected Results:
  file should be saved with the .docx extension

  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
  CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded

  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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

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

[Desktop-packages] [Bug 1812101]

2019-01-22 Thread Michael Weghorn

(In reply to Hans P. Möller from comment #7)
> Who creates the checkbox? Libreoffice or the filemanager (in kubuntu
> dolphin)?

A quick search suggests that kio is responsible for this in KDE Plasma,
s.
https://sources.debian.org/src/kio/5.51.0-1/src/filewidgets/kfilewidget.cpp/?hl=2312#L2312
(but I didn't have a closer look)

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.

  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.

  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension

  Actual Results:
  file are saved without .docx extension.

  Expected Results:
  file should be saved with the .docx extension

  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
  CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded

  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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

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

[Desktop-packages] [Bug 1812101]

2019-01-22 Thread Hans P Möller

(In reply to Michael Weghorn from comment #9)
> (In reply to Hans P. Möller from comment #7)
> > Created attachment 148473 [details]
> > lubuntu LXQt file saver
> 
> @Hans: Is that screenshot with LibreOffice 6.1 and the the gtk3_kde5 VCL
> plugin or with 6.2 and the kde4 one?
> 
> Btw, when using the "qt5" VCL plugin (i.e. starting LibreOffice with the env
> variable "SAL_USE_VCLPLUGIN=qt5" set), the checkbox is also there, but seems
> to have no effect, the file extension is not added.

with LO 6.1 and VCL=gtk3_kde5.
I havent been able to run 6.2 with VCL=kde5, only kde=4. But Olivier could and 
had the same issue.

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.

  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.

  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension

  Actual Results:
  file are saved without .docx extension.

  Expected Results:
  file should be saved with the .docx extension

  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
  CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded

  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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

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

[Desktop-packages] [Bug 1812101]

2019-01-22 Thread Michael Weghorn

(In reply to Hans P. Möller from comment #7)
> Created attachment 148473 [details]
> lubuntu LXQt file saver

@Hans: Is that screenshot with LibreOffice 6.1 and the the gtk3_kde5 VCL
plugin or with 6.2 and the kde4 one?

Btw, when using the "qt5" VCL plugin (i.e. starting LibreOffice with the
env variable "SAL_USE_VCLPLUGIN=qt5" set), the checkbox is also there,
but seems to have no effect, the file extension is not added.

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.

  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.

  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension

  Actual Results:
  file are saved without .docx extension.

  Expected Results:
  file should be saved with the .docx extension

  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
  CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded

  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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

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

[Desktop-packages] [Bug 1812881] Re: backup file (files ending in ~) visible in Desktop on disco, were correctly) hidden in cosmic and previous releases

The desktop is not handled by nautilus anymore, reassigning


** Package changed: nautilus (Ubuntu) => gnome-shell-extension-desktop-icons 
(Ubuntu)

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

Title:
  backup file (files ending in ~) visible in Desktop on disco, were
  correctly) hidden in cosmic and previous releases

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  Prior to disco, if I edited a file on my desktop with an editor such
  as emacs that created a backup file whose name ended in "~", then this
  file would be hidden from the Desktop view, which is arguably correct
  and useful behavior.

  In disco, the file is annoyingly visible on the desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 11:34:48 2019
  InstallationDate: Installed on 2019-01-02 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

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

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

[Desktop-packages] [Bug 1812883] Re: Desktop view flashes every time ~/Desktop changes, even if the changes are invisible

The desktop is not handled by nautilus anymore, reassigning


** Package changed: nautilus (Ubuntu) => gnome-shell-extension-desktop-icons 
(Ubuntu)

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Importance: Undecided => High

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

Title:
  Desktop view flashes every time ~/Desktop changes, even if the changes
  are invisible

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  All of the icons on my desktop visibly flash every time I change
  anything in the folder ~/Desktop, even if the change is not something
  that is visible on my desktop.

  For example, "touch ~/Desktop/.#foo".

  I mean, the icons that haven't changed should never flash at all, even
  if a change is made that _does_ affect the visible display -- only the
  things that are actually new or different should change their
  appearance, and everything else should remain the same and not flash.
  But at the very least, there should be no flash when there are no
  visible changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 11:38:30 2019
  InstallationDate: Installed on 2019-01-02 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

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

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

[Desktop-packages] [Bug 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive

Thanks!

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Triaged

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

Title:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100%
  CPU and 100% RAM for a while, making all the system unresponsive

Status in evolution-data-server package in Ubuntu:
  Triaged

Bug description:
  /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 
100% RAM for a while, making all the system unresponsive; the GUI doesn't 
respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it 
lasts for a few minutes, then goes back to normal.  
  If I wait long enough, the addressbook crashes (not enough memory ?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evolution-data-server 3.30.1-1build1
  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: GNOME
  Date: Sat Jan 19 09:59:18 2019
  ExecutablePath: 
/usr/lib/evolution/evolution-data-server/evolution-alarm-notify
  InstallationDate: Installed on 2017-01-09 (740 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago)

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

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

[Desktop-packages] [Bug 1812818] Re: Nautilus is not respecting the SGID when it copies directories

2019-01-22 Thread mirohe

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

ok, thanks. Sebastien

Other information if you can help:

- With the application Nemo has the same problem
- With the application Thunar works ok

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

Title:
  Nautilus is not respecting the SGID when it copies directories

Status in nautilus package in Ubuntu:
  New

Bug description:
  Hi,

  Both on ubuntu 16.04 and on ubuntu 18.04 have de same problem

  if I have a directory with the SGID activated and within this I create
  with the nautilus another directory inside, the latter has the SGID.

  But if I copy a directory from another place through the nautilus and
  paste it into the directory with SGID, the copied directory does not
  have the SGID.

  for example:

  home directory test:

  $> ls -l

  drwxr-sr-x  2 myuser mygroup   4096 ene 21 16:47  test

  Create a new directorio called "dir1" with nautilus into of test.
  Result:

  $> ls -l test

  drwxr-sr-x 2 myuser mygroup 4096 ene 21 17:09 dir1

  This is correct.

  =
  NOW
  =

  if I copy a directory from another place (for example /home/user/dir2)
  called "dir2" through the nautilus and paste it into the directory
  "test", the result is:

  $> ls -l test

  drwxrwsr-x 2 miguel.rodriguez miguel.rodriguez 4096 ene 21 17:09 dir1
  drwxrwxr-x 2 miguel.rodriguez miguel.rodriguez 4096 ene 21 17:12 dir2

  The directory dir2 not have "s" SUID in group user.

  
  If I do this from the command line without using nautilus it works correctly. 
example:

  $> cp -r /home/user/dir2 /home/user/test/.
  $> ls -l test

  drwxrwsr-x 2 miguel.rodriguez miguel.rodriguez 4096 ene 21 17:09 dir1
  drwxrwsr-x 2 miguel.rodriguez miguel.rodriguez 4096 ene 21 17:12 dir2

  this way it works

  
  Any more this happens?
  Since I can not open an issue, I do it here.

  Best Regards

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

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

[Desktop-packages] [Bug 1812885] Re: Rename shell script on desktop, nautilus keeps trying to execute it under its old name

The desktop is not handled by nautilus anymore, reassigning

** Package changed: nautilus (Ubuntu) => gnome-shell-extension-desktop-
icons (Ubuntu)

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

Title:
  Rename shell script on desktop, nautilus keeps trying to execute it
  under its old name

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  Create a shell script in /tmp. Make the script executable. Mv it into
  ~/Desktop. Double-click it and note that it executes. Now rename the
  file with mv in a terminal window. Double-click it again and note how
  nautilus attempts to execute it under the old name, which of course
  fails, and you get a notification about that instead of the script
  executing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 11:48:06 2019
  InstallationDate: Installed on 2019-01-02 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

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

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

[Desktop-packages] [Bug 1812880] Re: create shell script file on Desktop, chmod it so that it is executable, icon remains text file instead of shell script and won't launch on double-click

The desktop is not handled by nautilus anymore, reassigning


** Package changed: nautilus (Ubuntu) => gnome-shell-extension-desktop-icons 
(Ubuntu)

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

Title:
  create shell script file on Desktop, chmod it so that it is
  executable, icon remains text file instead of shell script and won't
  launch on double-click

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  Using a text editor, create a file on your Desktop that you intend to
  be a shell script. When you save it initially, it won't be executable
  (unless your text editor is too smart for its own good), so it will be
  displayed on the desktop as a text file.

  Now do "chmod +x" on the file in a terminal window.

  It's still displayed on the desktop as a text file, and you still
  can't execute it.

  Now mv it out of your desktop and into /tmp, and then mv it back onto
  your desktop. Now the icon is displayed as a shell script and can be
  double-clicked.

  The icon for a file on the desktop should turn from text file to
  executable script as soon as the file itself turns from text file to
  executable script.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 11:30:45 2019
  InstallationDate: Installed on 2019-01-02 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

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

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

[Desktop-packages] [Bug 1812865] Re: Extracting an archive by right-clicking and selecting "Extract here" results in many extracted files to be 0 bytes in size

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

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

Title:
  Extracting an archive by right-clicking and selecting "Extract here"
  results in many extracted files to be 0 bytes in size

Status in nautilus package in Ubuntu:
  New

Bug description:
  Download the linux-x64 zip from here
  (https://github.com/JustArchiNET/ArchiSteamFarm/releases/tag/3.4.2.2)
  to test. Extracting works fine with the unzip command. I am not aware
  of this bug occurring with zips different from the one provided.

  Ubuntu 18.10

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

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

[Desktop-packages] [Bug 1812884] Re: Can't execute shell scripts with spaces in their names from desktop

The desktop is not handled by nautilus anymore, reassigning


** Package changed: nautilus (Ubuntu) => gnome-shell-extension-desktop-icons 
(Ubuntu)

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Can't execute shell scripts with spaces in their names from desktop

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  Create a shell script with a space in its name in /tmp. Make sure the
  script is executable. Mv it into ~/Desktop. (You have to do it this
  way rather than creating it directly on the desktop because of the
  other bug I just filed.) Try to double-click on it. You will get an
  error notification instead of the script executing. Shell scripts
  added to the desktop in this way without spaces in their names do not
  have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 11:44:14 2019
  InstallationDate: Installed on 2019-01-02 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

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

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

[Desktop-packages] [Bug 1812908] [NEW] Ubuntu Budgie no longer shows any menu categories after the upgrade

2019-01-22 Thread fossfreedom

Public bug reported:

After the upgrade, UB no longer displays any menu categories.

I've recompiled the debian sid version and install the deb's.  That
similarly does not work.

Will try to revert the budgie-desktop Sundry menu category handling to
see if that is the issue.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-menus 3.31.4-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-0ubuntu19
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Tue Jan 22 20:00:11 2019
Dependencies:
 
InstallationDate: Installed on 2019-01-21 (1 days ago)
InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190121)
SourcePackage: gnome-menus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

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

Title:
  Ubuntu Budgie no longer shows any menu categories after the upgrade

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  After the upgrade, UB no longer displays any menu categories.

  I've recompiled the debian sid version and install the deb's.  That
  similarly does not work.

  Will try to revert the budgie-desktop Sundry menu category handling to
  see if that is the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-menus 3.31.4-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-0ubuntu19
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Jan 22 20:00:11 2019
  Dependencies:
   
  InstallationDate: Installed on 2019-01-21 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190121)
  SourcePackage: gnome-menus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1809129] Re: Window previews have inconsistent ordering

The change was reverted from the bionic SRU with
https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/0.9.1ubuntu18.04.3 since it was decided that behaviour changes is
probably not a good idea for the SRU

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Bionic)
   Status: Fix Committed => Won't Fix

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

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

Title:
  Window previews have inconsistent ordering

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Bionic:
  Won't Fix

Bug description:
  Upstream bug:  https://github.com/micheleg/dash-to-dock/issues/639

  The window previews available in d-2-d change order so that the most
  recently used one is always at the top.  This causes confusion as the
  window which was at the bottom last time you clicked on the icon is
  now at the top.

  This has been fixed upstream to keep the previews in the same order
  that the windows were created.

  [ Impact ]

  Windows previews in ubuntu dock change order so that the top one is
  always the most recently used, causing confusion.

  [ Test case ]

  - Open two window instances of a program (say, nautilus)
  - Click in the ubuntu dock icon to select the window to focus
  - Choose one at the bottom
  - Click again in the dock icon
  - The one that was at the bottom before (and now focused) should still be in 
the
same position

  [ Regression potential ]

  No windows in popup selector could be visible at all

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

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

[Desktop-packages] [Bug 1807460] Re: Filenames with spaces not accepted when connecting to certificate-authenticated wifi

This bug was fixed in the package network-manager-applet -
1.8.10-2ubuntu2

---
network-manager-applet (1.8.10-2ubuntu2) bionic; urgency=medium

  * debian/patches/git_certificate_escaping.patch:
- 'libnma: unescape certificate paths in URIs', that fixes
   selecting files with a space in their name (lp: #1807460)

 -- Sebastien Bacher   Tue, 11 Dec 2018 17:26:44
+0100

** Changed in: network-manager-applet (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Filenames with spaces not accepted when connecting to certificate-
  authenticated wifi

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Bionic:
  Fix Released

Bug description:
  * Impact
  Using an authentification certificate with a filename in its name is not 
possible

  * Test case
  - connect to a wpa wifi needing a certificate
  - name the certificate to include a space
  - try to use that said certificate

  it should be possible to use it

  * Regression potential
  the change is on the function dealing with the filename/uri for certificate, 
make sure those keep working on different locations with names including spaces 
or not

  
  ***

  
  This bug was encountered on a fresh install of Ubuntu 18.04.1 LTS

  When connecting to a certificate-authenticated wifi network (WPA/WPA2
  Enterprise, authentication TLS) for the first time, the "Wi-Fi Network
  Authentication Required" dialogue is displayed, prompting the user to
  select their CA and user certificates.

  Unexpected behaviour: If any of the files have spaces in their
  filenames, after choosing them in the file picker the field is
  highlighted by a red box, and the 'Connect' button is greyed out.

  This is depicted in the attachment network-authentication-red-box-
  spaces-filename.png

  There is also no explanation offered for why the red box highlight is
  present - no tooltip, no help from pressing F1, no popup, and as far
  as I can find no logs.

  If you move/rename the file, so there are no spaces in the filename,
  the problem is worked around.

  The problem is not present on the edit connection dialogue; filenames
  with spaces are acceptable there.

  The problem was also not present on Ubuntu 16.04, and users who
  upgrade from 16.04 to 18.04 will find their connection keeps working.
  It is only when creating an entirely new connection (or after
  forgetting the connection and recreating it) that the problem dialog
  appears.

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

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

[Desktop-packages] [Bug 1807460] Update Released

The verification of the Stable Release Update for network-manager-applet
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Filenames with spaces not accepted when connecting to certificate-
  authenticated wifi

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Bionic:
  Fix Released

Bug description:
  * Impact
  Using an authentification certificate with a filename in its name is not 
possible

  * Test case
  - connect to a wpa wifi needing a certificate
  - name the certificate to include a space
  - try to use that said certificate

  it should be possible to use it

  * Regression potential
  the change is on the function dealing with the filename/uri for certificate, 
make sure those keep working on different locations with names including spaces 
or not

  
  ***

  
  This bug was encountered on a fresh install of Ubuntu 18.04.1 LTS

  When connecting to a certificate-authenticated wifi network (WPA/WPA2
  Enterprise, authentication TLS) for the first time, the "Wi-Fi Network
  Authentication Required" dialogue is displayed, prompting the user to
  select their CA and user certificates.

  Unexpected behaviour: If any of the files have spaces in their
  filenames, after choosing them in the file picker the field is
  highlighted by a red box, and the 'Connect' button is greyed out.

  This is depicted in the attachment network-authentication-red-box-
  spaces-filename.png

  There is also no explanation offered for why the red box highlight is
  present - no tooltip, no help from pressing F1, no popup, and as far
  as I can find no logs.

  If you move/rename the file, so there are no spaces in the filename,
  the problem is worked around.

  The problem is not present on the edit connection dialogue; filenames
  with spaces are acceptable there.

  The problem was also not present on Ubuntu 16.04, and users who
  upgrade from 16.04 to 18.04 will find their connection keeps working.
  It is only when creating an entirely new connection (or after
  forgetting the connection and recreating it) that the problem dialog
  appears.

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

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

[Desktop-packages] [Bug 1743976] Please test proposed package

Hello Daniel, or anyone else affected,

Accepted gnome-shell-extension-ubuntu-dock into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/0.9.1ubuntu18.04.3 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

Title:
  gnome-shell is wasting CPU repainting unchanging panels

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Bionic:
  Fix Committed

Bug description:
  gnome-shell is wasting CPU repainting an unchanging panel and dock.
  Every time an app window changes all visible actors including the
  panel get repainted. But the panels mostly doesn't change, so should
  be cached via offscreen-redirect instead.

  [ Impact ]

  Ubuntu dock repaints the dock when a window changes

  [ Test case ]

  - Maximize a window
  - Change its content, by acting on it
  - Monitor gnome-shell CPU usage, and it should be lower than using previous 
dock version

  [ Possible regression ]

  The dock isn't repainted properly or it could produce artifacts in
  some scenarios

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

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

[Desktop-packages] [Bug 1769383] Please test proposed package