date:20190624

@andreas oops I think I got muddled up, sorry about that! I'm going to
unsub from this bug (which I should have done earlier).

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs:
  Unknown
Status in samba:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Released
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Fix Released
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine that shows up in
  the network browsing, and then check with "smbstatus" which version of
  the protocol was used when connecting to an actual share.

  ---

  Nautilus should show smbtree and host on the smb network.

  When inputing this command:
  killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse

  You can

[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

So... any word on this bug? :S Still getting it.

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.
  smb: \> dir
.   D0  Fri May  3 18:16:38 2019
..  D0  Fri May  3 18:15:24 2019
hello.txt   N   21  Fri May  3 18:16:12 2019
hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

  20509264 blocks of size 1024. 13121800 blocks
  available

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

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

[Desktop-packages] [Bug 1511832] Re: Totem global menu drop down options GUI buggy display

[Expired for One Hundred Papercuts because there has been no activity
for 60 days.]

** Changed in: hundredpapercuts
   Status: Incomplete => Expired

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

Title:
  Totem global menu drop down options GUI buggy display

Status in One Hundred Papercuts:
  Expired
Status in Totem:
  Incomplete
Status in totem package in Ubuntu:
  Expired

Bug description:
  When playing videos with single audio track (most videos), if you go
  to the "View>Languages>" you can see the bug. It does not show empty.
  Only a thin black horizontal line with shadow appears. The screenshot
  is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: totem 3.16.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 31 00:59:31 2015
  InstallationDate: Installed on 2012-06-22 (1225 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: totem
  UpgradeStatus: Upgraded to wily on 2015-10-29 (1 days ago)

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

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

[Desktop-packages] [Bug 1375400] Re: totem gets stuck

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

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

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

Title:
  totem gets stuck

Status in totem package in Ubuntu:
  Expired

Bug description:
  I run totem and then open a file.  It then gets stuck and does not play the 
file.
  A lot of the time it works and if it does work, then totem never seems to 
have a problem with subsequent files.
  The issue is always with the first file opened it seems

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: totem 3.10.1-1ubuntu4
  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: Mon Sep 29 19:07:25 2014
  InstallationDate: Installed on 2011-07-29 (1158 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (45 days ago)

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

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

[Desktop-packages] [Bug 1494334] Re: tried to open video player but it doesn't open at all no launch error nothing

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

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

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

Title:
  tried to open video player but it doesn't open at all no launch error
  nothing

Status in totem package in Ubuntu:
  Expired

Bug description:
  I have tried to play an mp4 video using the default video player . I
  always prefer defaults over third party but it doesn't open at all .
  The mouse ticker shows loading but after a few moments nothing loads
  at all just like I didn't tried to open anything .

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: totem 3.10.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic i686
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: i386
  Date: Thu Sep 10 19:50:50 2015
  InstallationDate: Installed on 2015-09-08 (1 days ago)
  InstallationMedia: It
  SourcePackage: totem
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1511832] Re: Totem global menu drop down options GUI buggy display

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

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

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

Title:
  Totem global menu drop down options GUI buggy display

Status in One Hundred Papercuts:
  Expired
Status in Totem:
  Incomplete
Status in totem package in Ubuntu:
  Expired

Bug description:
  When playing videos with single audio track (most videos), if you go
  to the "View>Languages>" you can see the bug. It does not show empty.
  Only a thin black horizontal line with shadow appears. The screenshot
  is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: totem 3.16.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 31 00:59:31 2015
  InstallationDate: Installed on 2012-06-22 (1225 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: totem
  UpgradeStatus: Upgraded to wily on 2015-10-29 (1 days ago)

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

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

[Desktop-packages] [Bug 1825919] Re: Gedit right click context menu stops working

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

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

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

Title:
  Gedit right click context menu stops working

Status in gedit package in Ubuntu:
  Expired

Bug description:
  The Gedit text area right-click context menu stops appearing.

  This bug affects Ubuntu 19.04, but may be a regression of old Bug
  #1731581 from Ubuntu 17.10.

  Gedit version: 3.32.0-3
  Fresh install of Ubuntu 19.04
  gkt-3 version: 3.24.8-1ubuntu1

  RECREATING ISSUE

  When I first log in, the right-click context menus in Gedit works fine.
  After some time of usage, the right-click context menu no longer appears.

  SIDE-EFFECT

  A side-effect of this issue is that the mouse cursor does not revert
  to a pointer style after doing a right-click. It retains the "I"
  (Insert) shape even when you hover outside Gedit's text area.

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

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

[Desktop-packages] [Bug 1826196] Re: The Dock cannot scroll without a mouse when multiple programs are open

[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there
has been no activity for 60 days.]

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

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

Title:
  The Dock cannot scroll without a mouse when multiple programs are open

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

Bug description:
  This only happened after upgrading to 19.04.

  Everything works fine if i attach a mouse to my laptop. But without it
  i cannot scroll through the programs because my touchpad does not have
  a built-in side scroller.

  All was fine with Ubuntu 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 12:51:20 2019
  InstallationDate: Installed on 2018-06-12 (315 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to disco on 2019-04-20 (3 days ago)
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1633572] Re: video not playing

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

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

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

Title:
  video not playing

Status in totem package in Ubuntu:
  Expired

Bug description:
  I have faced the problem several times, video not playing, shows read i/o 
error.
  Also file copy to usb drive problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: totem 3.10.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-98-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Oct 14 23:16:58 2016
  InstallationDate: Installed on 2016-08-25 (50 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1812563] Re: The Chromium window is corrupted only on initial startup.

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

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  The Chromium window is corrupted only on initial startup.

Status in Ubuntu Manual Tests:
  Invalid
Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  The Chromium window is corrupted only on it's first launch. Both on VM
  and acer laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1812563/+subscriptions

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

[Desktop-packages] [Bug 1826310] Re: display driver issue

[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  display driver issue

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

Bug description:
  display driver issue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Apr 25 09:24:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [103c:3397]
  InstallationDate: Installed on 2013-12-07 (1964 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=e586694b-5243-4be0-924c-d519be6aa981 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.90
  dmi.board.asset.tag: INA346Z6BB
  dmi.board.name: 3397
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: INA346Z6BB
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq Elite 8300 SFF
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.98+git1904191830.be3b07~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1~git1904241930.09e477~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.1~git1904241930.09e477~oibaf~b
  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:19.0.1+git1903191930.36703f~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1903011933.6afed3~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.16+git1904230730.ec2b45~oibaf~b
  xserver.bootTime: Sat Feb 23 19:10:12 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1826310/+subscriptions

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

[Desktop-packages] [Bug 1834053] Re: [Inspiron 3558] PCI/internal sound card not detected

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1820794, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- PCI/internal sound card not detected
+ [Inspiron 3558] PCI/internal sound card not detected

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

** This bug has been marked a duplicate of bug 1820794
   [Dell Inspiron 3558] PCI/internal sound card not detected

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

Title:
  [Inspiron 3558] PCI/internal sound card not detected

Status in linux package in Ubuntu:
  New

Bug description:
  No sound as my pc does not detect sound hardware

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', 
'/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jun 24 20:39:45 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2016-11-06 (960 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to xenial on 2019-06-24 (0 days ago)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0XCR91
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/06/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 3558
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1834112] Re: the mouse stopped responding to commands

1. Which mouse is having the problem? You seem to have at least two mice
connected.

2. Please remove these from your kernel command line options:

   drm.debug=0xe plymouth:debug

   and then reboot.

3. Wait for the problem to happen again and then please immediately run:

   dmesg > newdmesg.txt

   and send us the file 'newdmesg.txt'.


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

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

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

Title:
  the mouse stopped responding to commands

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  the mouse stopped responding to commands

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-24-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Jun 24 21:21:31 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335]
  InstallationDate: Installed on 2019-03-27 (89 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406
  dmi.board.name: P5N-E SLI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Apr 24 21:29:22 2019

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

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

[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

---> bug 1834058 now

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released

Bug description:
  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913

  [ Impact ]

  Keyboard Layout indicator don't display current layout (empty selected
  drop down box)

  [ Test case ]

  1. Boot
  2. Suspend or lock the screen
  3. Log again with your user
  4. The keyboard indicator should display current layout

  [ Regression Potential ]

  Really low, we properly pass a null value instead of an undefined one,
  without breaking JS.

  --

  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  [ Workarounds ]

  - Switch with keyboard (Super+space) or mouse. BUT if you then logout
  on the login screen *when you press the first character* of the
  password the shown selected keyboard layout resets.

  - Restart Gnome Shell (Alt+F2 r):
  https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
     Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
     Card-2: NVIDIA GM108M [GeForce 940M]
     Display Server: x11 (X.Org 1.19.6 )
     drivers: fbdev (unloaded: modesetting,vesa)
     Resolution: 1920x1080@60.00hz
     OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
     version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
     System Locale: LANG=en_US.UTF-8
    LC_NUMERIC=es_AR.UTF-8
    LC_MONETARY=es_AR.UTF-8
    LC_PAPER=es_AR.UTF-8
    LC_NAME=es_AR.UTF-8
    LC_ADDRESS=es_AR.UTF-8
    LC_TELEPHONE=es_AR.UTF-8
    LC_MEASUREMENT=es_AR.UTF-8
    LC_IDENTIFICATION=es_AR.UTF-8
     VC Keymap: n/a
    X11 Layout: es
     X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

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

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

[Desktop-packages] [Bug 1834058] Re: Keyboard layout indicator vanishes after Suspend or Screenlock

Just in case it is related, please try UNINSTALLING these extensions and
then reboot:

'gnom...@panacier.gmail.com'
'activities-config@nls1729'
'dash-to-d...@micxgx.gmail.com'
'appindicatorsupp...@rgcjonas.gmail.com'
'apps-m...@gnome-shell-extensions.gcampax.github.com'
'background-l...@marketing.fedoraproject.org'
'caffe...@patapon.info'
'lockk...@vaina.lt'

We find a lot of bugs are caused by extensions.

** Tags added: resume suspend-resume

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

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

Title:
  Keyboard layout indicator vanishes after Suspend or Screenlock

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Related to bug 1812266.

  lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  apt-cache policy gnome-shell
  gnome-shell:
  installed: 3.28.4-0ubuntu18.04.1

  After Suspend or Screenlock ...

  What you expected to happen:
  Keyboard layout indicator should be visible all the time.

  What happened instead:
  not visible anymore

  Current manual fix:
  Press SUPER
  give search field the focus
  Press SUPER+Spacebar several times until current keyboard layout is selected.
  Keyboard layout indicator is visible again with current layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 24 17:40:12 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-07-20 (339 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1834110] Re: Broken lock-screen wallpaper, stutter after resuming from hibernation

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1834110

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

Title:
  Broken lock-screen wallpaper, stutter after resuming from hibernation

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Very similar to Bug #1809407
  (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407).

  I set up my swap partition and tested hibernation on 19.04 /w Nvidia
  drivers.

  Basically I observed 2 things:
  - Lock screen wallpaper gone (black screen with clock), same as with #1809407
  - Desktop wallpaper seems okay
  - Big frame rate drops (despite performance governor), everything seems quite 
laggy

  I'm new to Linux/Ubuntu, if you need any logs please tell me the
  commands and I will attach them.

  Thanks

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

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

[Desktop-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes

The above log looks like a kernel issue (if not a hardware issue).


** Package changed: libinput (Ubuntu) => linux (Ubuntu)

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

Title:
  Bluetooth touchpad (Apple Magic Trackpad) disconnects every few
  minutes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently got an Apple's Magic Trackpad. I paired it with Ubuntu
  18.04.2 LTS and worked out of the box, no special drivers needed.

  However, I experience frequent disconnections that last a few seconds
  (5-15 seconds usually), which are quite annoying, as the cursor stops
  responding during that interval. The trackpad connects by itself after
  that period. That usually happens every 20-40 minutes.

  I use the onboard bluetooth device of my laptop. I also have, at the
  same time, two more bluetooth devices (keyboard and mouse) and they do
  not experience that issue, just the trackpad. On ocassion I use
  bluetooth headphones which work just fine.

  First of all:

  Using the command "bluetoothctl" I get the following every time I
  experience a disconnection:

  [CHG] Device F4:1B:A1:33:F9:8D Connected: no
  [CHG] Device F4:1B:A1:33:F9:8D Connected: yes

  Checking "dmesg" I can see more information: (if I am not mistaken,
  this shows 4 disconnections)

  
  [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0
  [ 1609.070797] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23
  [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 1676.917377] NET: Registered protocol family 38
  [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0
  [ 1872.815559] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24
  [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0
  [ 3101.683100] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0
  [ 3110.683929] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26
  [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98

  
  And this is what journalctl -b shows at the moment of the 
disconnection/reconnection:

  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: removing device Apple Wireless Trackpad
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option 
"fd" "64" (1,63 m)˜
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - 
Apple Wireless Trackpad: device removed
  de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 
'array' failed
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
UnloadModule: "libinput"
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
systemd-logind: releasing fd for 13:80
  de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown 
main item tag 0x0
  de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: 
input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 
64:5d:86:86:3f:98
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1)
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input 
driver specified, ignoring this device.
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This 
device may have been added with another device file.
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16)
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple 
Wireless Trackpad: Applying InputClass "libinput touchpad catchall"

[Desktop-packages] [Bug 1834047] Re: External monitor not recognised

> I have BenQ i do not know what number, but it is connected by HDMI to
DVI cable.

Does that mean you are trying to connect two monitors or only one?
Because the system is recognising one 1920x1080 monitor on a
DisplayPort.

** Tags added: nvidia

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-418
(Ubuntu)

** Changed in: nvidia-graphics-drivers-418 (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/1834047

Title:
  External monitor not recognised

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Incomplete

Bug description:
  I have BenQ i do not know what number, but it is connected by HDMI to DVI 
cable.
   nvidia-driver-418 is version 418.56-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 24 16:20:03 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   als, master, 5.0.0-16-generic, x86_64: installed
   als, master, 5.0.0-17-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-16-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] (P1000 
[Zbook 17 G5 mobile workstation]) [103c:842f]
  MachineType: HP HP ZBook 17 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic 
root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q70 Ver. 01.07.00
  dmi.board.name: 842D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 15.37.00
  dmi.chassis.asset.tag: 5CD8501DGX
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ70Ver.01.07.00:bd04/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.37.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook 17
  dmi.product.name: HP ZBook 17 G5
  dmi.product.sku: 4QH25EA#BCM
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1833617] Re: [amdgpu] screen freeze after suspend

Recovery mode should work, but that does sound like a different bug.

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

Title:
  [amdgpu] screen freeze after suspend

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

Bug description:
  It's most likely amdgup driver needs an upgrade. Problem occurs since
  kernel upgrade to 5.0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jun 20 13:46:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
 Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
  InstallationDate: Installed on 2019-06-06 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. Inspiron 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic 
root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1834032] Re: loosing wificontact

You say:

* Often I receive the message : Problem in ubunt, do you want to send
the messaage?

* Often my laptop (Dell Latitude) looses contact with wifi, only to be
repaired by restarting the computer.

But those are two separate issues. Please choose one issue you would
like this bug to be about.

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

Title:
  loosing wificontact

Status in Ubuntu:
  Incomplete

Bug description:
  Often I receive the message : Problem in ubunt, do you want to send the 
messaage?
  Often my laptop (Dell Latitude) looses contact with wifi, only to be repaired 
by restarting the computer.
  This happens for all after changing a user and a moment of computersleep

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun 24 15:02:44 2019
  DistUpgraded: 2019-05-03 22:15:55,047 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0492]
  InstallationDate: Installed on 2019-05-01 (53 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Latitude E6320
  ProcEnviron:
   LANGUAGE=nl
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=cf82673b-3d94-436d-9879-0993332233ff ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-05-03 (51 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0GJF11
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn0GJF11:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6320
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.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

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

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

[Desktop-packages] [Bug 1834110] Re: Broken lock-screen wallpaper, stutter after resuming from hibernation

2019-06-24 Thread Aleksandar Palic

** Description changed:

  Very similar to Bug #1809407
  (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407).
  
- I set up my swap partition and tested hibernation on 19.04.
+ I set up my swap partition and tested hibernation on 19.04 /w Nvidia
+ drivers.
  
  Basically I observed 2 things:
  - Lock screen wallpaper gone (black screen with clock), same as with #1809407
  - Desktop wallpaper seems okay
  - Big frame rate drops (despite performance governor), everything seems quite 
laggy
  
  I'm new to Linux/Ubuntu, if you need any logs please tell me the
  commands and I will attach them.
  
  Thanks

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

Title:
  Broken lock-screen wallpaper, stutter after resuming from hibernation

Status in mutter package in Ubuntu:
  New

Bug description:
  Very similar to Bug #1809407
  (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407).

  I set up my swap partition and tested hibernation on 19.04 /w Nvidia
  drivers.

  Basically I observed 2 things:
  - Lock screen wallpaper gone (black screen with clock), same as with #1809407
  - Desktop wallpaper seems okay
  - Big frame rate drops (despite performance governor), everything seems quite 
laggy

  I'm new to Linux/Ubuntu, if you need any logs please tell me the
  commands and I will attach them.

  Thanks

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

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

[Desktop-packages] [Bug 1834110] [NEW] Broken lock-screen wallpaper, stutter after resuming from hibernation

2019-06-24 Thread Aleksandar Palic

Public bug reported:

Very similar to Bug #1809407
(https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407).

I set up my swap partition and tested hibernation on 19.04.

Basically I observed 2 things:
- Lock screen wallpaper gone (black screen with clock), same as with #1809407
- Desktop wallpaper seems okay
- Big frame rate drops (despite performance governor), everything seems quite 
laggy

I'm new to Linux/Ubuntu, if you need any logs please tell me the
commands and I will attach them.

Thanks

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

** Summary changed:

- Corrupted wallpaper after resuming from hibernation
+ Broken lock-screen wallpaper, stutter after resuming from hibernation

** Description changed:

  Very similar to Bug #1809407
  (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407).
+ 
+ I set up my swap partition and tested hibernation on 19.04.
  
  Basically I observed 2 things:
  - Lock screen wallpaper gone (black screen with clock), same as with #1809407
  - Desktop wallpaper seems okay
  - Big frame rate drops (despite performance governor), everything seems quite 
laggy
  
  I'm new to Linux/Ubuntu, if you need any logs please tell me the
  commands and I will attach them.
  
  Thanks

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

Title:
  Broken lock-screen wallpaper, stutter after resuming from hibernation

Status in mutter package in Ubuntu:
  New

Bug description:
  Very similar to Bug #1809407
  (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407).

  I set up my swap partition and tested hibernation on 19.04.

  Basically I observed 2 things:
  - Lock screen wallpaper gone (black screen with clock), same as with #1809407
  - Desktop wallpaper seems okay
  - Big frame rate drops (despite performance governor), everything seems quite 
laggy

  I'm new to Linux/Ubuntu, if you need any logs please tell me the
  commands and I will attach them.

  Thanks

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

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

[Desktop-packages] [Bug 1834112] [NEW] the mouse stopped responding to commands

2019-06-24 Thread Louis Peutzen

Public bug reported:

the mouse stopped responding to commands

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-24-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Mon Jun 24 21:21:31 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335]
InstallationDate: Installed on 2019-03-27 (89 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/18/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406
dmi.board.name: P5N-E SLI
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Apr 24 21:29:22 2019

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


** Tags: amd64 apport-bug bionic 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/1834112

Title:
  the mouse stopped responding to commands

Status in xorg package in Ubuntu:
  New

Bug description:
  the mouse stopped responding to commands

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-24-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Jun 24 21:21:31 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335]
  InstallationDate: Installed on 2019-03-27 (89 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406
  dmi.board.name: P5N-E SLI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati:

[Desktop-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's

This bug was fixed in the package xorg-server - 2:1.19.6-1ubuntu4.3

---
xorg-server (2:1.19.6-1ubuntu4.3) bionic; urgency=medium

  * sync-i965-pciids.diff: Updated with Comet Lake id's. (LP: #1821863)

 -- Timo Aaltonen   Fri, 31 May 2019 14:10:48 +0300

** Changed in: xorg-server (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Need to add Intel CML related pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released
Status in mesa source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Please make it happen in the coming oem-kernel as there will be a
  flood of Intel Comet Lake (CML) platforms that would need it. Thank
  you.

  The same is needed for the rest of the stack.

  CML is basically another iteration of Skylake/Kabylake/Coffee Lake,
  and doesn't need other changes than pci-id's and support for the PCH
  (similar to Cannon point, already supported by the kernel).

  [Test case]

  Test that i915 graphics works on CML.

  [Regression potential]

  None really, these only add a bunch of new pci-id's across the stack.

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

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

[Desktop-packages] [Bug 1821863] Update Released

2019-06-24 Thread Steve Langasek

The verification of the Stable Release Update for xorg-server 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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1821863

Title:
  Need to add Intel CML related pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Committed
Status in libdrm source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released
Status in mesa source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Please make it happen in the coming oem-kernel as there will be a
  flood of Intel Comet Lake (CML) platforms that would need it. Thank
  you.

  The same is needed for the rest of the stack.

  CML is basically another iteration of Skylake/Kabylake/Coffee Lake,
  and doesn't need other changes than pci-id's and support for the PCH
  (similar to Cannon point, already supported by the kernel).

  [Test case]

  Test that i915 graphics works on CML.

  [Regression potential]

  None really, these only add a bunch of new pci-id's across the stack.

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

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

[Desktop-packages] [Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes

This bug was fixed in the package gnome-control-center -
1:3.18.2-1ubuntu6.1

---
gnome-control-center (1:3.18.2-1ubuntu6.1) xenial; urgency=medium

  * debian/patches/correct-value-of-90-minutes-to-5400.patch:
- correct the value of 90 minutes to 5400 (LP: #1827346)

 -- Ethan Hsieh   Fri, 03 May 2019 11:14:24
+0800

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

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

Title:
  Power: Fail to set delay time when the value is 90 minutes

Status in OEM Priority Project:
  Fix Committed
Status in OEM Priority Project bionic series:
  Fix Committed
Status in OEM Priority Project xenial series:
  Fix Committed
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Xenial:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Fail to set delay time when the value is 90 minutes.

  In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not
  5400 (90*60). When setting the delay time to 90 minutes, the UI will
  show "80 minutes" after reopening "All Settings". (Please refer to the
  photo in #1 and #2)

  [Test Case]

  1) Go to [All Settings][Power][Automatic suspend]

  2) Set delay time to 90 minutes (On Battery Power or Plugged in)

  3) Close [All Settings]

  4) Reopen [All Settings][Power][Automatic suspend]

  5) Check if the value is 90 minutes.

  [Regression Potential]

  Low. The value of 90 minutes is wrong. Just correct the value to 5400.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions

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

[Desktop-packages] [Bug 1834096] [NEW] package lirc 0.10.1-5.2 failed to install/upgrade: o subprocesso instalado, do pacote lirc, o script post-installation retornou erro do status de saída 1

2019-06-24 Thread Flavio Castro

Public bug reported:

Very bugs!!! Quando digito em um site quaisquer a digitação é cancelada!
Aí tenho que ficar clicando a todo instante na linha de digitação para
que o cursor se firme na linha e eu consiga escrever todo o conteúdo que
desejo! É horrível isto! Help me

ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: lirc 0.10.1-5.2
ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
Uname: Linux 5.0.0-17-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
Date: Mon Jun 24 15:47:51 2019
ErrorMessage: o subprocesso instalado, do pacote lirc, o script 
post-installation retornou erro do status de saída 1
InstallationDate: Installed on 2019-06-24 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
RelatedPackageVersions:
 dpkg 1.19.6ubuntu1
 apt  1.8.1
SourcePackage: lirc
Title: package lirc 0.10.1-5.2 failed to install/upgrade: o subprocesso 
instalado, do pacote lirc, o script post-installation retornou erro do status 
de saída 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package disco

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

Title:
  package lirc 0.10.1-5.2 failed to install/upgrade: o subprocesso
  instalado, do pacote lirc, o script post-installation retornou erro do
  status de saída 1

Status in lirc package in Ubuntu:
  New

Bug description:
  Very bugs!!! Quando digito em um site quaisquer a digitação é
  cancelada! Aí tenho que ficar clicando a todo instante na linha de
  digitação para que o cursor se firme na linha e eu consiga escrever
  todo o conteúdo que desejo! É horrível isto! Help me

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: lirc 0.10.1-5.2
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Mon Jun 24 15:47:51 2019
  ErrorMessage: o subprocesso instalado, do pacote lirc, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2019-06-24 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.6ubuntu1
   apt  1.8.1
  SourcePackage: lirc
  Title: package lirc 0.10.1-5.2 failed to install/upgrade: o subprocesso 
instalado, do pacote lirc, o script post-installation retornou erro do status 
de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1777285] Re: Batch libreoffice --convert-to offers no way to wait for document completion

Launchpad has imported 10 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=117731.

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


On 2018-05-21T20:25:17+00:00 Richard Elkins wrote:

Description:
Command-line: libreoffice --headless --convert-to odt:writer8 myfile.txt
The returned status code ($?) is zero.  So far, so good.
But, when I try to use the ODT file (E.g. copy it), it doesn't exist yet.
Yes, I tried `sync; sync; sync` but it did not help.
If I add a `sleep 1` immediately after checking the status code, then this 
seems to allow enough time for some libreoffice subprocess (?) to finish.

Before version 6, I did not need the sleep step.  Maybe, this is some
sort of optimization?  If so, please provide an option to indicate that
libreoffice should hold up the process until the desired output is
available.

I am using libreoffice 1:6.0.3-0ubuntu1 on Xubuntu 18.04.

`libreoffice --help` shows: 
LibreOffice 6.0.3.2 00m0(Build:2)


Steps to Reproduce:
Linux batch script, starting with an existing text file called "myfile.txt":

libreoffice --headless --convert-to odt:writer8 myfile.txt
RC=$?
if [ $RC -ne 0 ]; then 
echo '*** libreoffice conversion failed for myfile.txt'
exit 86
fi
cp myfile.odt somewhere-else.odt


Actual Results:  
cp: cannot stat 'myfile.odt': No such file or directory


Expected Results:
Copy completes as normal because myfile.odt is available.


Reproducible: Always


User Profile Reset: No


Additional Info:



User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:60.0) Gecko/20100101 
Firefox/60.0

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1777285/comments/0


On 2018-06-16T11:54:31+00:00 JBF wrote:

Not reproducible for me under Ubuntu 16.04 x86-64 with LibreOffice 6.0.4
from Ubuntu PPA. The script completes as expected.

To be sure, does it works for you if you try only the command

libreoffice --headless --convert-to odt:writer8 myfile.txt

in a terminal ?

Do you have some non standard settings for you file system?

Status set to NEEDINFO, please set it back to UNCONFIRMED once requested
informations are provided.


Best regards. JBF

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1777285/comments/1


On 2018-06-16T14:07:41+00:00 Richard Elkins wrote:

Like you, when I ran LibreOffice under Xubuntu 16.04 and 17.10, there
was no timing issue.  This only has appeared for me in 18.04.

In a terminal window (I've done this before),
`libreoffice --headless --convert-to odt:writer8 myfile.txt; ls *.odt` result:
ls: cannot access '*.odt': No such file or directory

My LibreOffice packages installed:
ii  libreoffice   1:6.0.3-0ubuntu1 amd64
office productivity suite (metapackage)
ii  libreoffice-avmedia-backend-gstreamer 1:6.0.3-0ubuntu1 amd64
GStreamer backend for LibreOffice
ii  libreoffice-base  1:6.0.3-0ubuntu1 amd64
office productivity suite -- database
ii  libreoffice-base-core 1:6.0.3-0ubuntu1 amd64
office productivity suite -- shared library
ii  libreoffice-base-drivers  1:6.0.3-0ubuntu1 amd64
Database connectivity drivers for LibreOffice
ii  libreoffice-calc  1:6.0.3-0ubuntu1 amd64
office productivity suite -- spreadsheet
ii  libreoffice-common1:6.0.3-0ubuntu1 all  
office productivity suite -- arch-independent files
ii  libreoffice-core  1:6.0.3-0ubuntu1 amd64
office productivity suite -- arch-dependent files
ii  libreoffice-draw  1:6.0.3-0ubuntu1 amd64
office productivity suite -- drawing
ii  libreoffice-gnome 1:6.0.3-0ubuntu1 amd64
office productivity suite -- GNOME integration
ii  libreoffice-gtk   1:6.0.3-0ubuntu1 all  
transitional package for LibreOffice gtk2 backend
ii  libreoffice-gtk2  1:6.0.3-0ubuntu1 amd64
office productivity suite -- GTK+ 2 integration
ii  libreoffice-gtk3  1:6.0.3-0ubuntu1 amd64
office productivity suite -- GTK+ 3 integration
ii  libreoffice-help-en-us1:6.0.3-0ubuntu1 all  
office productivity suite -- English_american help
ii  libreoffice-impress   1:6.0.3-0ubuntu1 amd64
office productivity suite --

[Desktop-packages] [Bug 1777285] Re: Batch libreoffice --convert-to offers no way to wait for document completion

2019-06-24 Thread Marcus Tomlinson

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

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

Title:
  Batch libreoffice --convert-to offers no way to wait for document
  completion

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

Bug description:
  Command-line: libreoffice --convert-to odt:writer8 myfile.txt

  The returned status code ($?) is zero.  So far, so good.  But, when I
  try to access the ODT file (E.g. copy it), it doesn't yet exist.

  Adding `sync; sync; sync` right after the libreoffice batch execution did not 
help.
  Adding --headless as an option did not help.

  If I sleep for a few seconds immediately after the libreoffice batch
  execution, then the file finally gets completed before a subsequent
  command references the ODT file.

  Sample script:

  ### Create somehow a file called myfile.txt
  rm myfile.odt somewhere-else.odt
  libreoffice --headless --convert-to odt:writer8 myfile.txt
  RC=$?
  if [ $RC -ne 0 ]; then 
echo '*** libreoffice conversion failed for myfile.txt'
exit 86
  fi
  #sleep 3
  ls *.odt

  Result: ls: cannot access '*.odt': No such file or directory

  If one changes the above script so that the sleep is executed, then
  the ODT file is available.

  Observation: It appears that executing libreoffice in batch mode is
  somehow kicking off a separate process to finish the ODT file.  The
  exit to the shell and the availability of the ODT file should be
  synchronized.

  Before 18.04, I never saw this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  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
  CurrentDesktop: XFCE
  Date: Sat Jun 16 17:07:02 2018
  InstallationDate: Installed on 2017-10-13 (246 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago)

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

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

[Desktop-packages] [Bug 1777285] Re: Batch libreoffice --convert-to offers no way to wait for document completion

2019-06-24 Thread Richard Elkins

I reopened https://bugs.documentfoundation.org/show_bug.cgi?id=117731
since it seems to be an issue in the central Libreoffice code.

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

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

Title:
  Batch libreoffice --convert-to offers no way to wait for document
  completion

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

Bug description:
  Command-line: libreoffice --convert-to odt:writer8 myfile.txt

  The returned status code ($?) is zero.  So far, so good.  But, when I
  try to access the ODT file (E.g. copy it), it doesn't yet exist.

  Adding `sync; sync; sync` right after the libreoffice batch execution did not 
help.
  Adding --headless as an option did not help.

  If I sleep for a few seconds immediately after the libreoffice batch
  execution, then the file finally gets completed before a subsequent
  command references the ODT file.

  Sample script:

  ### Create somehow a file called myfile.txt
  rm myfile.odt somewhere-else.odt
  libreoffice --headless --convert-to odt:writer8 myfile.txt
  RC=$?
  if [ $RC -ne 0 ]; then 
echo '*** libreoffice conversion failed for myfile.txt'
exit 86
  fi
  #sleep 3
  ls *.odt

  Result: ls: cannot access '*.odt': No such file or directory

  If one changes the above script so that the sleep is executed, then
  the ODT file is available.

  Observation: It appears that executing libreoffice in batch mode is
  somehow kicking off a separate process to finish the ODT file.  The
  exit to the shell and the availability of the ODT file should be
  synchronized.

  Before 18.04, I never saw this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  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
  CurrentDesktop: XFCE
  Date: Sat Jun 16 17:07:02 2018
  InstallationDate: Installed on 2017-10-13 (246 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago)

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

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

[Desktop-packages] [Bug 1777285] Re: Batch libreoffice --convert-to offers no way to wait for document completion

2019-06-24 Thread Richard Elkins

The file /usr/bin/libreoffice is a soft link to soffice, a Bourne shell
script. Inside the script, the soffice.bin executable is invoked.

The source code indicates that soffice.bin is the one starting a
background process that does not finish before soffice.bin exits.

See: 
https://github.com/LibreOffice/core/blob/master/shell/source/unix/exec/shellexec.cxx
 
Go to line 218:

OString cmd =
#ifdef LINUX
// avoid blocking (call it in background)
"( " + aBuffer.makeStringAndClear() +  " ) &";
#else
aBuffer.makeStringAndClear();
#endif
FILE *pLaunch = popen(cmd.getStr(), "w");
if ( pLaunch != nullptr )
{
if ( 0 == pclose( pLaunch ) )
return;

It would be interesting to understand why for only Linux, the request is
executed in background. In my opinion, this is undesirable for command
line execution in any O/S.

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

Title:
  Batch libreoffice --convert-to offers no way to wait for document
  completion

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Command-line: libreoffice --convert-to odt:writer8 myfile.txt

  The returned status code ($?) is zero.  So far, so good.  But, when I
  try to access the ODT file (E.g. copy it), it doesn't yet exist.

  Adding `sync; sync; sync` right after the libreoffice batch execution did not 
help.
  Adding --headless as an option did not help.

  If I sleep for a few seconds immediately after the libreoffice batch
  execution, then the file finally gets completed before a subsequent
  command references the ODT file.

  Sample script:

  ### Create somehow a file called myfile.txt
  rm myfile.odt somewhere-else.odt
  libreoffice --headless --convert-to odt:writer8 myfile.txt
  RC=$?
  if [ $RC -ne 0 ]; then 
echo '*** libreoffice conversion failed for myfile.txt'
exit 86
  fi
  #sleep 3
  ls *.odt

  Result: ls: cannot access '*.odt': No such file or directory

  If one changes the above script so that the sleep is executed, then
  the ODT file is available.

  Observation: It appears that executing libreoffice in batch mode is
  somehow kicking off a separate process to finish the ODT file.  The
  exit to the shell and the availability of the ODT file should be
  synchronized.

  Before 18.04, I never saw this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  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
  CurrentDesktop: XFCE
  Date: Sat Jun 16 17:07:02 2018
  InstallationDate: Installed on 2017-10-13 (246 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago)

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

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

[Desktop-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes

2019-06-24 Thread whochismo

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

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

Title:
  Bluetooth touchpad (Apple Magic Trackpad) disconnects every few
  minutes

Status in libinput package in Ubuntu:
  New

Bug description:
  I recently got an Apple's Magic Trackpad. I paired it with Ubuntu
  18.04.2 LTS and worked out of the box, no special drivers needed.

  However, I experience frequent disconnections that last a few seconds
  (5-15 seconds usually), which are quite annoying, as the cursor stops
  responding during that interval. The trackpad connects by itself after
  that period. That usually happens every 20-40 minutes.

  I use the onboard bluetooth device of my laptop. I also have, at the
  same time, two more bluetooth devices (keyboard and mouse) and they do
  not experience that issue, just the trackpad. On ocassion I use
  bluetooth headphones which work just fine.

  First of all:

  Using the command `bluetoothctl` I get the following every time I
  experience a disconnection:

  `[CHG] Device F4:1B:A1:33:F9:8D Connected: no
  [CHG] Device F4:1B:A1:33:F9:8D Connected: yes`

  Checking `dmesg` I can see more information: (if I am not mistaken,
  this shows 4 disconnections)

  `
  [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0
  [ 1609.070797] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23
  [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 1676.917377] NET: Registered protocol family 38
  [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0
  [ 1872.815559] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24
  [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0
  [ 3101.683100] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0
  [ 3110.683929] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26
  [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  `

  And this is what journalctl -b shows at the moment of the
  disconnection/reconnection:

  `de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: removing device Apple Wireless Trackpad
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option 
"fd" "64" (1,63 m)˜ 
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - 
Apple Wireless Trackpad: device removed
  de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 
'array' failed
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
UnloadModule: "libinput"
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
systemd-logind: releasing fd for 13:80
  de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown 
main item tag 0x0
  de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: 
input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 
64:5d:86:86:3f:98
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1)
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input 
driver specified, ignoring this device.
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This 
device may have been added with another device file.
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16)
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple 
Wireless Trackpad: Applying InputClass "libinput touchpad catchall"
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) Using

[Desktop-packages] [Bug 1834085] [NEW] Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes

You have been subscribed to a public bug:

I recently got an Apple's Magic Trackpad. I paired it with Ubuntu
18.04.2 LTS and worked out of the box, no special drivers needed.

However, I experience frequent disconnections that last a few seconds
(5-15 seconds usually), which are quite annoying, as the cursor stops
responding during that interval. The trackpad connects by itself after
that period. That usually happens every 20-40 minutes.

I use the onboard bluetooth device of my laptop. I also have, at the
same time, two more bluetooth devices (keyboard and mouse) and they do
not experience that issue, just the trackpad. On ocassion I use
bluetooth headphones which work just fine.

First of all:

Using the command `bluetoothctl` I get the following every time I
experience a disconnection:

`[CHG] Device F4:1B:A1:33:F9:8D Connected: no
[CHG] Device F4:1B:A1:33:F9:8D Connected: yes`

Checking `dmesg` I can see more information: (if I am not mistaken, this
shows 4 disconnections)

`
[ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0
[ 1609.070797] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23
[ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
[ 1676.917377] NET: Registered protocol family 38
[ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0
[ 1872.815559] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24
[ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
[ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0
[ 3101.683100] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
[ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
[ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0
[ 3110.683929] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26
[ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
`

And this is what journalctl -b shows at the moment of the
disconnection/reconnection:

`de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: removing device Apple Wireless Trackpad
de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" 
"64" (1,63 m)˜ 
de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - 
Apple Wireless Trackpad: device removed
de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' 
failed
de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
UnloadModule: "libinput"
de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
systemd-logind: releasing fd for 13:80
de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008
de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main 
item tag 0x0
de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: 
input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 
64:5d:86:86:3f:98
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: 
Adding input device Apple Wireless Trackpad (/dev/input/mouse1)
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input 
driver specified, ignoring this device.
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device 
may have been added with another device file.
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: 
Adding input device Apple Wireless Trackpad (/dev/input/event16)
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple 
Wireless Trackpad: Applying InputClass "libinput touchpad catchall"
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) Using input 
driver 'libinput' for 'Apple Wireless Trackpad'
de juny 13 21:37:50 TM1703 upowerd[1271]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
systemd-logind: got fd for /dev/input/event16 13:80 fd 65 paused 0
de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]:

[Desktop-packages] [Bug 1759462] Re: Keyboard shortcuts not operational on 18.04

2019-06-24 Thread Aslan

I have the same issue. It has started recently after several months of
usage. Super+D works. Most other shortcuts including Ctrl+Alt+T for
opening terminal do not work. The physical volume buttons have stopped
working too. Tried assigning custom shortcuts but that did not work too.
Restarting does not solve the issue. Version: Ubuntu 18.04.2 LTS
(Budgie) with all updates installed.

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

Title:
  Keyboard shortcuts not operational on 18.04

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

Bug description:
  After installing 18.04, I noticed that certain keyboard shortcuts no
  longer function.

  It appears to be related to the shortcuts that gnome-settings-daemon
  control as my shortcuts that are provided by my desktop (Budgie) still
  function.

  Some examples are:

  * Media keys for volume up/down/mute
  * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same 
behaviour.

  I double checked, and it looks like the needed daemon is still
  running,

  ```
  dustin3337  0.0  0.2 500736 22216 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-keyboard
  dustin3338  0.0  0.3 943372 25732 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-media-keys
  dustin3343  0.0  0.0 274908  5844 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-mouse
  dustin3345  0.0  0.3 519896 25144 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-power
  dustin3348  0.0  0.1 346004 10212 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-print-notifications
  dustin3351  0.0  0.0 374684  7952 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-smartcard
  dustin3355  0.0  0.1 329584  8064 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sound
  dustin3361  0.0  0.1 449708  9856 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sharing
  dustin3367  0.0  0.0 272416  4772 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  dustin3375  0.0  0.0 420028  5804 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-rfkill
  dustin3383  0.0  0.2 507120 23244 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-wacom
  dustin3385  0.0  0.3 498040 25040 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-xsettings
  dustin3387  0.0  0.0 274900  5936 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-a11y-settings
  dustin3392  0.0  0.2 496016 22044 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-clipboard
  dustin3395  0.0  0.3 810156 25976 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-color
  dustin3396  0.0  0.2 471656 21080 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-datetime
  dustin3400  0.0  0.0 361196  7116 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-housekeeping
  dustin3433  0.0  0.1 505404 12576 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-printer
  dustin9776  0.0  0.0  18188  1032 pts/1S+   21:19   0:00 grep 
--color=auto gnome-settings-daemon
  ```

  Reboot does not seem to help. However, occasionally the shortcuts do
  seem to work - but only very occasionally.

  Any other info needed?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 27 21:12:18 2018
  InstallationDate: Installed on 2018-03-05 (22 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180304)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1759462] Re: Keyboard shortcuts not operational on 18.04

2019-06-24 Thread Aslan

It saddens me to see the importance marked as low since this disrupts my
workflow.

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

Title:
  Keyboard shortcuts not operational on 18.04

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

Bug description:
  After installing 18.04, I noticed that certain keyboard shortcuts no
  longer function.

  It appears to be related to the shortcuts that gnome-settings-daemon
  control as my shortcuts that are provided by my desktop (Budgie) still
  function.

  Some examples are:

  * Media keys for volume up/down/mute
  * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same 
behaviour.

  I double checked, and it looks like the needed daemon is still
  running,

  ```
  dustin3337  0.0  0.2 500736 22216 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-keyboard
  dustin3338  0.0  0.3 943372 25732 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-media-keys
  dustin3343  0.0  0.0 274908  5844 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-mouse
  dustin3345  0.0  0.3 519896 25144 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-power
  dustin3348  0.0  0.1 346004 10212 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-print-notifications
  dustin3351  0.0  0.0 374684  7952 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-smartcard
  dustin3355  0.0  0.1 329584  8064 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sound
  dustin3361  0.0  0.1 449708  9856 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sharing
  dustin3367  0.0  0.0 272416  4772 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  dustin3375  0.0  0.0 420028  5804 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-rfkill
  dustin3383  0.0  0.2 507120 23244 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-wacom
  dustin3385  0.0  0.3 498040 25040 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-xsettings
  dustin3387  0.0  0.0 274900  5936 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-a11y-settings
  dustin3392  0.0  0.2 496016 22044 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-clipboard
  dustin3395  0.0  0.3 810156 25976 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-color
  dustin3396  0.0  0.2 471656 21080 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-datetime
  dustin3400  0.0  0.0 361196  7116 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-housekeeping
  dustin3433  0.0  0.1 505404 12576 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-printer
  dustin9776  0.0  0.0  18188  1032 pts/1S+   21:19   0:00 grep 
--color=auto gnome-settings-daemon
  ```

  Reboot does not seem to help. However, occasionally the shortcuts do
  seem to work - but only very occasionally.

  Any other info needed?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 27 21:12:18 2018
  InstallationDate: Installed on 2018-03-05 (22 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180304)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

2019-06-24 Thread Andreas Hasenack

@bloodyiron, you said in
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/comments/81
that you had SMB1 disabled in your network, and I confirmed that with
SMB1 disabled there is still a bug, and that bug is
https://bugs.launchpad.net/gvfs/+bug/1828107, and it affects all ubuntu
releases. I don't know what else to tell you, sorry, it sounds like you
are ignoring that open bug.

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs:
  Unknown
Status in samba:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Released
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Fix Released
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine that shows up in
  the network browsing, and then check with

Re: [Desktop-packages] [Bug 1833617] Re: [amdgpu] screen freeze after suspend

2019-06-24 Thread Meir Levi

Thanks, Daniel.There is another issue since Linux 5.0.For some reason, I can't 
get to the Recovery mode during boot up (neither "esc" nor "shift" key work).Is 
that by design or another bug?
Just for reference. Here is my latest Journal generated this morning. (I use 
Cinnomon as my Desktop)
6/24/19 9:21 AM    systemd    Reached target Timers.
6/24/19 9:21 AM    systemd    Listening on GnuPG cryptographic agent and 
passphrase cache.
6/24/19 9:21 AM    systemd    Listening on GnuPG network certificate management 
daemon.
6/24/19 9:21 AM    systemd    Listening on GnuPG cryptographic agent and 
passphrase cache (restricted).
6/24/19 9:21 AM    systemd    Listening on GnuPG cryptographic agent (ssh-agent 
emulation).
6/24/19 9:21 AM    systemd    Started Pending report trigger for Ubuntu Report.
6/24/19 9:21 AM    systemd    Reached target Paths.
6/24/19 9:21 AM    systemd    Listening on GnuPG cryptographic agent and 
passphrase cache (access for web browsers).
6/24/19 9:21 AM    systemd    Listening on Sound System.
6/24/19 9:21 AM    systemd    Listening on D-Bus User Message Bus Socket.
6/24/19 9:21 AM    systemd    Reached target Sockets.
6/24/19 9:21 AM    systemd    Reached target Basic System.
6/24/19 9:21 AM    systemd    Reached target Default.
6/24/19 9:21 AM    systemd    Startup finished in 148ms.
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (--) Log file renamed from 
"/home/meir-user/.local/share/xorg/Xorg.pid-19996.log" to 
"/home/meir-user/.local/share/xorg/Xorg.0.log"
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    X.Org X Server 1.20.4
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    X Protocol Version 11, 
Revision 0
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    Build Operating System: Linux 
4.4.0-143-generic x86_64 Ubuntu
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    Current Operating System: 
Linux meiradmin-Inspiron-3180 5.0.0-18-generic #19-Ubuntu SMP Wed Jun 12 
18:17:16 UTC 2019 x86_64
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic 
root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    Build Date: 03 April 2019  
09:03:57AM
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    xorg-server 2:1.20.4-1ubuntu3 
(For technical support please see http://www.ubuntu.com/support)
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    Current version of pixman: 
0.36.0
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session        Before reporting 
problems, check http://wiki.x.org
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session        to make sure that you 
have the latest version.
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    Markers: (--) probed, (**) 
from config file, (==) default setting,
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session        (++) from command line, 
(!!) notice, (II) informational,
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session        (WW) warning, (EE) error, 
(NI) not implemented, (??) unknown.
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (==) Log file: 
"/home/meir-user/.local/share/xorg/Xorg.0.log", Time: Mon Jun 24 09:21:53 2019
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (==) Using system config 
directory "/usr/share/X11/xorg.conf.d"
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (==) No Layout section.  
Using the first Screen section.
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (==) No screen section 
available. Using defaults.
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (**) |-->Screen "Default 
Screen Section" (0)
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (**) |   |-->Monitor 
""
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (==) No monitor specified for 
screen "Default Screen Section".
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session        Using a default monitor 
configuration.
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (==) Automatically adding 
devices
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (==) Automatically enabling 
devices
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (==) Automatically adding GPU 
devices
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (==) Automatically binding 
GPU devices
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (==) Max clients allowed: 
256, resource mask: 0x1f
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (WW) The directory 
"/usr/share/fonts/X11/cyrillic" does not exist.
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session        Entry deleted from font 
path.
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (WW) The directory 
"/usr/share/fonts/X11/100dpi/" does not exist.
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session        Entry deleted from font 
path.
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (WW) The directory 
"/usr/share/fonts/X11/75dpi/" does not exist.
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session        Entry deleted from font 
path.
6/24/19 9:21 AM    /usr/lib/gdm3/gdm-x-session    (WW) The directory

[Desktop-packages] [Bug 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend

2019-06-24 Thread Matthijs Kooijman

I'm also running into this bug (or at least something that looks like
it). Typically what happens for me is that I resume from suspend, get an
unlock prompt (the system is locked on suspend) and when I log in, the
unlock prompt stays visible (the password dots disappear, but I cannot
type anything or click any buttons). When I then kill X to recover
(ctrl-alt-backspace), I get a new login prompt. Sometimes, logging in
again no longer works then, seeing such messages in the console:

jun 21 17:01:50 grubby at-spi-bus-launcher[30649]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":1024"
jun 21 17:01:50 grubby at-spi-bus-launcher[30649]:   after 21 requests (21 
known processed) with 0 events remaining.
jun 21 17:01:50 grubby gsd-power[30703]: gsd-power: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :1024.
jun 21 17:01:50 grubby gsd-keyboard[30715]: gsd-keyboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
jun 21 17:01:50 grubby gsd-xsettings[30696]: gsd-xsettings: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
jun 21 17:01:50 grubby gsd-media-keys[30731]: gsd-media-keys: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
jun 21 17:01:50 grubby systemd-logind[1100]: Session c9 logged out. Waiting for 
processes to exit.
jun 21 17:01:50 grubby gsd-clipboard[30695]: gsd-clipboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
jun 21 17:01:50 grubby gsd-color[30713]: gsd-color: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :1024.
jun 21 17:01:50 grubby gnome-shell[30633]: Connection to xwayland lost


>From the messages, I suspect this might be the same problem as the original 
>poster.

However, I'm not entirely sure if at-spi-bus-launcher is actually the
culprit here. Could it be that that the xserver or xwayland (I'm not
sure which - I'm using the GNOME xorg session since the wayland session
doesn't work for me, but the log does talk about xwayland) crashes and
that at-spi-bus-launcher is just the first process to find out (because
it does so many requests maybe?). I've also seen some instances where
at-spi-bus-launcher is not the first one in the log, and I've tried
disabling at-spi-bus-launcher by masking it in systemd (not entirely
sure if that really worked), but then I also think I saw a crash where
at-spi-bus-launcher would not show up in the log at all.

One additional observation: At some point during testing, while login
would not work, I found a logged in session in some virtual terminal.
After logging out that session, logins would work again as normal. I'm
not entirely sure if there's a causal relationship there, nor where that
logged in session came from (but I was testing with two different users
to see if there was something in my homedir that triggered it, so
perhaps it came from one of those tests...). Vague, but I wanted to
mention this just in case it triggers an idea somewhere :-)

As for reporting an upstream issue, that is probably a good idea, though
I'm not entirely sure where the cause is. It's probably safe to say it
is something in gnome, though.

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

Title:
  at-spi-bus-launcher makes Xorg crash when resuming from suspend

Status in at-spi2-core package in Ubuntu:
  Confirmed

Bug description:
  If at-spi2-core is installed, when resuming from suspend messages like
  these are logged in systemd journal:

  at-spi-bus-launcher[31720]: XIO:  fatal IO error 11 (Resource temporarily 
unavailable) on X server ":0.0"
  at-spi-bus-launcher[31720]:   after 8065 requests (8065 known processed) 
with 0 events remaining.

  The number of requests vary, it can reach more than 15000. Depending
  on the number of requests, the Xorg server crashes with SIGBUS.
  Depending on the exact moment Xorg crashes, when lightdm manages to
  recover, it shows a login greeter, or worst case scenario, it can't
  recover, a black screen is shown and the desptop session doesn't
  start.

  It took me a long time to discover the cause. The visible symptom was:
  once in a while when resuming from suspend, I got a login greeter
  instead of an unlock greeter, or a black screen which forced me to
  power down. Investigating, I found out that whenever that happened,
  there was a Xorg core left behind. Looking at the journal messages
  before the crash, there was always that flood of at-spi2-core
  requests. So I uninstalled at-spi2-core and Xorg never crashed
  anymore.

  This is a quite severe bug, which makes it impossible to use at-
  spi2-core.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: at-spi2-core (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1

[Desktop-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-06-24 Thread Karl Pickett

ahci.mobile_lpm_policy=0 did not fix it, it hung in a few days.  I will
downgrade to 18.04.  And small correction, this is an asrock deskmini
h110m-stx system, not a NUC.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1834052] Re: autopkgtest failures: Chromium-Related in Tests

2019-06-24 Thread Thomas Ward

Iain:

Sounds like armhf needs to be badtested then for kopano-webapp, or at
least that failure ignored for now.  THat one I can ask be ignored.  The
rest of them sounds like a Chromium snap issue, indeed.

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

Title:
  autopkgtest failures: Chromium-Related in Tests

Status in chromium-browser package in Ubuntu:
  New
Status in kopano-webapp package in Ubuntu:
  New

Bug description:
  Hello.

  Currently, the kopano-webapp autopkgtests are failing.  Three of these
  are related to Chromium crashes/failures (possibly because they're
  snapped) within the Selenium calls.

  The fourth is a snap related issue in general.

  These autopkgtest failures are blocking HTTPD packages in Proposed
  (nginx, apache, etc.)

  
  --
  Relevant Links:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/k/kopano-webapp/20190624_082152_0ef6d@/log.gz

  arm64:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/arm64/k/kopano-
  webapp/20190624_084645_0ef6d@/log.gz

  armhf:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/armhf/k/kopano-
  webapp/20190624_082623_0ef6d@/log.gz

  i386:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/i386/k/kopano-
  webapp/20190624_082523_0ef6d@/log.gz

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

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

[Desktop-packages] [Bug 1834058] Re: Keyboard layout indicator vanishes after Suspend or Screenlock

2019-06-24 Thread hpp23

I use two keyboard layouts:
(1) German
(2) Chinese (Intelligent Pinyin)

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

Title:
  Keyboard layout indicator vanishes after Suspend or Screenlock

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Related to bug 1812266.

  lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  apt-cache policy gnome-shell
  gnome-shell:
  installed: 3.28.4-0ubuntu18.04.1

  After Suspend or Screenlock ...

  What you expected to happen:
  Keyboard layout indicator should be visible all the time.

  What happened instead:
  not visible anymore

  Current manual fix:
  Press SUPER
  give search field the focus
  Press SUPER+Spacebar several times until current keyboard layout is selected.
  Keyboard layout indicator is visible again with current layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 24 17:40:12 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-07-20 (339 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

The bug still exists for me on Disco, so I don't see how you arrive at
the position that it "works" out of the box. It does not "work" for me,
the bug exists on Disco for me. And I've regularly kept my system up to
date. I've reported this multiple times in this thread and seem to be
ignored.

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs:
  Unknown
Status in samba:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Released
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Fix Released
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine that shows up in
  the network browsing, and then check with "smbstatus" which version of
  the protocol was used when connecting to an actual share.

  ---

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

In fact I literally just tried it again, and get the same issue, where
it does not prompt for login, and the related gvfs process needs to be
killed.

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs:
  Unknown
Status in samba:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Released
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Fix Released
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine that shows up in
  the network browsing, and then check with "smbstatus" which version of
  the protocol was used when connecting to an actual share.

  ---

  Nautilus should show smbtree and host on the smb network.

  When inputing this command:
  killall gvfsd-smb-browse && GVFS_DEBUG=1

[Desktop-packages] [Bug 1834058] [NEW] Keyboard layout indicator vanishes after Suspend or Screenlock

2019-06-24 Thread hpp23

Public bug reported:

Related to bug 1812266.

lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04

apt-cache policy gnome-shell
gnome-shell:
installed: 3.28.4-0ubuntu18.04.1

After Suspend or Screenlock ...

What you expected to happen:
Keyboard layout indicator should be visible all the time.

What happened instead:
not visible anymore

Current manual fix:
Press SUPER
give search field the focus
Press SUPER+Spacebar several times until current keyboard layout is selected.
Keyboard layout indicator is visible again with current layout.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.4-0ubuntu18.04.1
ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
Uname: Linux 4.15.0-52-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 24 17:40:12 2019
DisplayManager: gdm3
InstallationDate: Installed on 2018-07-20 (339 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Keyboard layout indicator vanishes after Suspend or Screenlock

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Related to bug 1812266.

  lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  apt-cache policy gnome-shell
  gnome-shell:
  installed: 3.28.4-0ubuntu18.04.1

  After Suspend or Screenlock ...

  What you expected to happen:
  Keyboard layout indicator should be visible all the time.

  What happened instead:
  not visible anymore

  Current manual fix:
  Press SUPER
  give search field the focus
  Press SUPER+Spacebar several times until current keyboard layout is selected.
  Keyboard layout indicator is visible again with current layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 24 17:40:12 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-07-20 (339 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1834052] Re: autopkgtest failures: Chromium-Related in Tests

2019-06-24 Thread Iain Lane

all except armhf look like a problem with the Chromium snap

armhf will probably become that same problem once we're able to run
snaps there (need to look into what's required)

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

Title:
  autopkgtest failures: Chromium-Related in Tests

Status in chromium-browser package in Ubuntu:
  New
Status in kopano-webapp package in Ubuntu:
  New

Bug description:
  Hello.

  Currently, the kopano-webapp autopkgtests are failing.  Three of these
  are related to Chromium crashes/failures (possibly because they're
  snapped) within the Selenium calls.

  The fourth is a snap related issue in general.

  These autopkgtest failures are blocking HTTPD packages in Proposed
  (nginx, apache, etc.)

  
  --
  Relevant Links:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/k/kopano-webapp/20190624_082152_0ef6d@/log.gz

  arm64:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/arm64/k/kopano-
  webapp/20190624_084645_0ef6d@/log.gz

  armhf:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/armhf/k/kopano-
  webapp/20190624_082623_0ef6d@/log.gz

  i386:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/i386/k/kopano-
  webapp/20190624_082523_0ef6d@/log.gz

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

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

[Desktop-packages] [Bug 1833745] Re: [MIR] required new dependency of appstream

2019-06-24 Thread Sebastien Bacher

@Christian, thanks for the review! desktop-packages is subsribed to the
report/Desktop Team is going to own that one (the description has been updated
earlier to reflect that).
@Didrocks, unping :)

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

Title:
[MIR] required new dependency of appstream

Status in lmdb package in Ubuntu:
New

Bug description:
Availability

Built for all supported architectures. One upstream release ahead of Debian.

Rationale
=
Now a required build and runtime dependency of appstream in -proposed in Eoan

https://github.com/ximion/appstream/commit/358e9394631b87797f56dcb7e09e459b4044e631#commitcomment-33995178

Quote "Compiling AppStream without LMDB is not really possible."

Security

No known CVEs.
https://security-tracker.debian.org/tracker/source-package/lmdb

Quality assurance
=
- Desktop Packages team is subscribed.
- dh_auto_test run at build time for supported architectures.
- No functional outstanding bugs in Ubuntu or Debian. Upstream 'issue'
tracker is active.
https://bugs.launchpad.net/ubuntu/+source/lmdb
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=lmdb

https://www.openldap.org/its/index.cgi/Software%20Bugs?page=1;expression=lmdb;page=1

Dependencies

No universe binary dependencies

Standards compliance

4.1.5.0 , debhelper compat 9

Maintenance
===
Actively maintained:

http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=history;f=libraries/liblmdb;hb=HEAD

Not team maintained in Debian.
https://tracker.debian.org/pkg/lmdb

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

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

[Desktop-packages] [Bug 1834053] [NEW] PCI/internal sound card not detected

2019-06-24 Thread jonal

Public bug reported:

No sound as my pc does not detect sound hardware

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
Uname: Linux 3.13.0-170-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', 
'/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] 
failed with exit code 1:
CurrentDesktop: Unity
Date: Mon Jun 24 20:39:45 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
InstallationDate: Installed on 2016-11-06 (960 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: Upgraded to xenial on 2019-06-24 (0 days ago)
dmi.bios.date: 09/06/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0XCR91
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/06/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 3558
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound as my pc does not detect sound hardware

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', 
'/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jun 24 20:39:45 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2016-11-06 (960 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to xenial on 2019-06-24 (0 days ago)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0XCR91
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/06/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 3558
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1834052] Re: autopkgtest failures: Chromium-Related in Tests

2019-06-24 Thread Iain Lane

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

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

Title:
  autopkgtest failures: Chromium-Related in Tests

Status in chromium-browser package in Ubuntu:
  New
Status in kopano-webapp package in Ubuntu:
  New

Bug description:
  Hello.

  Currently, the kopano-webapp autopkgtests are failing.  Three of these
  are related to Chromium crashes/failures (possibly because they're
  snapped) within the Selenium calls.

  The fourth is a snap related issue in general.

  These autopkgtest failures are blocking HTTPD packages in Proposed
  (nginx, apache, etc.)

  
  --
  Relevant Links:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/k/kopano-webapp/20190624_082152_0ef6d@/log.gz

  arm64:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/arm64/k/kopano-
  webapp/20190624_084645_0ef6d@/log.gz

  armhf:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/armhf/k/kopano-
  webapp/20190624_082623_0ef6d@/log.gz

  i386:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/i386/k/kopano-
  webapp/20190624_082523_0ef6d@/log.gz

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

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

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

2019-06-24 Thread Daniel C

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

I agree with mactyr that this should not be a duplicate of that bug. The
flaw that I see is not what is shown in those videos. There is no
glitching, it is the whole screen flashing brighter, and is why I used
the word "flashes" in the title, as opposed to "flickers" or "glitches".

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

Title:
  Dell XPS 13 9380 - Screen flashes

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hello,

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

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

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

  However the screen flashing still persists.

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

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

  Thank you.

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

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

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

[Desktop-packages] [Bug 1834047] [NEW] External monitor not recognised

2019-06-24 Thread Daniel Martinek

Public bug reported:

I have BenQ i do not know what number, but it is connected by HDMI to DVI cable.
 nvidia-driver-418 is version 418.56-0ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
Uname: Linux 5.0.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 24 16:20:03 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 als, master, 5.0.0-16-generic, x86_64: installed
 als, master, 5.0.0-17-generic, x86_64: installed
 nvidia, 418.56, 5.0.0-16-generic, x86_64: installed
 nvidia, 418.56, 5.0.0-17-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] (P1000 
[Zbook 17 G5 mobile workstation]) [103c:842f]
MachineType: HP HP ZBook 17 G5
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic 
root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2019
dmi.bios.vendor: HP
dmi.bios.version: Q70 Ver. 01.07.00
dmi.board.name: 842D
dmi.board.vendor: HP
dmi.board.version: KBC Version 15.37.00
dmi.chassis.asset.tag: 5CD8501DGX
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ70Ver.01.07.00:bd04/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.37.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook 17
dmi.product.name: HP ZBook 17 G5
dmi.product.sku: 4QH25EA#BCM
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco ubuntu

** Attachment added: "journalctl output"
   https://bugs.launchpad.net/bugs/1834047/+attachment/5272831/+files/jcl.txt

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

Title:
  External monitor not recognised

Status in xorg package in Ubuntu:
  New

Bug description:
  I have BenQ i do not know what number, but it is connected by HDMI to DVI 
cable.
   nvidia-driver-418 is version 418.56-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 24 16:20:03 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   als, master, 5.0.0-16-generic, x86_64: installed
   als, master, 5.0.0-17-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-16-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] (P1000 
[Zbook 17 G5 mobile workstation]) [103c:842f]

[Desktop-packages] [Bug 1833899] Re: nautilus crashed with SIGSEGV

2019-06-24 Thread Brian Murray

The core file is truncated and gdb will not work with it.

GNU gdb (Ubuntu 8.3-0ubuntu1) 8.3
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.10/amd64/report-sandbox//usr/bin/nautilus...
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.10/amd64/report-sandbox/usr/lib/debug/.build-id/ed/225155cf94bd3b6e89bcf31cd7bb9d2efc09c3.debug...
"/tmp/apport_core_k99t7p9a" is not a core dump: file truncated
(gdb) quit


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

Title:
  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  just logged in. no apps started.
  corrado@corrado-HP-p4-ee-0618:~$ inxi -Fx
  System:Host: corrado-HP-p4-ee-0618 Kernel: 5.0.0-17-generic x86_64 bits: 
64 compiler: gcc v: 8.3.0 
 Desktop: Gnome 3.32.2 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook 
PC v: 0991100600087 
 serial:  
 Mobo: Hewlett-Packard model: 2211 v: 86.49 serial:  
UEFI: Insyde v: F.36 
 date: 12/18/2014 
  Battery:   ID-1: BAT1 charge: 11.3 Wh condition: 19.9/19.5 Wh (102%) model: 
13-42 OA03031 
 status: Discharging 
  CPU:   Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT 
MCP arch: Haswell rev: 1 
 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19156 
 Speed: 898 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 898 2: 
898 3: 898 4: 898 
  Graphics:  Device-1: Intel Haswell-ULT Integrated Graphics vendor: 
Hewlett-Packard driver: i915 v: kernel 
 bus ID: 00:02.0 
 Display: x11 server: X.Org 1.20.4 driver: i915 resolution: 
1366x768~60Hz 
 OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 19.0.5 
direct render: Yes 
  Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard 
driver: snd_hda_intel v: kernel 
 bus ID: 00:03.0 
 Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard driver: 
snd_hda_intel v: kernel 
 bus ID: 00:1b.0 
 Sound Server: ALSA v: k5.0.0-17-generic 
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: 
Hewlett-Packard driver: r8169 
 v: kernel port: 3000 bus ID: 08:00.0 
 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce 
 Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe vendor: 
Hewlett-Packard driver: rt2800pci 
 v: 2.3.0 port: 3000 bus ID: 09:00.0 
 IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d 
  Drives:Local Storage: total: 465.76 GiB used: 6.89 GiB (1.5%) 
 ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 
465.76 GiB 
  Partition: ID-1: / size: 31.25 GiB used: 6.88 GiB (22.0%) fs: ext4 dev: 
/dev/sda4 
 ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
  Sensors:   System Temperatures: cpu: 30.0 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 207 Uptime: 7m Memory: 3.78 GiB used: 1.01 GiB (26.7%) 
Init: systemd runlevel: 5 
 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.34 
  corrado@corrado-HP-p4-ee-0618:~$

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.32.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 23 20:57:41 2019
  Disassembly: No registers.
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-06-23 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190618)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  Registers: The program has no registers now.
  SegvAnalysis: Failure: invalid literal for int() with base 16: 'program'
  Signal: 11
  SourcePackage: nautilus
  Stacktrace: No stack.
  StacktraceTop:
   
  ThreadStacktrace:
   
  Title: nautilus crashed

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

2019-06-24 Thread Andreas Hasenack

Disco works out of the box wrt this bug specifically. Which is expected
since it has the same fix.

windows network tab is populated (see disco-windows-network-
populated.png)

Connecting to the pub share (see disco-connect-to-pub.png).

smbstatus shows smb3.11 in the pub connection, and NT1 for IPC$:
ubuntu@disco-desktop:~$ sudo smbstatus

Samba version 4.10.0-Ubuntu
PID Username GroupMachine   
Protocol Version  Encryption   Signing  

3969ubuntu   ubuntu   127.0.0.1 (ipv4:127.0.0.1:43370)  
SMB3_11   -partial(AES-128-CMAC)
3752nobody   nogroup  disco-desktop (ipv4:192.168.122.70:53276) NT1 
  --
3721nobody   nogroup  disco-desktop (ipv4:127.0.0.1:40552)  NT1 
  --
3805nobody   nogroup  disco-desktop (ipv4:127.0.0.1:40562)  NT1 
  --
3731nobody   nogroup  disco-desktop (ipv4:192.168.122.70:53270) NT1 
  --

Service  pid Machine   Connected at Encryption  
 Signing 
-
IPC$ 3721disco-desktop seg jun 24 10:35:20 2019 -03 -   
 -   
pub  3969127.0.0.1 seg jun 24 10:36:16 2019 -03 -   
 -   
IPC$ 3752disco-desktop seg jun 24 10:35:31 2019 -03 -   
 -   
IPC$ 3805disco-desktop seg jun 24 10:35:54 2019 -03 -   
 -   
IPC$ 3731disco-desktop seg jun 24 10:35:23 2019 -03 -   
 -   

No locked files


If you have NT1 disabled in your network, then the windows network tab will be 
empty, and that's https://bugs.launchpad.net/gvfs/+bug/1828107 and it affects 
all releases still.

** Attachment added: "disco-windows-network-populated.png"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272828/+files/disco-windows-network-populated.png

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs:
  Unknown
Status in samba:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Released
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Fix Released
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share,

[Desktop-packages] [Bug 1695876] Re: German Documentation file displays incorrect CUPS version

2019-06-24 Thread Edward Hope-Morley

** Tags removed: sts-sru-needed

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

Title:
  German Documentation file displays incorrect CUPS version

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  In Progress

Bug description:
  The /doc/de/index.html.in file in the package source has an incorrect
  version number written into a header instead of using '@CUPS_VERSION@'
  to populate this file as in the other languages' version of the same
  file, seemingly resulting in /usr/share/cups/doc-root/de/index.html
  having the wrong version once CUPS is installed:

  ...
  

  CUPS 2.0.2
  ...

  instead of:

  ...
  

  CUPS @CUPS_VERSION@
  ...

  resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown.

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

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

2019-06-24 Thread Andreas Hasenack

** Attachment added: "disco-connect-to-pub.png"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272829/+files/disco-connect-to-pub.png

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs:
  Unknown
Status in samba:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Released
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Fix Released
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine that shows up in
  the network browsing, and then check with "smbstatus" which version of
  the protocol was used when connecting to an actual share.

  ---

  Nautilus should show smbtree and host on the smb network.

  When inputing this command:
  killall gvfsd-smb-browse && GVFS_DEBUG=1

[Desktop-packages] [Bug 1834036] Re: [HDA-Intel - HDA Intel PCH, recording] Only static noises are recorded on TravelMate X514-51

2019-06-24 Thread Buo-ren, Lin

** Attachment added: "Ubuntu bug #1834036 reproducing recording.ogg"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834036/+attachment/5272830/+files/Ubuntu%20bug%20%231834036%20reproducing%20recording.ogg

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

Title:
  [HDA-Intel - HDA Intel PCH, recording] Only static noises are recorded
  on TravelMate X514-51

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On TravelMate X514-51 the microphone is detected but only staticky
  noises are recorded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buo.ren.lin   7028 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Jun 24 21:24:17 2019
  InstallationDate: Installed on 2019-05-08 (47 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=zh_TW:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_TW.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: 內部音效 - HDA Intel PCH
  Symptom_Type: High background noise, or volume is too low
  Title: [HDA-Intel - HDA Intel PCH, recording] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.name: Crux_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd01/24/2019:svnAcer:pnTravelMateX514-51:pvrV1.04:rvnWL:rnCrux_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: TravelMate X5
  dmi.product.name: TravelMate X514-51
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1831624] Re: ibus-cangjie in libreoffice cannot type Chinese character at end of line

Launchpad has imported 2 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=126068.

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


On 2019-06-24T10:04:36+00:00 Marcus Tomlinson wrote:

Description:
When at the end of a line in Writer, spaces seem to get inserted with zero 
width rather than wrapping over to the next line. I.e. x number spaces at the 
end of a line requires x number of backspaces to move the cursor backward again.

Steps to Reproduce:
1. Open Writer
2. Hold down the spacebar

Actual Results:
When the cursor hits the end of the line, subsequent spaces are entered 
invisibly at the end of that line.

Expected Results:
When the cursor hits the end of the line it should wrap over to the next.


Reproducible: Always


User Profile Reset: No


Additional Info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1831624/comments/9


On 2019-06-24T13:01:42+00:00 Vstuart-foote wrote:

Confirmed on Windows 10 Home 64-bit en-US with
Version: 6.2.4.2 (x64)
Build ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded

STR

1. New Writer document
2. Page properties, set left & right margins to 3" reduce to a narrow column
3. change font for Paragraph to Liberation Mono
4. enter sequence of spaces to fill to the reduced margins (24 on US 8.5x11 in 
page)
5. notice the count of characters in the status bar shows 24
6. keep entering spaces, count goes up but text cursor remains at right margin
7. back space will reduce the count of characters, untill cursor starts moving 
left into paragraph again. Enter additional spaces, text cursor again stops a 
right margin.
8. save file to Flat XML .fodt
9. open the .fodt in a text editor

Examine the  and note that the text spans are  or more, so this looks to be correct ODF 1.2 recording of spaces.
And, they are legitimate Unicode U+0020 (not assigned any other glyph
with an +X toggle)

However with a second paragraph, placed after the first, text cursor
movement will pass from the right margin of the first directly to the
left margin start of the next paragraph. Ignoring the text span's
 "spaces" beyond the end of the margin.

Not clear it is incorrect (from ODF perspective) but it is weird UX.

@Regina?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1831624/comments/11


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

** Changed in: df-libreoffice
   Importance: Unknown => Medium

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

Title:
  ibus-cangjie in libreoffice cannot type Chinese character at end of
  line

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

Bug description:
  I am using LibreOffice Version: 6.0.7.3, in particular I am using
  LibreOffice Writer.

  I am using ibus-cangjie to input Chinese.

  I cannot input any Chinese characters when I reach the end of a line
  on the screen.

  The expected behavior is that the typed Chinese character simply
  spills over to the next line and I can continue to type without a
  problem.

  If I reach the end of the line with half a space (of full-sized
  Chinese character) available, then I could insert a punctuation mark
  like 。 or 、 even if I use cangjie codes to input them (and then I can
  continue normally).

  if I reach the end of the line with no space available, then I cannot
  insert 。 or 、 when I use cangjie codes to input them (in the ibus-
  cangjie standard input table, 、 = XI)

  In neither case I can type a Chinese character like 日, all the typed
  characters simply disappears from the input queue and is not typed at
  all.  Note that as I type I can see that the candidate Chinese
  characters according to the cangjie codes I input, they just don't get
  sent to the application.

  when I am at the end of the line, I can type as many spaces as I want
  and the problem of being unable to type a Chinese character persists.

  Finally, the bug only triggers when I am at the end of text; if I am
  inserting in the middle of text, even if I am at the linebreak, I can
  type normally and naturally.

  the attached screenshot shows where I am getting my cursor stuck.

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

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

[Desktop-packages] [Bug 1834036] [NEW] [HDA-Intel - HDA Intel PCH, recording] Only static noises are recorded on TravelMate X514-51

2019-06-24 Thread Buo-ren, Lin

Public bug reported:

On TravelMate X514-51 the microphone is detected but only staticky
noises are recorded.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  buo.ren.lin   7028 F pulseaudio
CurrentDesktop: KDE
Date: Mon Jun 24 21:24:17 2019
InstallationDate: Installed on 2019-05-08 (47 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=zh_TW:zh
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=zh_TW.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_Card: 內部音效 - HDA Intel PCH
Symptom_Type: High background noise, or volume is too low
Title: [HDA-Intel - HDA Intel PCH, recording] Background noise or low volume
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/24/2019
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.name: Crux_WL
dmi.board.vendor: WL
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.04
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd01/24/2019:svnAcer:pnTravelMateX514-51:pvrV1.04:rvnWL:rnCrux_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
dmi.product.family: TravelMate X5
dmi.product.name: TravelMate X514-51
dmi.product.sku: 
dmi.product.version: V1.04
dmi.sys.vendor: Acer

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

Title:
  [HDA-Intel - HDA Intel PCH, recording] Only static noises are recorded
  on TravelMate X514-51

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On TravelMate X514-51 the microphone is detected but only staticky
  noises are recorded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buo.ren.lin   7028 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Jun 24 21:24:17 2019
  InstallationDate: Installed on 2019-05-08 (47 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=zh_TW:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_TW.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: 內部音效 - HDA Intel PCH
  Symptom_Type: High background noise, or volume is too low
  Title: [HDA-Intel - HDA Intel PCH, recording] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.name: Crux_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd01/24/2019:svnAcer:pnTravelMateX514-51:pvrV1.04:rvnWL:rnCrux_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: TravelMate X5
  dmi.product.name: TravelMate X514-51
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1834032] [NEW] loosing wificontact

2019-06-24 Thread j.niehof

Public bug reported:

Often I receive the message : Problem in ubunt, do you want to send the 
messaage?
Often my laptop (Dell Latitude) looses contact with wifi, only to be repaired 
by restarting the computer.
This happens for all after changing a user and a moment of computersleep

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
Uname: Linux 4.15.0-52-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Jun 24 15:02:44 2019
DistUpgraded: 2019-05-03 22:15:55,047 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0492]
InstallationDate: Installed on 2019-05-01 (53 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Dell Inc. Latitude E6320
ProcEnviron:
 LANGUAGE=nl
 PATH=(custom, no user)
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=cf82673b-3d94-436d-9879-0993332233ff ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-05-03 (51 days ago)
dmi.bios.date: 11/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.name: 0GJF11
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn0GJF11:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6320
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.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

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


** Tags: amd64 apport-bug bionic compiz-0.9 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/1834032

Title:
  loosing wificontact

Status in xorg package in Ubuntu:
  New

Bug description:
  Often I receive the message : Problem in ubunt, do you want to send the 
messaage?
  Often my laptop (Dell Latitude) looses contact with wifi, only to be repaired 
by restarting the computer.
  This happens for all after changing a user and a moment of computersleep

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun 24 15:02:44 2019
  DistUpgraded: 2019-05-03 22:15:55,047 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0492]
  InstallationDate: Installed on 2019-05-01 (53 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Latitude E6320
  ProcEnviron:
   LANGUAGE=nl
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=cf82673b-3d94-436d-9879-0993332233ff ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-05-03 (51 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0GJF11
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias:

[Desktop-packages] [Bug 1422253] Re: gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: (window->display->focus_window != window)") from g_assertion_message_expr() from meta_wi

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message("assertion
  failed: (window->display->focus_window != window)") from
  g_assertion_message_expr() from meta_window_unmanage() from
  handle_other_xevent()

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Bionic:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/868da6d40640c1199f496b7af7e37e54871ed8d7
  https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/15

  New issue (same stacktrace) is
  https://gitlab.gnome.org/GNOME/mutter/issues/308

  [ Description ]

  Was running 3 programs at time of crash, PROGRAM 1. Nautilus with no
  tabs open, PROGRAM 2. Firefox v.34.0 with 3 tabs open (1.
  https://twitter.com/ - 2.
  http://www.scons.org/wiki/FrequentlyAskedQuestions#What_is_SCons.3F -
  PROGRAM 3. http://scons.org/download.php) Synaptic Package Manager ver
  0.81.3 installing Scons & Scons-doc - crash happened while synaptic
  was in process of installing programs (downloads were complete &
  actual install was in progress)

  [ Test case ]

  1. Run one of the reproducer test (python or gjs version) available at:
     https://gitlab.gnome.org/GNOME/mutter/issues/15
  2. when that close, g-s should not crash

  [ Regression potential ]

  Possible break for windows that have the grab but are not the active
  ones.

  

  ProblemType: CrashDistroRelease: Ubuntu 15.04
  Package: gnome-shell 3.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Feb 16 01:20:05 2015
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2015-01-26 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 
(20150120.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSignal: 6SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   meta_window_unmanage () from /usr/lib/libmutter.so.0
   ?? () from /usr/lib/libmutter.so.0
   ?? () from /usr/lib/libmutter.so.0
  Title: gnome-shell crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1822515] Re: Touchscreen input doesn't rotate with the screen

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

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

Title:
  Touchscreen input doesn't rotate with the screen

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  When a touch screen is rotated, touch input is not mapped correctly.

  I'm testing 19.04 on an Acer-One S1003 where the default orientation
  is portrait.

  Ubuntu 19.04 support automatic screen rotation out of the box. But,
  when the tablet is in landscape, the touchscreen doesn't behave
  correctly. Moving a finger horizontally cause a vertical movement and
  vice versa.

  The same happens in both X11 and Wayland.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  Package: xorg-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

This bug was fixed in the package gvfs - 1.36.1-0ubuntu1.3.2

---
gvfs (1.36.1-0ubuntu1.3.2) bionic; urgency=medium

  * No change rebuild to pick up the current samba version.
The patch git_smb_nt1.patch added to fix smb browsing requires a new
libsmb api to work and that's checked for at build time (lp: #1778322)

 -- Sebastien Bacher   Wed, 08 May 2019 10:48:17
+0200

** Changed in: gvfs (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs:
  Unknown
Status in samba:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Released
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Fix Released
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click

[Desktop-packages] [Bug 1833555] Re: Add OEM->Family

This bug was fixed in the package ubuntu-report - 1.6.0

---
ubuntu-report (1.6.0) eoan; urgency=medium

  * Add product_family to OEM information (LP: #1833555)
  * Various test fixes

 -- Jean-Baptiste Lallement   Mon,
24 Jun 2019 11:10:02 +0200

** Changed in: ubuntu-report (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Add OEM->Family

Status in ubuntu-report package in Ubuntu:
  Fix Released
Status in ubuntu-report source package in Bionic:
  New

Bug description:
  Some OEM store the commercial name of the product into the Family
  field of the system information record of smbios.

  Please add this fied to ubuntu-report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-report 1.5.1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 14:49:35 2019
  Dependencies:
   gcc-9-base 9.1.0-4ubuntu1
   libc6 2.29-0ubuntu2
   libgcc1 1:9.1.0-4ubuntu1
   libidn2-0 2.0.5-1
   libunistring2 0.9.10-1ubuntu2
  InstallationDate: Installed on 2014-07-15 (1801 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: ubuntu-report
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (452 days ago)

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

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

[Desktop-packages] [Bug 1822351] Re: Nautilus does not open after updating to 19.04

2019-06-24 Thread Murshid Ahmed

Same issue for me. It was working for a while and all of a sudden it
stopped. The workaround mentioned in #2 doesn't work for me.

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

Title:
  Nautilus does not open after updating to 19.04

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  After updating to Ubuntu 19.04 dev branch, nautilus does not open at
  all. Moreover, trying to open nautilus from the terminal does not give
  any error, nor any output at all, and no window opens.

  I don't really know how to report this bug without any terminal
  output.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 13:58:12 2019
  InstallationDate: Installed on 2018-02-23 (398 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1831624] Re: ibus-cangjie in libreoffice cannot type Chinese character at end of line

2019-06-24 Thread Marcus Tomlinson

I'm still unable to reproduce this issue unfortunately, however, in
testing this I did stumble across a bug which may actually be the root
cause: https://bugs.documentfoundation.org/show_bug.cgi?id=126068

I've linked the upstream bug to this one. Let's give this another try
once that is resolved.

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

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

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

Title:
  ibus-cangjie in libreoffice cannot type Chinese character at end of
  line

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

Bug description:
  I am using LibreOffice Version: 6.0.7.3, in particular I am using
  LibreOffice Writer.

  I am using ibus-cangjie to input Chinese.

  I cannot input any Chinese characters when I reach the end of a line
  on the screen.

  The expected behavior is that the typed Chinese character simply
  spills over to the next line and I can continue to type without a
  problem.

  If I reach the end of the line with half a space (of full-sized
  Chinese character) available, then I could insert a punctuation mark
  like 。 or 、 even if I use cangjie codes to input them (and then I can
  continue normally).

  if I reach the end of the line with no space available, then I cannot
  insert 。 or 、 when I use cangjie codes to input them (in the ibus-
  cangjie standard input table, 、 = XI)

  In neither case I can type a Chinese character like 日, all the typed
  characters simply disappears from the input queue and is not typed at
  all.  Note that as I type I can see that the candidate Chinese
  characters according to the cangjie codes I input, they just don't get
  sent to the application.

  when I am at the end of the line, I can type as many spaces as I want
  and the problem of being unable to type a Chinese character persists.

  Finally, the bug only triggers when I am at the end of text; if I am
  inserting in the middle of text, even if I am at the linebreak, I can
  type normally and naturally.

  the attached screenshot shows where I am getting my cursor stuck.

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

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

This bug was fixed in the package gvfs - 1.38.1-0ubuntu1.3.1

---
gvfs (1.38.1-0ubuntu1.3.1) cosmic; urgency=medium

  * No change rebuild to pick up the current samba version.
The patch git_smb_nt1.patch added to fix smb browsing requires a new
libsmb api to work and that's checked for at build time (lp: #1778322)

 -- Sebastien Bacher   Wed, 08 May 2019 11:17:32
+0200

** Changed in: gvfs (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs:
  Unknown
Status in samba:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Committed
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Fix Released
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click

[Desktop-packages] [Bug 1778322] Update Released

2019-06-24 Thread Łukasz Zemczak

The verification of the Stable Release Update for gvfs 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 gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1778322

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs:
  Unknown
Status in samba:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Committed
Status in samba source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Fix Released
Status in samba source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The so called "browsing a windows network" made use of an SMB1 protocol 
version feature. Recent versions of samba, including the one released with 
bionic, default to a higher versions of the protocol which lacks this feature. 
As a result, the "other locations -> windows network" tab in Nautilus is empty 
even when there are windows or samba machines in the network.
  Accessing such machines directly, via smb:/// type urls, 
continues to work.

  The fix is two-fold:
  - introduce a new samba API call that can be used to set the protocol version 
to use
  - change applications to make use of this API call to set the protocol versio 
to SMB1/NT1 just for the network browsing

  gvfs was updated to make use of this api call, if detected at build
  time. To complete this SRU, gvfs needs a no-change rebuild *after*
  samba was accepted into proposed.

  [Test case]
  * Launch a bionic desktop vm. You can start with a server one, and then 
install the "ubuntu-desktop" package. In the same command, also install the 
packages we need for this test:
  $ sudo apt update
  $ sudo apt install ubuntu-desktop samba smbclient

  * set a password for the ubuntu user, so you can login at the graphical 
console
  $ sudo passwd ubuntu

  * set the same password for the ubuntu samba user:
  sudo smbpasswd -a ubuntu

  * add a simple [pub] share to samba:
  $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a 
/etc/samba/smb.conf

  * reboot
  $ sudo reboot

  * login at the graphical console as the ubuntu user. Go through the
  first-user-setup motions as you want.

  * try to browse the windows network via "other locations -> windows
  network". You will get an empty folder.

  * update the samba and gvfs packages
  * logout and login again on the gui, browse the windows network again. This 
time it will show the "WORKGROUP" folder, and if you click through, you will 
see yourself (your VM) and the [pub] share, among others.

  * click on the "pub" share, select registered user and login with the
  ubuntu credentials you created earlier with smbpasswd.

  * in another terminal, run this command to confirm that the SMB protocol 
version that was used to connect to [pub] was not just NT1/SMB1, but higher:
  $ sudo smbstatus
  ...
  8779ubuntu   ubuntu   192.168.122.94 (ipv4:192.168.122.94:60818) 
SMB3_11   -partial(AES-128-CMAC)

  Note "SMB3_11" above.

  
  [Regression potential]
  The samba update itself just introduces and exposes a new API call. It's up 
to other applications to make use of that. gvfs was patched to detect this call 
at build time and use it if it's detected.
  Packages that are not rebuilt will not see the change, and packages that 
*are* rebuilt will only see the change if they make use of it.

  [Other Info]
  This update introduces a specific runtime dependency between gvfs and 
libsmbclient due to the new API call added to the latter. Any package that is 
rebuilt with libsmbclient and makes use of that API call will get this specific 
dependency. This is handled automatically by dh_mkshlibs.

  To complete this SRU, gvfs will need a no-change rebuild after samba
  was accepted into proposed.

  Disco's gvfs is already using the new call, as can be seen in this build log 
https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz:
  ...
  Dependency smbclient found: YES 0.5.0
  Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES

  The smbc_setOptionProtocols() call is only used when the url is like
  "smb:///", or the server cannot be resolved. The downgrade overrides
  the setting in smb.conf, and is used just for this case: browsing the
  network. When connecting to a machine, the url is like
  "smb:///", and then this function we are adding is not called.

  I updated the test to actually click on the machine

[Desktop-packages] [Bug 25830] Re: Option to display file in browser, treat as text/plain

2019-06-24 Thread era

@jwatt What's this about a mass bug change? The link is to an
uninformative routine comment on an unrelated bug report, and googling
for similar comments only brings up this single bug report. Was this a
failed test for an upcoming actual mass bug change? Or can you explain
what it means with a correct link, or more information about what the
link means?

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

Title:
  Option to display file in browser, treat as text/plain

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

Bug description:
  A suggestion:

  When you click certain files, like .py or .pl files, for example, Firefox 
brings
  up a dialog that offers you the ability to:
  1. Open with a certain application
  2. Save to disk
  What would be nice is a third option:
  3. Treat as text/plain

  The wording could be altered... "Display as text in browser" or
  something.

  Sometimes you just want to quickly visit a file on the web and look for
  something in it, and the fact that you *could* open it in a more customized
  application is true but not really easier for you at that moment. If you just
  want to look a Python script for a version number at the top it is not 
necessary
  to open it in your IDE or save it to disk; you just want to open it in the
  normal viewing window as plain text and quickly find what you need to look at.

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

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

[Desktop-packages] [Bug 1833555] Re: Add OEM->Family

2019-06-24 Thread Jean-Baptiste Lallement

** Changed in: ubuntu-report (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: ubuntu-report (Ubuntu)
   Importance: Low => Medium

** Changed in: ubuntu-report (Ubuntu Bionic)
   Importance: Undecided => Medium

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

Title:
  Add OEM->Family

Status in ubuntu-report package in Ubuntu:
  Triaged
Status in ubuntu-report source package in Bionic:
  New

Bug description:
  Some OEM store the commercial name of the product into the Family
  field of the system information record of smbios.

  Please add this fied to ubuntu-report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-report 1.5.1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 14:49:35 2019
  Dependencies:
   gcc-9-base 9.1.0-4ubuntu1
   libc6 2.29-0ubuntu2
   libgcc1 1:9.1.0-4ubuntu1
   libidn2-0 2.0.5-1
   libunistring2 0.9.10-1ubuntu2
  InstallationDate: Installed on 2014-07-15 (1801 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: ubuntu-report
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (452 days ago)

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

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

[Desktop-packages] [Bug 1833555] Re: Add OEM->Family

2019-06-24 Thread Didier Roche

** Also affects: ubuntu-report (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  Add OEM->Family

Status in ubuntu-report package in Ubuntu:
  Triaged
Status in ubuntu-report source package in Bionic:
  New

Bug description:
  Some OEM store the commercial name of the product into the Family
  field of the system information record of smbios.

  Please add this fied to ubuntu-report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-report 1.5.1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 14:49:35 2019
  Dependencies:
   gcc-9-base 9.1.0-4ubuntu1
   libc6 2.29-0ubuntu2
   libgcc1 1:9.1.0-4ubuntu1
   libidn2-0 2.0.5-1
   libunistring2 0.9.10-1ubuntu2
  InstallationDate: Installed on 2014-07-15 (1801 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: ubuntu-report
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (452 days ago)

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

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

[Desktop-packages] [Bug 1833745] Re: [MIR] required new dependency of appstream

2019-06-24 Thread Rik Mills

** Description changed:

Availability

Built for all supported architectures. One upstream release ahead of Debian.

Rationale
=
Now a required build and runtime dependency of appstream in -proposed in Eoan

https://github.com/ximion/appstream/commit/358e9394631b87797f56dcb7e09e459b4044e631#commitcomment-33995178

Quote "Compiling AppStream without LMDB is not really possible."

Security

No known CVEs.
https://security-tracker.debian.org/tracker/source-package/lmdb

Quality assurance
=
+ - Desktop Packages team is subscribed.
- dh_auto_test run at build time for supported architectures.
- No functional outstanding bugs in Ubuntu or Debian. Upstream 'issue'
tracker is active.
https://bugs.launchpad.net/ubuntu/+source/lmdb
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=lmdb

https://www.openldap.org/its/index.cgi/Software%20Bugs?page=1;expression=lmdb;page=1

Dependencies

No universe binary dependencies

Standards compliance

4.1.5.0 , debhelper compat 9

Maintenance
===
Actively maintained:

http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=history;f=libraries/liblmdb;hb=HEAD

Not team maintained in Debian.
https://tracker.debian.org/pkg/lmdb

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

Title:
[MIR] required new dependency of appstream

Status in lmdb package in Ubuntu:
New

Bug description:
Availability

Built for all supported architectures. One upstream release ahead of Debian.

Rationale
=
Now a required build and runtime dependency of appstream in -proposed in Eoan

https://github.com/ximion/appstream/commit/358e9394631b87797f56dcb7e09e459b4044e631#commitcomment-33995178

Quote "Compiling AppStream without LMDB is not really possible."

Security

No known CVEs.
https://security-tracker.debian.org/tracker/source-package/lmdb

https://www.openldap.org/its/index.cgi/Software%20Bugs?page=1;expression=lmdb;page=1

Dependencies

No universe binary dependencies

Standards compliance

4.1.5.0 , debhelper compat 9

Maintenance
===
Actively maintained:

http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=history;f=libraries/liblmdb;hb=HEAD

Not team maintained in Debian.
https://tracker.debian.org/pkg/lmdb

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

[Desktop-packages] [Bug 1833745] Re: [MIR] required new dependency of appstream

2019-06-24 Thread Christian Ehrhardt 

[Reasoning]
So far lmdb was disabled e.g. in bind9 [2], but as outlined in the referred 
patch [1] this can't really be disabled in AppStream.
So lets take a look, fortunately it seems rather small.

[Duplication]
LMDB is a very thin in memory database. You'd think either of big databases 
which these days almost all grew in-memory features or mid sized projects like 
memchached.
But none of these really fits in the same size/use-as-lib/key-value-only 
tradeoff that LMDB tries to address.
Leveldb comes to mind [3] but that isn't in main either.

So while it feels like "oh no, another in-mem DB" I can't find something that 
would be a proper replacement.
Also given that bind9, postfix and appstream switched to it makes it less of a 
special on-off snowflake.

[Embedded sources and static linking]
- no other embedded libraries
- no static build
- no golang

[Security]
- no CVEs yet
- does not run as a daemon itself (lib)
- doesn't use webkit1,2
- doesn't use lib*v8 directly
- does not open a port
- does not processe arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)

The one usual check that applies is that to some extend it "parses data 
formats" when it persists and reads them from/to disk.
Also the content at least - in the use case triggering this being appstream - 
can be partially remote.

Further the mmapped files represent a new "attack vector" against tools using 
this in replacement for internal variables.
Following the "if in doubt let security check it" rule this will need a 
security review as well.

[Common blockers]
- no FTBFS currently
- runtime builds and runs test suite
- lib only without a lot user visible messages (no translation need)
- not a python package

The package lacks a team subscriber, some team has to step up - since
driven by appstream (bug 1538293) probably the Desktop Team?


[Packaging red flags]
- no Ubuntu delta atm
- symbols file exists and it tracked
- d/watch is present
- regular updates in Debian and by Upstream (no big moves, just minor versiosn)
- the current release is packaged
- currently just a sync, so no issue for MOTUs
- only very minor lintian warnings
- d/rules fits a page and debian/* in general is rather clean
- no use of Built-Using
- no golang

[Upstream red flags]
- developed under the umbrella of the openldap project [5] by symas [4]
- some warnigns on
  Wimplicit-fallthrough
  obsolete tags
  undocumented macros
  Nothing severe
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH
- no use of user nobody
- no use of setuid
- no open important bugs in Debian or Ubuntu or Upstream
- no use of webkit, qtwebkit, seed or libgoa-*
- not in scope for the Unity Dash (or other recent UI)

[Summary]
Approved by MIR team under the two following constraints
- needs package subscriber (I susbcribed didrocks to consider it)
- needs security review

[1]: 
https://github.com/ximion/appstream/commit/358e9394631b87797f56dcb7e09e459b4044e631#commitcomment-33995178
[2]: 
https://github.com/ximion/appstream/commit/358e9394631b87797f56dcb7e09e459b4044e631#commitcomment-33995446
[3]: 
https://mozilla.github.io/firefox-browser-architecture/text/0017-lmdb-vs-leveldb.html
[4]: https://symas.com/lmdb/
[5]: https://github.com/openldap/openldap/tree/master/libraries/liblmdb


** Changed in: lmdb (Ubuntu)
 Assignee: Christian Ehrhardt  (paelzer) => Ubuntu Security Team 
(ubuntu-security)

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

Title:
  [MIR] required new dependency of appstream

Status in lmdb package in Ubuntu:
  New

Bug description:
  Availability
  
  Built for all supported architectures. One upstream release ahead of Debian.

  Rationale
  =
  Now a required build and runtime dependency of appstream in -proposed in Eoan

  
https://github.com/ximion/appstream/commit/358e9394631b87797f56dcb7e09e459b4044e631#commitcomment-33995178

  Quote "Compiling AppStream without LMDB is not really possible."

  Security
  
  No known CVEs.
  https://security-tracker.debian.org/tracker/source-package/lmdb

  Quality assurance
  =
  - Desktop Packages team is subscribed.
  - dh_auto_test run at build time for supported architectures.
  - No functional outstanding bugs in Ubuntu or Debian. Upstream 'issue' 
tracker is active.
  https://bugs.launchpad.net/ubuntu/+source/lmdb
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=lmdb
  
https://www.openldap.org/its/index.cgi/Software%20Bugs?page=1;expression=lmdb;page=1

  Dependencies
  
  No universe binary dependencies

  Standards compliance
  
  4.1.5.0 , debhelper compat 9

  Maintenance
  ===
  Actively maintained:

[Desktop-packages] [Bug 1525454] Re: bootstrapping mono compiler fails at mdoc

2019-06-24 Thread Gianfranco Costamagna

Debian decided to just stop building mdocs on s390x with the following patch on 
rules file (applied conditionally on s390x only).
+CONF_FLAGS += --with-mcs-docs=no


I dropped the Ubuntu delta, now that s390x builds fine, and the optimization 
level is back to the default one
(I think no docs is better than not optimized binary!)

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

Title:
  bootstrapping mono compiler fails at mdoc

Status in mono package in Ubuntu:
  Fix Released

Bug description:
  mdoc fails when bootstrapping mono

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

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

[Desktop-packages] [Bug 1833991] [NEW] Unable to connect to Android phones via mtp (usbfs: process did not claim interface 0 before use)

2019-06-24 Thread Karl Kastner

Public bug reported:

I cannot connect to my Huawei P20 Lite running Android 8.0 via mtp. This
does neither work with mtp-tools, jmtp-fs nor gmtp. Creation of a
device-specific udev-rule did not help.

sudo mtp-connect 
[sudo] password for pia: 
libmtp version: 1.1.13

Device 0 (VID=12d1 and PID=107e) is a Huawei P9 Plus.
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, 
trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on 
second attempt
No devices.

dmesg excerpt:

[ 3987.745858] usb 3-3: usbfs: process 22111 (mtp-detect) did not claim
interface 0 before use

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: mtp-tools 1.1.13-1
Uname: Linux 4.15.0-041500rc6-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jun 24 10:25:12 2019
InstallationDate: Installed on 2015-11-05 (1326 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: Notebook W230SS
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-041500rc6-generic 
root=UUID=72336061-5fc7-4600-beb4-237209b65813 ro uveau.modeset=0 
acpi_enforce_resources=lax nosplash uveau.modeset=0 acpi_enforce_resources=lax 
acpi_enforce_resources=lax acpi_enforce_resources=lax 
acpi_enforce_resources=lax acpi_enforce_resources=lax acpi_enforce_resources=lax
RelatedPackageVersions: udev 237-3ubuntu10.19
SourcePackage: libmtp
UpgradeStatus: Upgraded to bionic on 2018-05-24 (395 days ago)
dmi.bios.date: 04/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W230SS
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W230SS
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

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


** Tags: amd64 apport-bug bionic

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

Title:
  Unable to connect to Android phones via mtp (usbfs: process did not
  claim interface 0 before use)

Status in libmtp package in Ubuntu:
  New

Bug description:
  I cannot connect to my Huawei P20 Lite running Android 8.0 via mtp.
  This does neither work with mtp-tools, jmtp-fs nor gmtp. Creation of a
  device-specific udev-rule did not help.

  sudo mtp-connect 
  [sudo] password for pia: 
  libmtp version: 1.1.13

  Device 0 (VID=12d1 and PID=107e) is a Huawei P9 Plus.
  ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, 
trying again after resetting USB interface
  LIBMTP libusb: Attempt to reset device
  ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on 
second attempt
  No devices.

  dmesg excerpt:

  [ 3987.745858] usb 3-3: usbfs: process 22111 (mtp-detect) did not
  claim interface 0 before use

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mtp-tools 1.1.13-1
  Uname: Linux 4.15.0-041500rc6-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 24 10:25:12 2019
  InstallationDate: Installed on 2015-11-05 (1326 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Notebook W230SS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-041500rc6-generic 
root=UUID=72336061-5fc7-4600-beb4-237209b65813 ro uveau.modeset=0 
acpi_enforce_resources=lax nosplash uveau.modeset=0 acpi_enforce_resources=lax 
acpi_enforce_resources=lax acpi_enforce_resources=lax 
acpi_enforce_resources=lax acpi_enforce_resources=lax acpi_enforce_resources=lax
  RelatedPackageVersions: udev 237-3ubuntu10.19
  SourcePackage: libmtp
  UpgradeStatus: Upgraded to bionic on 2018-05-24 (395 days ago)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

[Desktop-packages] [Bug 1833745] Re: [MIR] required new dependency of appstream

2019-06-24 Thread Christian Ehrhardt 

** Changed in: lmdb (Ubuntu)
 Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

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

Title:
  [MIR] required new dependency of appstream

Status in lmdb package in Ubuntu:
  New

Bug description:
  Availability
  
  Built for all supported architectures. One upstream release ahead of Debian.

  Rationale
  =
  Now a required build and runtime dependency of appstream in -proposed in Eoan

  
https://github.com/ximion/appstream/commit/358e9394631b87797f56dcb7e09e459b4044e631#commitcomment-33995178

  Quote "Compiling AppStream without LMDB is not really possible."

  Security
  
  No known CVEs.
  https://security-tracker.debian.org/tracker/source-package/lmdb

  Quality assurance
  =
  - dh_auto_test run at build time for supported architectures.
  - No functional outstanding bugs in Ubuntu or Debian. Upstream 'issue' 
tracker is active.
  https://bugs.launchpad.net/ubuntu/+source/lmdb
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=lmdb
  
https://www.openldap.org/its/index.cgi/Software%20Bugs?page=1;expression=lmdb;page=1

  Dependencies
  
  No universe binary dependencies

  Standards compliance
  
  4.1.5.0 , debhelper compat 9

  Maintenance
  ===
  Actively maintained:
  
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=history;f=libraries/liblmdb;hb=HEAD

  Not team maintained in Debian.
  https://tracker.debian.org/pkg/lmdb

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

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

[Desktop-packages] [Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)