[Desktop-packages] [Bug 1870728] [NEW] gnome shell dock disappeared

2020-04-03 Thread Jerry Quinn
Public bug reported:

I had to restart gnome shell to get the dock to reappear with Alt-F2 r
(which I hear doesn't work in newer Ubuntu).

There are a number of gnome-shell issues in syslog:

Apr  4 00:15:21 cerberus gnome-shell[4263]: System monitor applet enabling
Apr  4 00:15:22 cerberus gnome-shell[4263]: error reading: 
/sys/class/hwmon/hwmon0/fan1_input
Apr  4 00:15:22 cerberus gnome-shell[4263]: System monitor applet enabling done
Apr  4 00:15:22 cerberus gnome-shell[4263]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem :1.319/StatusNotifierItem
Apr  4 00:15:22 cerberus gnome-shell[4263]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.105/org/ayatana/NotificationItem/software_update_available
Apr  4 00:15:22 cerberus gnome-shell[4263]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.69/org/ayatana/NotificationItem/org_gnome_Pomodoro
Apr  4 00:15:22 cerberus gnome-shell[4263]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem :1.105/org/ayatana/NotificationItem/livepatch
Apr  4 00:15:22 cerberus gnome-shell[4263]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.70/org/ayatana/NotificationItem/classicmenu_indicator
Apr  4 00:15:23 cerberus gnome-shell[4263]: [AppIndicatorSupport-DEBUG] Using 
Brute-force mode for StatusNotifierItem 
:1.67/org/ayatana/NotificationItem/indicator_cpufreq
Apr  4 00:15:23 cerberus gnome-shell[4263]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.67/org/ayatana/NotificationItem/indicator_cpufreq
Apr  4 00:15:23 cerberus kernel: [201601.586313] sr 5:0:0:0: [sr0] tag#29 
FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr  4 00:15:23 cerberus kernel: [201601.586316] sr 5:0:0:0: [sr0] tag#29 Sense 
Key : Illegal Request [current] 
Apr  4 00:15:23 cerberus kernel: [201601.586319] sr 5:0:0:0: [sr0] tag#29 Add. 
Sense: Read of scrambled sector without authentication
Apr  4 00:15:23 cerberus kernel: [201601.586322] sr 5:0:0:0: [sr0] tag#29 CDB: 
Read(10) 28 00 00 3a 8a 40 00 00 40 00
Apr  4 00:15:23 cerberus kernel: [201601.586323] print_req_error: I/O error, 
dev sr0, sector 15345920
Apr  4 00:15:23 cerberus kernel: [201601.670291] sr 5:0:0:0: [sr0] tag#0 FAILED 
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr  4 00:15:23 cerberus kernel: [201601.670295] sr 5:0:0:0: [sr0] tag#0 Sense 
Key : Illegal Request [current] 
Apr  4 00:15:23 cerberus kernel: [201601.670298] sr 5:0:0:0: [sr0] tag#0 Add. 
Sense: Read of scrambled sector without authentication
Apr  4 00:15:23 cerberus kernel: [201601.670300] sr 5:0:0:0: [sr0] tag#0 CDB: 
Read(10) 28 00 00 3a 8a 60 00 00 01 00
Apr  4 00:15:23 cerberus kernel: [201601.670303] print_req_error: I/O error, 
dev sr0, sector 15346048
Apr  4 00:15:23 cerberus kernel: [201601.670307] Buffer I/O error on dev sr0, 
logical block 3836512, async page read
Apr  4 00:15:23 cerberus kernel: [201601.730390] sr 5:0:0:0: [sr0] tag#2 FAILED 
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr  4 00:15:23 cerberus kernel: [201601.730394] sr 5:0:0:0: [sr0] tag#2 Sense 
Key : Illegal Request [current] 
Apr  4 00:15:23 cerberus kernel: [201601.730399] sr 5:0:0:0: [sr0] tag#2 Add. 
Sense: Read of scrambled sector without authentication
Apr  4 00:15:23 cerberus kernel: [201601.730402] sr 5:0:0:0: [sr0] tag#2 CDB: 
Read(10) 28 00 00 3a 8a 61 00 00 01 00
Apr  4 00:15:23 cerberus kernel: [201601.730405] print_req_error: I/O error, 
dev sr0, sector 15346052
Apr  4 00:15:23 cerberus kernel: [201601.730411] Buffer I/O error on dev sr0, 
logical block 3836513, async page read
Apr  4 00:15:23 cerberus gvfsd-metadata[4709]: g_udev_device_has_property: 
assertion 'G_UDEV_IS_DEVICE (device)' failed
Apr  4 00:15:23 cerberus gvfsd-metadata[4709]: g_udev_device_has_property: 
assertion 'G_UDEV_IS_DEVICE (device)' failed
Apr  4 00:15:28 cerberus gnome-shell[4263]: [AppIndicatorSupport-WARN] 
Attempting to re-register :1.67/org/ayatana/NotificationItem/indicator_cpufreq; 
resetting instead
Apr  4 00:15:28 cerberus gnome-shell[4263]: [AppIndicatorSupport-WARN] Item 
:1.67/org/ayatana/NotificationItem/indicator_cpufreq is already registered
Apr  4 00:15:33 cerberus gnome-shell[4263]: [AppIndicatorSupport-WARN] While 
reading menu layout: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: No such object path 
'/MenuBar'
Apr  4 00:15:33 cerberus gnome-shell[4263]: [AppIndicatorSupport-WARN] Could 
not retrieve properties: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: No such object path 
'/MenuBar'
Apr  4 00:15:33 cerberus gnome-shell[4263]: Object 
.Gjs_AppIndicatorIconActor__1 (0x55f34ac7a040), has been already finalized. 
Impossible to set any property to it.
Apr  4 00:15:33 cerberus org.gnome.Shell.desktop[4263]: == Stack trace for 
context 0x55f34023c320 ==
Apr  4 00:15:33 cerberus org.gnome.Shell.desktop[4263]: #0 0x7ffefdb014d0 I   
resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7f9bb40b5de0 @ 87)
Apr  4 00:15:33 cerberus org.gnome.She

[Desktop-packages] [Bug 1870726] [NEW] Ubuntu Login Screen Loop

2020-04-03 Thread Rajkumar S
Public bug reported:

* Ubuntu Focal Fossa 20.04 (dev)
* xorg:
  Installed: 1:7.7+19ubuntu14
  Candidate: 1:7.7+19ubuntu1

Expected : Show desktop after login
Happened : On login screen, when password is entered correctly, it gets into a 
loop and shows the login screen again. But, it takes me to desktop properly if 
Ubuntu on Wayland is selected.

Steps to reproduce : 
1) Install Ubuntu 20 on an Oracle VirtualBox
2) Start a live session
3) Click the install button (Entire disk, Apply updates automatic)
4) After reboot, try to login.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 10:28:22 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2020-04-04 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=d609fc71-9cba-4875-8bc1-795cb584a629 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu wayland-session

** Attachment added: "The video showing what actually happens."
   
https://bugs.launchpad.net/bugs/1870726/+attachment/5345984/+files/AayrBV8M.mp4

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

Title:
  Ubuntu Login Screen Loop

Status in xorg package in Ubuntu:
  New

Bug description:
  * Ubuntu Focal Fossa 20.04 (dev)
  * xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu1

  Expected : Show desktop after login
  Happened : On login screen, when password is entered correctly, it gets into 
a loop and shows the login screen again. But, it takes me to desktop properly 
if Ubuntu on Wayland is selected.

  Steps to reproduce : 
  1) Install Ubuntu 20 on an Oracle VirtualBox
  2) Start a live session
  3) Click the install button (Entire disk, Apply updates automatic)
  4) After reboot, try to login.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 10:28:22 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2020-04-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=d60

[Desktop-packages] [Bug 1870727] [NEW] JS ERROR _workspaceIsolation is undefined

2020-04-03 Thread Jerry Quinn
Public bug reported:

>From syslog:

Apr  4 01:04:02 cerberus gnome-shell[4263]: JS ERROR: TypeError: monitor is 
null#012_reposition@resource:///org/gnome/shell/ui/boxpointer.js:508:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_allocate@resource:///org/gnome/shell/ui/boxpointer.js:235:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_init/<@resource:///org/gnome/shell/ui/layout.js:210:17#012_updateRegions@resource:///org/gnome/shell/ui/layout.js:989:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
Apr  4 01:04:02 cerberus gnome-shell[4263]: JS WARNING: 
[/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js 1778]: 
reference to undefined property "_workspaceIsolation"
Apr  4 01:04:02 cerberus gnome-shell[4263]: JS ERROR: TypeError: 
this._workspaceIsolation is 
undefined#012DockManager<._deleteDocks@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1778:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012DockManager<._toggle@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1662:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
Apr  4 01:04:02 cerberus gnome-shell[4263]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.70/org/ayatana/NotificationItem/classicmenu_indicator
Apr  4 01:04:02 cerberus gnome-shell[4263]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.105/org/ayatana/NotificationItem/software_update_available
Apr  4 01:04:02 cerberus gnome-shell[4263]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem :1.105/org/ayatana/NotificationItem/livepatch
Apr  4 01:04:02 cerberus gnome-shell[4263]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.69/org/ayatana/NotificationItem/org_gnome_Pomodoro

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.4-0ubuntu18.04.3
ProcVersionSignature: Ubuntu 4.15.0-94.95-generic 4.15.18
Uname: Linux 4.15.0-94-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 01:10:22 2020
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' b"['bettervol...@tudmotu.com', 
'shortc...@kyle.aims.ac.za', 'system-moni...@paradoxxx.zero.gmail.com', 
'pomod...@arun.codito.in']"
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2016-05-30 (1404 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to bionic on 2018-09-17 (565 days ago)

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

Title:
  JS ERROR _workspaceIsolation is undefined

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  From syslog:

  Apr  4 01:04:02 cerberus gnome-shell[4263]: JS ERROR: TypeError: monitor is 
null#012_reposition@resource:///org/gnome/shell/ui/boxpointer.js:508:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_allocate@resource:///org/gnome/shell/ui/boxpointer.js:235:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_init/<@resource:///org/gnome/shell/ui/layout.js:210:17#012_updateRegions@resource:///org/gnome/shell/ui/layout.js:989:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
  Apr  4 01:04:02 cerberus gnome-shell[4263]: JS WARNING: 
[/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js 1778]: 
reference to undefined property "_workspaceIsolation"
  Apr  4 01:04:02 cerberus gnome-shell[4263]: JS ERROR: TypeError: 
this._workspaceIsolation is 
undefined#012DockManager<._deleteDocks@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1778:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012DockManager<._toggle@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1662:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
  Apr  4 01:04:02 cerberus gnome-shell[4263]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.70/org/ayatana/NotificationItem/classicmenu_indicator
  Apr  4 01:04:02 cerberus gnome-shell[4263]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.105/org/ayatana/NotificationItem/software_update_available
  Apr  4 01:04:02 cerberus gnome-shell[4263]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem :1.105/org/ayatana/NotificationItem/livepatch
  Apr 

[Desktop-packages] [Bug 1870721] Re: Ubuntu dock showing shortcut to "Dash to dock"

2020-04-03 Thread Alexandre Speltri
** Package changed: ubuntu => gnome-shell-extension-ubuntu-dock (Ubuntu)

** Description changed:

  1-) The release of Ubuntu: Ubuntu 20.04 Beta - everything updated -
  clean install, no installed extra extensions or programs
  
  2-)The version of the package you are using: Ubuntu dock extension
  version: 67ubuntu20.04.3
  
  3) What you expected to happen: Right clicking "Show applications"
  shouldn't show "Dash to dock settings"
  
  By default in "Dash to dock" - which Ubuntu dock is based on - when
  right clicking the "Show applications", the user gets a shortcut to the
  Dash to Dock settings. But this behavior is also present in the Ubuntu
  version of the extension. And if you try to open this "Dash to dock
  settings" using the Ubuntu dock (which shouldn't have an option to this
  shortcut at all), I get a notification with the following error message
  " Execution of "gnome-shell-extensions-prefs" failed: Command not found
  ".
- 
- PS: Launchpad pointed that "gnome-shell-extension-ubuntu-dock does not
- exist in Ubuntu", although it is installed by default.

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

Title:
  Ubuntu dock showing shortcut to "Dash to dock"

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

Bug description:
  1-) The release of Ubuntu: Ubuntu 20.04 Beta - everything updated -
  clean install, no installed extra extensions or programs

  2-)The version of the package you are using: Ubuntu dock extension
  version: 67ubuntu20.04.3

  3) What you expected to happen: Right clicking "Show applications"
  shouldn't show "Dash to dock settings"

  By default in "Dash to dock" - which Ubuntu dock is based on - when
  right clicking the "Show applications", the user gets a shortcut to
  the Dash to Dock settings. But this behavior is also present in the
  Ubuntu version of the extension. And if you try to open this "Dash to
  dock settings" using the Ubuntu dock (which shouldn't have an option
  to this shortcut at all), I get a notification with the following
  error message  " Execution of "gnome-shell-extensions-prefs" failed:
  Command not found ".

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

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


[Desktop-packages] [Bug 1854621] Re: ubuntu 20.04 daily boots with no background, selecting other background has warped picture

2020-04-03 Thread Chris Guiver
I ran a QA-test on (2020-Apr-03 ubu 20.04 desktop amd64)
dell [optiplex] 745 (c2d-6600, 6gb, amd/ati radeon rv516/x1300/x1550)
because lshw reports same video card, no glitches there with wallpaper on boot, 
nor changing wallpaper.

--- possibly unrelated
I did have that box boot the first time to "Oh No, something went wrong" and 
want me to logout, to get itself stuck in a loop..  I scanned dmesg and no 
squashfs errs, thought about filing then rebooted to see if it occurred again 
and nope.

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

Title:
  ubuntu 20.04 daily boots with no background, selecting other
  background has warped picture

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 daily - verified (check disc for defects) prior to boot.
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  On booting, the 20.04 daily has no background when desktop is loaded?
  (ie. top panel is there, dock on left side on black screen)

  When changing background (to any already installed), they are warped
  when selected and made the bacground as if corrupted (but small image
  where selection is made looks valid).


  This issue may relate to video card  [radeon]

  ubuntu@ubuntu:~$ sudo lshw -C video
*-display:0   
 description: VGA compatible controller
 product: RV516 [Radeon X1300/X1550 Series]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e 
ioport:dc00(size=256) memory:c-d
*-display:1 UNCLAIMED
 description: Display controller
 product: RV516 [Radeon X1300/X1550 Series] (Secondary)
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0.1
 bus info: pci@:01:00.1
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress bus_master cap_list
 configuration: latency=0
 resources: memory:fe9f-fe9f

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.440
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.432
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:58:33 2019
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1870721] [NEW] Ubuntu dock showing shortcut to "Dash to dock"

2020-04-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

1-) The release of Ubuntu: Ubuntu 20.04 Beta - everything updated -
clean install, no installed extra extensions or programs

2-)The version of the package you are using: Ubuntu dock extension
version: 67ubuntu20.04.3

3) What you expected to happen: Right clicking "Show applications"
shouldn't show "Dash to dock settings"

By default in "Dash to dock" - which Ubuntu dock is based on - when
right clicking the "Show applications", the user gets a shortcut to the
Dash to Dock settings. But this behavior is also present in the Ubuntu
version of the extension. And if you try to open this "Dash to dock
settings" using the Ubuntu dock (which shouldn't have an option to this
shortcut at all), I get a notification with the following error message
" Execution of "gnome-shell-extensions-prefs" failed: Command not found
".

PS: Launchpad pointed that "gnome-shell-extension-ubuntu-dock does not
exist in Ubuntu", although it is installed by default.

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


** Tags: bot-comment ubuntu-dock
-- 
Ubuntu dock showing shortcut to "Dash to dock"
https://bugs.launchpad.net/bugs/1870721
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu.

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


[Desktop-packages] [Bug 1870725] Re: artifacts appearing on gnome shell

2020-04-03 Thread Ryan Hirasaki
No problem!

When I change wallpapers the issue appears goes away but on reboot or
switching back the issue persists. it appears to not affect other
applications such as Firefox even when in full screen.

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

Title:
  artifacts appearing on gnome shell

Status in ubuntu-meta package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  problems appear on the desktop and lock screen (not in gdm)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 22:50:55 2020
  DistUpgraded: 2020-04-03 20:26:10,751 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2020-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: LENOVO 20L5CTO1WW
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=9aa1adb4-3c73-4d9b-8968-83630fb790f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-04 (0 days ago)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5CTO1WW
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1870725] Re: artifacts appearing on gnome shell

2020-04-03 Thread Chris Guiver
Thank you for taking the time to report this issue and helping to make
Ubuntu better.

If you change wallpapers, does the issue still occur?  Does it occur if
you have windows fullscreen (eg. if firefox is your open window and
maximized so it covers your wallpaper, do you see the artifacts?) or are
they visible only on your wallpaper?

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

Title:
  artifacts appearing on gnome shell

Status in ubuntu-meta package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  problems appear on the desktop and lock screen (not in gdm)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 22:50:55 2020
  DistUpgraded: 2020-04-03 20:26:10,751 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2020-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: LENOVO 20L5CTO1WW
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=9aa1adb4-3c73-4d9b-8968-83630fb790f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-04 (0 days ago)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5CTO1WW
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1745418] Re: Screen tearing with AMD APU on Ubuntu 18.04 and 17.10

2020-04-03 Thread Launchpad Bug Tracker
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Screen tearing with AMD APU on Ubuntu 18.04 and 17.10

Status in mesa package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  Hi,
  I have two PCs with AMD hardware: a desktop with AMD A10-7800 and a laptop 
with AMD A10-7300, so both with AMD Kaveri APUs.
  The operating system is Ubuntu 17.10 x64 both on the desktop and on the 
laptop.
  The good news is that the driver built into Ubuntu works fine. I hope I can 
improve yet but I am satisfied.
  The only problem occurs with the Opera browser: when I display something 
graphic, for example a video on YouTube or by scrolling the photos, it presents 
a lot of tearing. With Firefox this problem is not there.
  I have already reported this problem to Opera and AMD, but I do not think 
they have taken into account, because even the latest versions of Opera have 
screen tearing.
  I hope you can solve and work with AMD driver team and Opera because I would 
like to use that browser, thank you!

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

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


[Desktop-packages] [Bug 1745418] Re: Screen tearing with AMD APU on Ubuntu 18.04 and 17.10

2020-04-03 Thread Launchpad Bug Tracker
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Screen tearing with AMD APU on Ubuntu 18.04 and 17.10

Status in mesa package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  Hi,
  I have two PCs with AMD hardware: a desktop with AMD A10-7800 and a laptop 
with AMD A10-7300, so both with AMD Kaveri APUs.
  The operating system is Ubuntu 17.10 x64 both on the desktop and on the 
laptop.
  The good news is that the driver built into Ubuntu works fine. I hope I can 
improve yet but I am satisfied.
  The only problem occurs with the Opera browser: when I display something 
graphic, for example a video on YouTube or by scrolling the photos, it presents 
a lot of tearing. With Firefox this problem is not there.
  I have already reported this problem to Opera and AMD, but I do not think 
they have taken into account, because even the latest versions of Opera have 
screen tearing.
  I hope you can solve and work with AMD driver team and Opera because I would 
like to use that browser, thank you!

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

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


[Desktop-packages] [Bug 1855889] Re: Can't run Chromium since upgrade to Ubuntu 19.10

2020-04-03 Thread Launchpad Bug Tracker
[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/1855889

Title:
  Can't run Chromium since upgrade to Ubuntu 19.10

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  Hi,

  I try to run Chromium from the menu and nothing happens.
  If I run it from the CLI I get:
  cannot perform operation: mount --rbind /root /tmp/snap.rootfs_vWwNbw//root: 
Permission denied

  I tried uninstalling and reinstalling. I tried uninstalling and
  reinstalling snapd. Tried anything related I could find on-line, but
  nothing works.

  Upgrade snap to the latest version on the pre-release channel.

  For some reason Chromium does not show up in the Software centre
  either.

  Thanks for any help.

  $ lsb_release  -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ snap list chromium
  Name  VersionRev  Tracking  Publisher   Notes
  chromium  78.0.3904.108  958  stablecanonicalâ  -

  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 77.0.3865.120-0ubuntu1.19.10.1
Candidate: 77.0.3865.120-0ubuntu1.19.10.1
Version table:
   *** 77.0.3865.120-0ubuntu1.19.10.1 500
  500 http://mirror.overthewire.com.au/ubuntu eoan-updates/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   77.0.3865.120-0ubuntu1~snap1 500
  500 http://mirror.overthewire.com.au/ubuntu eoan/universe amd64 
Packages

  
  $ snap list chromium
  Name  VersionRev  Tracking  Publisher   Notes
  chromium  78.0.3904.108  958  stablecanonicalâ  -

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonicalâ
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more 
stable way for all
Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: stable
  refresh-date: today at 23:00 ACST
  channels:
stable:78.0.3904.108 2019-11-25 (958) 160MB -
candidate: 78.0.3904.108 2019-11-22 (952) 160MB -
beta:  79.0.3945.74  2019-12-06 (966) 155MB -
edge:  80.0.3983.2   2019-12-05 (964) 156MB -
  installed:   78.0.3904.108(958) 160MB

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

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


[Desktop-packages] [Bug 1858964] Re: gnome-software crashed with SIGABRT in raise()

2020-04-03 Thread Launchpad Bug Tracker
[Expired for gnome-software (Ubuntu) because there has been no activity
for 60 days.]

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

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

Title:
  gnome-software crashed with SIGABRT in raise()

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  a

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.30.6-2ubuntu11
  ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10
  Uname: Linux 5.3.0-24-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan  8 18:43:27 2020
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2020-01-08 (0 days ago)
  InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 
(20191230)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu11
  ProcCmdline: gnome-software
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_error () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-software crashed with SIGABRT in g_assertion_message_error()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1870152] Re: 'System Sounds' string showing not translated

2020-04-03 Thread Adolfo Jayme
** Changed in: ubuntu-translations
   Status: New => 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/1870152

Title:
  'System Sounds' string showing not translated

Status in gnome-control-center:
  Unknown
Status in Ubuntu Translations:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  Please check attachment

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

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


[Desktop-packages] [Bug 1870725] [NEW] artifacts appearing on gnome shell

2020-04-03 Thread Ryan Hirasaki
Public bug reported:

problems appear on the desktop and lock screen (not in gdm)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  3 22:50:55 2020
DistUpgraded: 2020-04-03 20:26:10,751 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
InstallationDate: Installed on 2020-03-30 (4 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
MachineType: LENOVO 20L5CTO1WW
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=9aa1adb4-3c73-4d9b-8968-83630fb790f2 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-04 (0 days ago)
dmi.bios.date: 02/19/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET56W (1.31 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K17763 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L5CTO1WW
dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug corruption focal ubuntu

** Attachment added: "Screenshot from 2020-04-03 21-08-18.png"
   
https://bugs.launchpad.net/bugs/1870725/+attachment/5345966/+files/Screenshot%20from%202020-04-03%2021-08-18.png

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  artifacts appearing on gnome shell

Status in ubuntu-meta package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  problems appear on the desktop and lock screen (not in gdm)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 22:50:55 2020
  DistUpgraded: 2020-04-03 20:26:10,751 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2020-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: LENOVO 20L5CTO1WW
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=9aa1adb4-3c73-4d9b-8968-83630fb790f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-04 (0 days ago)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.b

[Desktop-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

2020-04-03 Thread Phuc Minh Cai
Hi Hai Heng Feng,

How are you? Hope you're fine.

I saw it's already release kernel v5.6

Should I try with this kernel?

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

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
  - run udo apt-get install xserver-xorg-video-intel
  0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 14:29:01 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
  InstallationDate: Installed on 2020-01-24 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. T100HAN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T100HAN.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T100HAN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T100HAN
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1870692] Re: gnome-shell crashed with SIGABRT in __GI_raise()

2020-04-03 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1870692

** Tags added: iso-testing

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  QA-test using 2020-04-02 daily ISO of focal fossa
  It was a system problem detected (prior boot; .crash file saved to hdd). I 
don't know cause and didn't notice any side-effects, but system didn't have 
wallpaper showing correctly, and I was having trouble moving dock items around

  ** What I did

  (1) system booted with black background (no wallpaper) as reported on
  another reoprt (1854621), and in exploration of that i'd changed
  wallpaper many many times..

  (2) I also did some testing for 1867613 and moving icons on dock (left
  side of screen, right side of screen & at bottom where).

  (3) normal qa-tests

  ** Issue

  I got a System Problem detected, so NO abnormal behavior, and I don't
  know cause. This was a crash that occurred just prior to reboot; I'm
  filing on same box after reboot (so new session, but should be
  ~identical).  I don't know cause.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:20:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1585586945
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () 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
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1854621] Re: ubuntu 20.04 daily boots with no background, selecting other background has warped picture

2020-04-03 Thread Chris Guiver
Reboot of same box as #6; same ISO.

I have wallpaper visible this time, but tiny glitches visible at the top
in what could be top-panel or wallpaper.  As mostly dark it looks like
glitch is with top-panel, but if I make this firefox window full screen
the glitch is hidden thus part of wallpaper most likely

Screengrab uploaded of what I'm seeing this time.

To ensure screengrab showed issue, I viewed it in eye-of-gnome; I'm
getting glitches on the screen as I press  in eye-of-gnome to view
fullscreen; most (if not all) on screen glitches are occuring at top of
screen or top-panel, but that could be where easy to notice them..  It's
not just that program as I get same on screen glitches with firefox now.

** Attachment added: "Screenshot from 2020-04-04 02-02-32.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1854621/+attachment/5345959/+files/Screenshot%20from%202020-04-04%2002-02-32.png

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

Title:
  ubuntu 20.04 daily boots with no background, selecting other
  background has warped picture

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 daily - verified (check disc for defects) prior to boot.
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  On booting, the 20.04 daily has no background when desktop is loaded?
  (ie. top panel is there, dock on left side on black screen)

  When changing background (to any already installed), they are warped
  when selected and made the bacground as if corrupted (but small image
  where selection is made looks valid).


  This issue may relate to video card  [radeon]

  ubuntu@ubuntu:~$ sudo lshw -C video
*-display:0   
 description: VGA compatible controller
 product: RV516 [Radeon X1300/X1550 Series]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e 
ioport:dc00(size=256) memory:c-d
*-display:1 UNCLAIMED
 description: Display controller
 product: RV516 [Radeon X1300/X1550 Series] (Secondary)
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0.1
 bus info: pci@:01:00.1
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress bus_master cap_list
 configuration: latency=0
 resources: memory:fe9f-fe9f

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.440
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.432
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:58:33 2019
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1870692] Stacktrace.txt

2020-04-03 Thread Apport retracing service
** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1870692/+attachment/5345960/+files/Stacktrace.txt

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  QA-test using 2020-04-02 daily ISO of focal fossa
  It was a system problem detected (prior boot; .crash file saved to hdd). I 
don't know cause and didn't notice any side-effects, but system didn't have 
wallpaper showing correctly, and I was having trouble moving dock items around

  ** What I did

  (1) system booted with black background (no wallpaper) as reported on
  another reoprt (1854621), and in exploration of that i'd changed
  wallpaper many many times..

  (2) I also did some testing for 1867613 and moving icons on dock (left
  side of screen, right side of screen & at bottom where).

  (3) normal qa-tests

  ** Issue

  I got a System Problem detected, so NO abnormal behavior, and I don't
  know cause. This was a crash that occurred just prior to reboot; I'm
  filing on same box after reboot (so new session, but should be
  ~identical).  I don't know cause.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:20:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1585586945
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () 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
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1870692] StacktraceSource.txt

2020-04-03 Thread Apport retracing service
** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1870692/+attachment/5345961/+files/StacktraceSource.txt

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  QA-test using 2020-04-02 daily ISO of focal fossa
  It was a system problem detected (prior boot; .crash file saved to hdd). I 
don't know cause and didn't notice any side-effects, but system didn't have 
wallpaper showing correctly, and I was having trouble moving dock items around

  ** What I did

  (1) system booted with black background (no wallpaper) as reported on
  another reoprt (1854621), and in exploration of that i'd changed
  wallpaper many many times..

  (2) I also did some testing for 1867613 and moving icons on dock (left
  side of screen, right side of screen & at bottom where).

  (3) normal qa-tests

  ** Issue

  I got a System Problem detected, so NO abnormal behavior, and I don't
  know cause. This was a crash that occurred just prior to reboot; I'm
  filing on same box after reboot (so new session, but should be
  ~identical).  I don't know cause.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:20:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1585586945
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () 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
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1870692] ThreadStacktrace.txt

2020-04-03 Thread Apport retracing service
** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1870692/+attachment/5345962/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1870692/+attachment/5345947/+files/CoreDump.gz

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

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  QA-test using 2020-04-02 daily ISO of focal fossa
  It was a system problem detected (prior boot; .crash file saved to hdd). I 
don't know cause and didn't notice any side-effects, but system didn't have 
wallpaper showing correctly, and I was having trouble moving dock items around

  ** What I did

  (1) system booted with black background (no wallpaper) as reported on
  another reoprt (1854621), and in exploration of that i'd changed
  wallpaper many many times..

  (2) I also did some testing for 1867613 and moving icons on dock (left
  side of screen, right side of screen & at bottom where).

  (3) normal qa-tests

  ** Issue

  I got a System Problem detected, so NO abnormal behavior, and I don't
  know cause. This was a crash that occurred just prior to reboot; I'm
  filing on same box after reboot (so new session, but should be
  ~identical).  I don't know cause.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:20:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1585586945
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () 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
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1870692] gnome-shell crashed with SIGABRT in __GI_raise()

2020-04-03 Thread Apport retracing service
StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
 __GI_abort () at abort.c:79
 g_assertion_message.cold () from 
/tmp/apport_sandbox_r2i932cn/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1
 g_assertion_message_expr () from 
/tmp/apport_sandbox_r2i932cn/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1
 st_bin_destroy () from 
/tmp/apport_sandbox_r2i932cn/usr/lib/gnome-shell/libst-1.0.so

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  QA-test using 2020-04-02 daily ISO of focal fossa
  It was a system problem detected (prior boot; .crash file saved to hdd). I 
don't know cause and didn't notice any side-effects, but system didn't have 
wallpaper showing correctly, and I was having trouble moving dock items around

  ** What I did

  (1) system booted with black background (no wallpaper) as reported on
  another reoprt (1854621), and in exploration of that i'd changed
  wallpaper many many times..

  (2) I also did some testing for 1867613 and moving icons on dock (left
  side of screen, right side of screen & at bottom where).

  (3) normal qa-tests

  ** Issue

  I got a System Problem detected, so NO abnormal behavior, and I don't
  know cause. This was a crash that occurred just prior to reboot; I'm
  filing on same box after reboot (so new session, but should be
  ~identical).  I don't know cause.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:20:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1585586945
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () 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
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1867613] Re: Ubuntu dock does not allow drag and move icons at bottom

2020-04-03 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1867613

** Tags added: iso-testing

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

Title:
  Ubuntu dock does not allow drag and move icons at bottom

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

Bug description:
  Ubuntu 20.04 daily development branch @ 16/3/2020

  After a clean install daily at 14/3/2020 the ubuntu dock does not allow
  drag and move icons anymore with the dock placed at bottom
  you can still mouseclick and hold the icon, but it does not make space
  between other icons to release

  starting an application still showing the icon, and add to favorites
  still works

  the dock placed left or right it works better

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 16 12:31:30 2020
  InstallationDate: Installed on 2020-03-14 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1870692] [NEW] gnome-shell crashed with SIGABRT in __GI_raise()

2020-04-03 Thread Chris Guiver
Public bug reported:

QA-test using 2020-04-02 daily ISO of focal fossa
It was a system problem detected (prior boot; .crash file saved to hdd). I 
don't know cause and didn't notice any side-effects, but system didn't have 
wallpaper showing correctly, and I was having trouble moving dock items around

** What I did

(1) system booted with black background (no wallpaper) as reported on
another reoprt (1854621), and in exploration of that i'd changed
wallpaper many many times..

(2) I also did some testing for 1867613 and moving icons on dock (left
side of screen, right side of screen & at bottom where).

(3) normal qa-tests

** Issue

I got a System Problem detected, so NO abnormal behavior, and I don't
know cause. This was a crash that occurred just prior to reboot; I'm
filing on same box after reboot (so new session, but should be
~identical).  I don't know cause.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.0-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CasperVersion: 1.442
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 01:20:06 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1585586945
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/ubuntu
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
 __GI_abort () at abort.c:79
 ?? () 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
 ?? () from /usr/lib/gnome-shell/libst-1.0.so
Title: gnome-shell crashed with SIGABRT in __GI_raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

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


** Tags: amd64 apport-crash focal

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  QA-test using 2020-04-02 daily ISO of focal fossa
  It was a system problem detected (prior boot; .crash file saved to hdd). I 
don't know cause and didn't notice any side-effects, but system didn't have 
wallpaper showing correctly, and I was having trouble moving dock items around

  ** What I did

  (1) system booted with black background (no wallpaper) as reported on
  another reoprt (1854621), and in exploration of that i'd changed
  wallpaper many many times..

  (2) I also did some testing for 1867613 and moving icons on dock (left
  side of screen, right side of screen & at bottom where).

  (3) normal qa-tests

  ** Issue

  I got a System Problem detected, so NO abnormal behavior, and I don't
  know cause. This was a crash that occurred just prior to reboot; I'm
  filing on same box after reboot (so new session, but should be
  ~identical).  I don't know cause.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:20:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1585586945
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () 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
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1870690] [NEW] Settings starts but does not appear

2020-04-03 Thread Mike Gaudencio
Public bug reported:

Description:Ubuntu 19.10
Release:19.10

unity-control-center:
  Installed: 15.04.0+19.10.20190921-0ubuntu1
  Candidate: 15.04.0+19.10.20190921-0ubuntu1
  Version table:
 *** 15.04.0+19.10.20190921-0ubuntu1 500
500 http://mirrors.mit.edu/ubuntu eoan/universe amd64 Packages
100 /var/lib/dpkg/status

Steps:
- Click on "Show Applications"
- Click on "Settings"

Expected:
- Control panel to appear

Problem:
- Control panel appears in the toolbar briefly and then disappears

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
Uname: Linux 5.3.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  3 21:46:43 2020
InstallationDate: Installed on 2020-03-30 (4 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

** Summary changed:

- ettings starts but does not appear
+ Settings starts but does not appear

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

Title:
  Settings starts but does not appear

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 19.10
  Release:  19.10

  unity-control-center:
Installed: 15.04.0+19.10.20190921-0ubuntu1
Candidate: 15.04.0+19.10.20190921-0ubuntu1
Version table:
   *** 15.04.0+19.10.20190921-0ubuntu1 500
  500 http://mirrors.mit.edu/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  Steps:
  - Click on "Show Applications"
  - Click on "Settings"

  Expected:
  - Control panel to appear

  Problem:
  - Control panel appears in the toolbar briefly and then disappears

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 21:46:43 2020
  InstallationDate: Installed on 2020-03-30 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1867613] Re: Ubuntu dock does not allow drag and move icons at bottom

2020-04-03 Thread Chris Guiver
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

QA-test of focal fossa daily (2020-04-02) in 'live' session

requested to test for https://bugs.launchpad.net/ubuntu/+source/gnome-
shell-extension-ubuntu-dock/+bug/1867613 by lotuspsychje; i could move
icons on dock easily (working as intended 80-90% of the time when on
left, or right)

when dock is at the bottom I could only rarely moved icon on dock
rarely, nor add items from to dock with my attempts failing 80-90% of
the time now

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

Title:
  Ubuntu dock does not allow drag and move icons at bottom

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

Bug description:
  Ubuntu 20.04 daily development branch @ 16/3/2020

  After a clean install daily at 14/3/2020 the ubuntu dock does not allow
  drag and move icons anymore with the dock placed at bottom
  you can still mouseclick and hold the icon, but it does not make space
  between other icons to release

  starting an application still showing the icon, and add to favorites
  still works

  the dock placed left or right it works better

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 16 12:31:30 2020
  InstallationDate: Installed on 2020-03-14 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1854621] Re: ubuntu 20.04 daily boots with no background, selecting other background has warped picture

2020-04-03 Thread Chris Guiver
Changing wallpapers and on occasion the wallpaper would show correctly,
change it again sometimes it could get two change twice in a row without
glitches, then back to jarry-blocky mess for part of image on next
change (and usually 3-5 after that).

See #4 for pic; though % of jarry-block image and location varies, up to
80% of screen jarry-blocky but not always top of screen; can be lower
portion, or top & bottom but not middle... it's not consistent though
more commonly not right at top

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

Title:
  ubuntu 20.04 daily boots with no background, selecting other
  background has warped picture

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 daily - verified (check disc for defects) prior to boot.
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  On booting, the 20.04 daily has no background when desktop is loaded?
  (ie. top panel is there, dock on left side on black screen)

  When changing background (to any already installed), they are warped
  when selected and made the bacground as if corrupted (but small image
  where selection is made looks valid).


  This issue may relate to video card  [radeon]

  ubuntu@ubuntu:~$ sudo lshw -C video
*-display:0   
 description: VGA compatible controller
 product: RV516 [Radeon X1300/X1550 Series]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e 
ioport:dc00(size=256) memory:c-d
*-display:1 UNCLAIMED
 description: Display controller
 product: RV516 [Radeon X1300/X1550 Series] (Secondary)
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0.1
 bus info: pci@:01:00.1
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress bus_master cap_list
 configuration: latency=0
 resources: memory:fe9f-fe9f

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.440
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.432
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:58:33 2019
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1867613] Re: Ubuntu dock does not allow drag and move icons anymore

2020-04-03 Thread lotuspsychje
** Description changed:

  Ubuntu 20.04 daily development branch @ 16/3/2020
  
  After a clean install daily at 14/3/2020 the ubuntu dock does not allow
- drag and move icons anymore
+ drag and move icons anymore with the dock placed at bottom
  you can still mouseclick and hold the icon, but it does not make space
  between other icons to release
  
  starting an application still showing the icon, and add to favorites
  still works
+ 
+ the dock placed left or right it works better
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 16 12:31:30 2020
  InstallationDate: Installed on 2020-03-14 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- Ubuntu dock does not allow drag and move icons anymore
+ Ubuntu dock does not allow drag and move icons at bottom

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

Title:
  Ubuntu dock does not allow drag and move icons at bottom

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

Bug description:
  Ubuntu 20.04 daily development branch @ 16/3/2020

  After a clean install daily at 14/3/2020 the ubuntu dock does not allow
  drag and move icons anymore with the dock placed at bottom
  you can still mouseclick and hold the icon, but it does not make space
  between other icons to release

  starting an application still showing the icon, and add to favorites
  still works

  the dock placed left or right it works better

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 16 12:31:30 2020
  InstallationDate: Installed on 2020-03-14 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1854621] Re: ubuntu 20.04 daily boots with no background, selecting other background has warped picture

2020-04-03 Thread Chris Guiver
Sorry

Booted latest daily (03-Apr-2020) 'live' qa-test and on 
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

and whilst I like the 'smooth' bootup messages, it ends up booting to a
black screen without wallpaper (wallpapers was visible in background
during try/boot, and changing wallpapers/backgrounds has the same effect
as described so I won't add another screendump (see comment #4 for what
my current screen looks like)

I just noticed I have another box with the same `lshw` reported video
card so I'll endeavour to use the 'live' on that & other similar boxes
later today.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Incomplete => New

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

Title:
  ubuntu 20.04 daily boots with no background, selecting other
  background has warped picture

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 daily - verified (check disc for defects) prior to boot.
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  On booting, the 20.04 daily has no background when desktop is loaded?
  (ie. top panel is there, dock on left side on black screen)

  When changing background (to any already installed), they are warped
  when selected and made the bacground as if corrupted (but small image
  where selection is made looks valid).


  This issue may relate to video card  [radeon]

  ubuntu@ubuntu:~$ sudo lshw -C video
*-display:0   
 description: VGA compatible controller
 product: RV516 [Radeon X1300/X1550 Series]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e 
ioport:dc00(size=256) memory:c-d
*-display:1 UNCLAIMED
 description: Display controller
 product: RV516 [Radeon X1300/X1550 Series] (Secondary)
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0.1
 bus info: pci@:01:00.1
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress bus_master cap_list
 configuration: latency=0
 resources: memory:fe9f-fe9f

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.440
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.432
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:58:33 2019
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1870642] Re: Upgrade espeak-ng in Binoic Beaver to at least 1.49.2+dfsg-8 (from 1.49.2+dfsg-1)

2020-04-03 Thread Steven Presser
These directions document upgrading eSpeak NG on Ubuntu 18.04.  eSpeak
NG is the default voice for Orca.

On Ubuntu 18.04, the default version of eSpeak NG does not speak certain
types of punctuation (including the vertical bar (|), caret (^),
greater-than (>) and less-than (<)) when used in Orca's "say-all" or
speaking flat review lines or words, even with punctuation set to all.
This is not particularly critical for most uses, but these characters
are critical for programming and systems administration.

Upgrading eSpeak NG as follows will result in this punctuation being
read correctly when punctuation is set to all and a say-all or flat
review line or word command is issued.

COMMAND NOTATION

This document uses the dollar sign ($) as a prompt at the beginning of
each command.  This indicates that a command can be run as a non-
elevated/non-root user.  Do not type the dollar sign when typing the
command.

In many directions, the hash (#) is used to indicate that a command
should be run as root or using elevated privileges.  In these
directions, this notation is not used.  Instead commands are given with
sudo when elevated privileges are required.

INSTRUCTIONS

1. Check running version of eSpeak NG. The package name is the second
field on each line, while the version is the third field.

$ dpkg -l | grep espeak

The output should be:

ii  espeak-ng-data:amd64   1.49.2+dfsg-1
amd64Multi-lingual software speech synthesizer: speech data 
files
ii  libespeak-ng1:amd641.49.2+dfsg-1
amd64Multi-lingual software speech synthesizer: shared 
library
ii  speech-dispatcher-espeak-ng0.8.8-1ubuntu1   
amd64Speech Dispatcher: Espeak-ng output module

2. If this is less than 1.49.2+dsfg-8 (As of 2020-04-01, it is
1.49.2+dsfg-1 on Ubuntu 18.04), these directions are known to work.

3. Download the requisite packages:

$ wget 
http://mirrors.kernel.org/ubuntu/pool/main/e/espeak-ng/libespeak-ng1_1.49.2+dfsg-8_amd64.deb
$ wget 
http://mirrors.kernel.org/ubuntu/pool/main/e/espeak-ng/espeak-ng-data_1.49.2+dfsg-8_amd64.deb

4. Then install them:

$ sudo dpkg -i libespeak-ng1_1.49.2+dfsg-8_amd64.deb espeak-ng-
data_1.49.2+dfsg-8_amd64.deb

5. Check the installed eSpeak NG version:

$ dpkg -l | grep espeak

The output should be:

ii  espeak-ng-data:amd64   1.49.2+dfsg-8
amd64Multi-lingual software speech synthesizer: speech data 
files
ii  libespeak-ng1:amd641.49.2+dfsg-8
amd64Multi-lingual software speech synthesizer: shared 
library
ii  speech-dispatcher-espeak-ng0.8.8-1ubuntu1   
amd64Speech Dispatcher: Espeak-ng output module

6. Reboot the machine.  Turning Orca off and on several times may also
pick up the change, but this has not been entirely reliable in testing.

7. Test that the following characters are correctly read by issuing a
flat review speak line (Orca+i)

| ^ < >

8. Enjoy :)

These directions pull in an upgraded version of eSpeak NG from Ubuntu
19.04.  By doing so, we ensure that your system will continue to receive
upgrades to eSpeak NG as new software is added to Ubuntu 18.04, as long
as the new software is greater than the version we have just installed.

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

Title:
  Upgrade espeak-ng in Binoic Beaver to at least 1.49.2+dfsg-8 (from
  1.49.2+dfsg-1)

Status in espeak-ng package in Ubuntu:
  New

Bug description:
  Workaround directions follow this report in a comment.

  eSpeak NG prior to commit a766b22 (https://github.com/espeak-ng
  /espeak-ng/commit/a766b22643653402171ba8b482a9ed3f419f57bb) did not
  properly interpret certain characters (including the vertical bar (|),
  caret (^), greater than sign (>), and less than sign (<)) as
  punctuation.  Thus, when passing --punct (without arguments, for "read
  all punctuation") these characters were not read at all.

  This is particularly critical for users doing software development or
  systems administration using screen readers (such as the built-in
  Orca), where the addition or removal of one of these characters can
  significantly change the meaning of what is being read.

  eSpeak NG in Bionic Beaver (1.49.2+dfsg-1) does not include the fix
  for this issue.  However, eSpeak NG 1.49.2+dfsg-8 (as seen in Disco
  Dingo) includes the fix for this issue.  I have tested that upgrading
  to the Disco Dingo packages on a Bionic Beaver system corrects this
  issue.

  This minor version bump will significantly increase the accessibility
  of Bionic Beaver 18.04 LTS for users of Orca, other screen readers,
  and possibly other users and uses of eS

[Desktop-packages] [Bug 1870642] [NEW] Upgrade espeak-ng in Binoic Beaver to at least 1.49.2+dfsg-8 (from 1.49.2+dfsg-1)

2020-04-03 Thread Steven Presser
Public bug reported:

Workaround directions follow this report in a comment.

eSpeak NG prior to commit a766b22 (https://github.com/espeak-ng/espeak-
ng/commit/a766b22643653402171ba8b482a9ed3f419f57bb) did not properly
interpret certain characters (including the vertical bar (|), caret (^),
greater than sign (>), and less than sign (<)) as punctuation.  Thus,
when passing --punct (without arguments, for "read all punctuation")
these characters were not read at all.

This is particularly critical for users doing software development or
systems administration using screen readers (such as the built-in Orca),
where the addition or removal of one of these characters can
significantly change the meaning of what is being read.

eSpeak NG in Bionic Beaver (1.49.2+dfsg-1) does not include the fix for
this issue.  However, eSpeak NG 1.49.2+dfsg-8 (as seen in Disco Dingo)
includes the fix for this issue.  I have tested that upgrading to the
Disco Dingo packages on a Bionic Beaver system corrects this issue.

This minor version bump will significantly increase the accessibility of
Bionic Beaver 18.04 LTS for users of Orca, other screen readers, and
possibly other users and uses of eSpeak NG.

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

Package Info:
$ apt-cache policy libespeak-ng1
libespeak-ng1:
  Installed: 1.49.2+dfsg-1
  Candidate: 1.49.2+dfsg-1
  Version table:
 *** 1.49.2+dfsg-1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

Expected Behavior:

On Ubuntu 18.04 (Bionic Beaver), running:

$ espeak-ng --punct "< > | ^"

should produce the audio "less than greater than v bar circumflex".

Actual Behavior:

The system produces no sound.

** Affects: espeak-ng (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: a11y

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

Title:
  Upgrade espeak-ng in Binoic Beaver to at least 1.49.2+dfsg-8 (from
  1.49.2+dfsg-1)

Status in espeak-ng package in Ubuntu:
  New

Bug description:
  Workaround directions follow this report in a comment.

  eSpeak NG prior to commit a766b22 (https://github.com/espeak-ng
  /espeak-ng/commit/a766b22643653402171ba8b482a9ed3f419f57bb) did not
  properly interpret certain characters (including the vertical bar (|),
  caret (^), greater than sign (>), and less than sign (<)) as
  punctuation.  Thus, when passing --punct (without arguments, for "read
  all punctuation") these characters were not read at all.

  This is particularly critical for users doing software development or
  systems administration using screen readers (such as the built-in
  Orca), where the addition or removal of one of these characters can
  significantly change the meaning of what is being read.

  eSpeak NG in Bionic Beaver (1.49.2+dfsg-1) does not include the fix
  for this issue.  However, eSpeak NG 1.49.2+dfsg-8 (as seen in Disco
  Dingo) includes the fix for this issue.  I have tested that upgrading
  to the Disco Dingo packages on a Bionic Beaver system corrects this
  issue.

  This minor version bump will significantly increase the accessibility
  of Bionic Beaver 18.04 LTS for users of Orca, other screen readers,
  and possibly other users and uses of eSpeak NG.

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

  Package Info:
  $ apt-cache policy libespeak-ng1
  libespeak-ng1:
Installed: 1.49.2+dfsg-1
Candidate: 1.49.2+dfsg-1
Version table:
   *** 1.49.2+dfsg-1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Expected Behavior:

  On Ubuntu 18.04 (Bionic Beaver), running:

  $ espeak-ng --punct "< > | ^"

  should produce the audio "less than greater than v bar circumflex".

  Actual Behavior:

  The system produces no sound.

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

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


[Desktop-packages] [Bug 1870643] [NEW] Changing lightdm background image

2020-04-03 Thread Bill Pechter
Public bug reported:

Ubuntu 20.04 beta seems to not allow me to change the image which I have
changed in 18.04, 19.04, and 19.10.

Here's the file I want to use:
background = /usr/share/backgrounds/ubuntu-mate-common/mate-black.jpg
 cd /usr/share/backgrounds/ubuntu-mate-common/
root@S20:/usr/share/backgrounds/ubuntu-mate-common# ls -ltra

The file is there, world readable.
total 8464
-rw-r--r--  1 root root  688519 Oct 13  2018 mate-black.jpg

These are the config files... This machine was upgraded from 19.10 today.
I made the following changes in  the /etc/lightdm/*conf files in 18.x and they 
worked until now...
root@S20:/etc/lightdm# grep background *conf
lightdm.conf:background = 
/usr/share/backgrounds/ubuntu-mate-common/mate-black.jpg
lightdm-gtk-greeter.conf:background = 
/usr/share/backgrounds/ubuntu-mate-common/mate-black.jpg

** Affects: unity-greeter (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Changing lightdm background image

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 beta seems to not allow me to change the image which I
  have changed in 18.04, 19.04, and 19.10.

  Here's the file I want to use:
  background = /usr/share/backgrounds/ubuntu-mate-common/mate-black.jpg
   cd /usr/share/backgrounds/ubuntu-mate-common/
  root@S20:/usr/share/backgrounds/ubuntu-mate-common# ls -ltra

  The file is there, world readable.
  total 8464
  -rw-r--r--  1 root root  688519 Oct 13  2018 mate-black.jpg

  These are the config files... This machine was upgraded from 19.10 today.
  I made the following changes in  the /etc/lightdm/*conf files in 18.x and 
they worked until now...
  root@S20:/etc/lightdm# grep background *conf
  lightdm.conf:background = 
/usr/share/backgrounds/ubuntu-mate-common/mate-black.jpg
  lightdm-gtk-greeter.conf:background = 
/usr/share/backgrounds/ubuntu-mate-common/mate-black.jpg

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

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


[Desktop-packages] [Bug 1870550] Re: PCI/internal sound card not detected

2020-04-03 Thread Hui Wang
https://people.canonical.com/~hwang4/testdsp/ please test this kernel.
if it doesn't help. please upload a dmesg with that kernel.

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The sound card is not detected on my machine

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 00:51:33 2020
  InstallationDate: Installed on 2020-02-25 (37 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.46
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8UR41PA#ABG
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1870637] Re: 20.04beta: Cannot set 3840x2160

2020-04-03 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (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/1870637

Title:
  20.04beta: Cannot set 3840x2160

Status in xorg package in Ubuntu:
  New

Bug description:
  When i do get it to work, on reboot it'll be back to fullhd.
  this happens on nvidia 440, 435 and 390.

  On X.Org X server it does work.

  Graphics card: nVidia GT1030
  Amp: Onkyo TX-NR646

  On 19.10 there are no problems.
  A couple of weeks ago i tested a daily build and there were no troubles also, 
so this is new.

  My favourite setting: 3840x2160 200% 60hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:10:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:02:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1870638] Re: When taskbar is set to bottom icons cannot be re-arranged

2020-04-03 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (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/1870638

Title:
  When taskbar is set to bottom icons cannot be re-arranged

Status in xorg package in Ubuntu:
  New

Bug description:
  When taskbar is set to bottom icons cannot be re-arranged
  When taskbar is set to the left of the screen icons can be re-arranged

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:23:38 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1870638] [NEW] When taskbar is set to bottom icons cannot be re-arranged

2020-04-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When taskbar is set to bottom icons cannot be re-arranged
When taskbar is set to the left of the screen icons can be re-arranged

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 01:23:38 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476]
InstallationDate: Installed on 2020-04-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: Micro-Star International Co., Ltd. MS-7B84
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.D0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M PRO-M2 (MS-7B84)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B84
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu
-- 
When taskbar is set to bottom icons cannot be re-arranged
https://bugs.launchpad.net/bugs/1870638
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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


[Desktop-packages] [Bug 1870637] [NEW] 20.04beta: Cannot set 3840x2160

2020-04-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When i do get it to work, on reboot it'll be back to fullhd.
this happens on nvidia 440, 435 and 390.

On X.Org X server it does work.

Graphics card: nVidia GT1030
Amp: Onkyo TX-NR646

On 19.10 there are no problems.
A couple of weeks ago i tested a daily build and there were no troubles also, 
so this is new.

My favourite setting: 3840x2160 200% 60hz.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:10:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 01:02:09 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476]
InstallationDate: Installed on 2020-04-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: Micro-Star International Co., Ltd. MS-7B84
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.D0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M PRO-M2 (MS-7B84)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B84
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal resolution ubuntu
-- 
20.04beta: Cannot set 3840x2160   
https://bugs.launchpad.net/bugs/1870637
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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


[Desktop-packages] [Bug 1870640] [NEW] Does not register as x-www-browser alternative

2020-04-03 Thread Daniel Richard G.
Public bug reported:

This concern chromium 80.0.3987.162 (snap package) in Ubuntu focal.

After installing the package, update-alternatives(1) cannot set x-www-
browser to point to /usr/bin/chromium-browser:

# update-alternatives --set x-www-browser /usr/bin/chromium-browser
update-alternatives: error: alternative /usr/bin/chromium-browser for 
x-www-browser not registered; not setting

This worked correctly with the previous non-snap chromium-browser
package.

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

Title:
  Does not register as x-www-browser alternative

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  This concern chromium 80.0.3987.162 (snap package) in Ubuntu focal.

  After installing the package, update-alternatives(1) cannot set x-www-
  browser to point to /usr/bin/chromium-browser:

  # update-alternatives --set x-www-browser /usr/bin/chromium-browser
  update-alternatives: error: alternative /usr/bin/chromium-browser for 
x-www-browser not registered; not setting

  This worked correctly with the previous non-snap chromium-browser
  package.

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

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


[Desktop-packages] [Bug 1870609] Re: decimal point problem in ibus-libpinyin

2020-04-03 Thread Ping-Wu
Tried the PPA; works great!

(before)

3 除于 6 等于 0。5。(3 divided by 6 equals 0.5.)

(after)

3 除于 6 等于 0.5。(3 divided by 6 equals 0.5.)

!!!

Ubuntu 20.04 is looking very good. At least as far as Chinese input is
concerned.

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

Title:
  decimal point problem in ibus-libpinyin

Status in ibus-libpinyin package in Ubuntu:
  In Progress

Bug description:
  When in Chinese input mode, the "decimal point" is incorrectly shown
  as the Chinese punctuation "period". For example, 20.04 will be shown
  as 20。04。

  That is:

  (in English input mode) 3 divided by 6 is 0.5.
  (in Chinese input mode) 3 除于 6 等于 0。5。

  This problem has been solved in ibus-libpinyin 1.11.92:

  https://github.com/libpinyin/ibus-
  libpinyin/commit/1eb70ce12bed9d6b53c02ac8693ec52abe1d0216

  Please update the ibus-libpinyin version in Ubuntu 20.04.

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

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


[Desktop-packages] [Bug 1870609] Re: decimal point problem in ibus-libpinyin

2020-04-03 Thread Gunnar Hjalmarsson
@Boyuan: Yes, that is what I had in mind.

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

Title:
  decimal point problem in ibus-libpinyin

Status in ibus-libpinyin package in Ubuntu:
  In Progress

Bug description:
  When in Chinese input mode, the "decimal point" is incorrectly shown
  as the Chinese punctuation "period". For example, 20.04 will be shown
  as 20。04。

  That is:

  (in English input mode) 3 divided by 6 is 0.5.
  (in Chinese input mode) 3 除于 6 等于 0。5。

  This problem has been solved in ibus-libpinyin 1.11.92:

  https://github.com/libpinyin/ibus-
  libpinyin/commit/1eb70ce12bed9d6b53c02ac8693ec52abe1d0216

  Please update the ibus-libpinyin version in Ubuntu 20.04.

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

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


[Desktop-packages] [Bug 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

2020-04-03 Thread Gunnar Hjalmarsson
On 2020-04-03 21:52, Michael wrote:
> Was a mistake, miss-clicked and wouldn't let me revert. sorry!

N.p., thanks for explaining.

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1870627] Re: Cannot change symbols in charts in LibreOffice Calc 6.4

2020-04-03 Thread SeijiSensei
I don't know why it says the package is not installed.

$ ls /usr/bin/libreoffice -l
lrwxrwxrwx 1 root root 34 Apr  2 11:11 /usr/bin/libreoffice -> 
../lib/libreoffice/program/soffice

$ ls /usr/lib/libreoffice/program/soffice -l
-rwxr-xr-x 1 root root 6738 Mar 30 04:16 /usr/lib/libreoffice/program/soffice

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

Title:
  Cannot change symbols in charts in LibreOffice Calc 6.4

Status in libreoffice package in Ubuntu:
  New

Bug description:
  After the upgrade to LO 6.4 in Kubuntu 20.04, it is not possible to
  change the symbols used to identify points in charts created in Calc.
  I have filed a bug report with LO, but thought I would mention it here
  as well. The symbols used seem to be chosen at random. I've gotten
  boxes and triangles and cannot change them to my preferred symbol, the
  plus sign.

  I've used LO for years and have never encountered this problem before.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Apr  3 17:41:31 2020
  InstallationDate: Installed on 2020-04-02 (1 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1870627] [NEW] Cannot change symbols in charts in LibreOffice Calc 6.4

2020-04-03 Thread SeijiSensei
Public bug reported:

After the upgrade to LO 6.4 in Kubuntu 20.04, it is not possible to
change the symbols used to identify points in charts created in Calc. I
have filed a bug report with LO, but thought I would mention it here as
well. The symbols used seem to be chosen at random. I've gotten boxes
and triangles and cannot change them to my preferred symbol, the plus
sign.

I've used LO for years and have never encountered this problem before.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Apr  3 17:41:31 2020
InstallationDate: Installed on 2020-04-02 (1 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Cannot change symbols in charts in LibreOffice Calc 6.4

Status in libreoffice package in Ubuntu:
  New

Bug description:
  After the upgrade to LO 6.4 in Kubuntu 20.04, it is not possible to
  change the symbols used to identify points in charts created in Calc.
  I have filed a bug report with LO, but thought I would mention it here
  as well. The symbols used seem to be chosen at random. I've gotten
  boxes and triangles and cannot change them to my preferred symbol, the
  plus sign.

  I've used LO for years and have never encountered this problem before.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Apr  3 17:41:31 2020
  InstallationDate: Installed on 2020-04-02 (1 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1870628] [NEW] Authentication required window after startup

2020-04-03 Thread Igor Zubarev
Public bug reported:

After I setup auto logging without password in Gnome Control Center I
got Authentication required window every start of Ubuntu

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-keyring 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 00:41:50 2020
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Authentication required window after startup

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  After I setup auto logging without password in Gnome Control Center I
  got Authentication required window every start of Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-keyring 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 00:41:50 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1870609] Re: decimal point problem in ibus-libpinyin

2020-04-03 Thread Gunnar Hjalmarsson
Thanks for your investigation!

TBH I don't understand how to reproduce the problem. Anyway, I submitted
a merge request to Debian:

https://salsa.debian.org/debian/ibus-libpinyin/-/merge_requests/1

and made a test upload to this PPA:

https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin

Can you please install from the PPA and confirm that it fixes the issue?

** Changed in: ibus-libpinyin (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ibus-libpinyin (Ubuntu)
   Status: New => In Progress

** Changed in: ibus-libpinyin (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  decimal point problem in ibus-libpinyin

Status in ibus-libpinyin package in Ubuntu:
  In Progress

Bug description:
  When in Chinese input mode, the "decimal point" is incorrectly shown
  as the Chinese punctuation "period". For example, 20.04 will be shown
  as 20。04。

  That is:

  (in English input mode) 3 divided by 6 is 0.5.
  (in Chinese input mode) 3 除于 6 等于 0。5。

  This problem has been solved in ibus-libpinyin 1.11.92:

  https://github.com/libpinyin/ibus-
  libpinyin/commit/1eb70ce12bed9d6b53c02ac8693ec52abe1d0216

  Please update the ibus-libpinyin version in Ubuntu 20.04.

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

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


[Desktop-packages] [Bug 1870609] Re: decimal point problem in ibus-libpinyin

2020-04-03 Thread Boyuan Yang
@Gunnar: Do you think preparing a version with minimal changes in Debian
(applying the referenced commit as patch) works for Ubuntu?

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

Title:
  decimal point problem in ibus-libpinyin

Status in ibus-libpinyin package in Ubuntu:
  In Progress

Bug description:
  When in Chinese input mode, the "decimal point" is incorrectly shown
  as the Chinese punctuation "period". For example, 20.04 will be shown
  as 20。04。

  That is:

  (in English input mode) 3 divided by 6 is 0.5.
  (in Chinese input mode) 3 除于 6 等于 0。5。

  This problem has been solved in ibus-libpinyin 1.11.92:

  https://github.com/libpinyin/ibus-
  libpinyin/commit/1eb70ce12bed9d6b53c02ac8693ec52abe1d0216

  Please update the ibus-libpinyin version in Ubuntu 20.04.

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

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


[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-04-03 Thread Rick
20.04 beta still has this issue for me

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-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.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1870609] Re: decimal point problem in ibus-libpinyin

2020-04-03 Thread Sebastien Bacher
Thank you for your bug report, looks like a ibus-libpinyin bug though?
reassigning

** Package changed: gnome-settings-daemon (Ubuntu) => ibus-libpinyin
(Ubuntu)

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

Title:
  decimal point problem in ibus-libpinyin

Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  When in Chinese input mode, the "decimal point" is incorrectly shown
  as the Chinese punctuation "period". For example, 20.04 will be shown
  as 20。04。

  That is:

  (in English input mode) 3 divided by 6 is 0.5.
  (in Chinese input mode) 3 除于 6 等于 0。5。

  This problem has been solved in ibus-libpinyin 1.11.92:

  https://github.com/libpinyin/ibus-
  libpinyin/commit/1eb70ce12bed9d6b53c02ac8693ec52abe1d0216

  Please update the ibus-libpinyin version in Ubuntu 20.04.

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

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


[Desktop-packages] [Bug 1870620] Re: can't rotate screen by 90 or 270 degrees

2020-04-03 Thread Sebastien Bacher
** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => gnome-
shell (Ubuntu)

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

Title:
  can't rotate screen by 90 or 270 degrees

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2) gnome-control-center:
Installiert:   1:3.36.1-1ubuntu2
Installationskandidat: 1:3.36.1-1ubuntu2
Versionstabelle:
   *** 1:3.36.1-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) I change the rotation of my screen to 90/270 degrees (its the
  vertical second screen of my system) using the gnome-control-center

  4) the rotation changes are discarded and my two screen overlap as if
  the relative position of the screens was applied but not the rotation.

  a few weeks back this still worked in the focal channel.

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

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


[Desktop-packages] [Bug 1870617] Re: Merge fontconfig 2.13.1-3 (main) from Debian unstable (main)

2020-04-03 Thread Sebastien Bacher
** Changed in: fontconfig (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Merge fontconfig 2.13.1-3 (main) from Debian unstable (main)

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Please merge fontconfig 2.13.1-3 (main) from Debian unstable (main)

  Sorry, I can't work on this merge myself.
  It fixes Debian bugs, and they can be related to Ubuntu too.

  Explanation of the Ubuntu delta:
* Really include the symbols file update
* debian/patches/04_ubuntu_monospace_lcd_filter_conf.patch:
  - updated the 53-monospace-lcd-filter.conf syntax to avoid warnings
which make autopkgtests fail
* Upload proposed patch from upstream bug #103652. If the fontconfig cache
  was built on a system that has nanosecond timestamps and then later
  transplanted to one that doesn't - for example by mksquashfs as part of a
  live CD build - we consider the cache invalid and rebuild it during the
  boot process. Depending on the fonts involved, this can take a significant
  amount of time and potentially cause knock-on timeouts. The approach in
  this patch is to ignore the nanosecond portion of the cache's value if we
  get 0 when stat()ing the referenced directory, meaning it is considered
  fresh if the rest of the timestamp matches. (LP: #1749546)
* Merge with Debian (LP: #1638959, LP: #1702544). Remaining changes:
  - debian/source_fontconfig.py, debian/fontconfig.install:
+ Install apport hook
  - Add 03_prefer_dejavu.patch:
+ Prefer DejaVu to Bitstream Vera
  - Add 04_ubuntu_monospace_lcd_filter_conf.patch:
+ Use legacy lcdfilter with smaller monospace fonts
  - Add 05_ubuntu_add_antialiasing_confs.patch:
+ Add config file for antialiasing
  - Add 05_lcdfilterlegacy.patch: Recognize const value "lcdfilterlegacy",
used in Ubuntu before upstream introduced "lcdlegacy"
  - Add 07_no_bitmaps.patch:
+ Install 70-no-bitmaps.conf
  - Drop debian/fontconfig.NEWS, debian/fontconfig-config.templates,
debian/fontconfig-config.config, and associatedpo files.
Modify debian/rules, debian/fontconfig-config.postinst,
debian/fontconfig-config.postrm, and debian/README.Debian.
+ Don't provide debconf prompts
  - Modify debian/rules, debian/fontconfig-config.install,
debian/fontconfig-config.links, debian/fontconfig-config.postrm,
and debian/fontconfig-udeb.install:
+ Delay doing the transition from /etc to /usr
* New upstream release
* Refresh patches
* Update Ubuntu patches to use mode="append" and target="pattern"
  (LP: #1192175)
* Drop patches applied in new release:
  - 01_fonts_nanum.patch
  - 03_locale_c.utf8.patch
  - 06_cross.patch
  - CVE-2016-5384.patch

  Changelog entries since current focal version 2.13.1-2ubuntu2:

  fontconfig (2.13.1-3) unstable; urgency=medium

[ Laurent Bigonville ]
* debian/rules: Stop looking for fonts in /usr/X11R6/lib/X11/fonts, nothing
  is installing fonts there for years and it's causing gnome-settings-daemon
  to check the location every few seconds (Closes: #568686)

[ Fabian Greffrath ]
* fontconfig-config: extend, clean-up and order fontconfig-config's
  font dependencies (Closes: #879503)

[ Emilio Pozuelo Monfort ]
* Split documentation into a -doc package to avoid multi-arch problems in
  the -dev one (Closes: #935760, #844607)
* Since we're going through NEW, rename libfontconfig1-dev to
  libfontconfig-dev and provide the former.
* Switch to debhelper-compat.

   -- Emilio Pozuelo Monfort   Wed, 18 Mar 2020
  00:56:46 +0100

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

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


[Desktop-packages] [Bug 1870624] [NEW] fails to install after password prompt

2020-04-03 Thread Guilherme Campos
Public bug reported:

1) Description: Ubuntu Focal Fossa (development branch)
Release:20.04

2) gnome-software:
  Installed: 3.35.91-0ubuntu1
  Candidate: 3.35.91-0ubuntu1
  Version table:
 *** 3.35.91-0ubuntu1 500
500 http://pt.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

3) Opera installation

4) Blank error


Screenshot: https://imgur.com/TWGk02s.png

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

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

Title:
  fails to install after password prompt

Status in gnome-software package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2) gnome-software:
Installed: 3.35.91-0ubuntu1
Candidate: 3.35.91-0ubuntu1
Version table:
   *** 3.35.91-0ubuntu1 500
  500 http://pt.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Opera installation

  4) Blank error

  
  Screenshot: https://imgur.com/TWGk02s.png

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

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


[Desktop-packages] [Bug 1870622] [NEW] package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/lib/libreoffice/share/basic/Access2Base/Application.xba', which

2020-04-03 Thread Vinny
Public bug reported:

Happened on boot

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libreoffice-common 1:6.4.2-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
Date: Sat Mar 28 06:45:40 2020
ErrorMessage: trying to overwrite 
'/usr/lib/libreoffice/share/basic/Access2Base/Application.xba', which is also 
in package libreoffice-base 1:6.3.5-0ubuntu0.19.10.1
InstallationDate: Installed on 2019-07-21 (257 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  2.0.1
SourcePackage: libreoffice
Title: package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade: 
trying to overwrite 
'/usr/lib/libreoffice/share/basic/Access2Base/Application.xba', which is also 
in package libreoffice-base 1:6.3.5-0ubuntu0.19.10.1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade:
  trying to overwrite
  '/usr/lib/libreoffice/share/basic/Access2Base/Application.xba', which
  is also in package libreoffice-base 1:6.3.5-0ubuntu0.19.10.1

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Happened on boot

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-common 1:6.4.2-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  Date: Sat Mar 28 06:45:40 2020
  ErrorMessage: trying to overwrite 
'/usr/lib/libreoffice/share/basic/Access2Base/Application.xba', which is also 
in package libreoffice-base 1:6.3.5-0ubuntu0.19.10.1
  InstallationDate: Installed on 2019-07-21 (257 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  2.0.1
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade: 
trying to overwrite 
'/usr/lib/libreoffice/share/basic/Access2Base/Application.xba', which is also 
in package libreoffice-base 1:6.3.5-0ubuntu0.19.10.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1870575] Re: App's name are truncated in full screen grid view

2020-04-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  App's name are truncated in full screen grid view

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Ubuntu 20.04, default.

  In the global app-menu ( full screen grid view ) app'names are
  truncated, only displayed on one line.

  There is enough room to display them on two or three lines under each
  icon.

  Maybe it's not a big readability concern in English but it is in
  French and I guess in German and other languages as many app's start
  with same first words, i.e. Gestionnaire de… / Éditeur de… / Libre
  Office…

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

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


[Desktop-packages] [Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series

2020-04-03 Thread Kelsey Margarete Skunberg
** Changed in: linux-restricted-modules (Ubuntu Eoan)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Eoan)
   Status: New => Fix Committed

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

Title:
  Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility
  to the 340 and 390 series

Status in linux package in Ubuntu:
  Triaged
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-restricted-modules source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Eoan:
  Fix Committed
Status in nvidia-settings source package in Eoan:
  Fix Committed

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

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

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

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

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

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

  [Discussion]

  440.40:
    * New upstream release:
  - Added support for the following GPU:
  Quadro T2000 with Max-Q Design
  - Added support for the __GL_SYNC_DISPLAY_DEVICE environment
    variable for Vulkan applications.
  - Fixed a bug that caused applications running directly on a
    display (such as VR HMDs) to tear when a G-SYNC or G-SYNC
    Compatible monitor is plugged in the system.
  - Fixed a bug in an error handling path that could cause a kernel
    crash while loading nvidia.ko.
  - Fixed driver installation failure on Oracle Linux 7.7 systems,
    where the NVIDIA kernel module failed to build with error
    "unknown type name 'vm_fault_t'".
    * Changes from the 440.36 series:
  - Added support for the following GPUs:
    o GeForce GTX 1650 SUPER
    o GeForce GTX 1660 SUPER
  - Fixed graphical corruption that can occur when using glslang
    SPIR-V Generator Version <= 2.
  - Fixed a bug that could cause the X server to crash when running
    applications using GLX indirect rendering.
  - Updated the Module.symvers sanity check, which is part of the
    NVIDIA kernel module build process, to accommodate the recent
    addition of a new field in the Module.symvers file format.
    This fixes the error "The Module.symvers file is missing [...]"
    seen during driver installation or DKMS rebuilds with Linux 5.4 RC
    kernels.
  - Fixed kernel module build problems with Linux kernel 5.4.0 release
    candidates.
  - Updated nvidia-bug-report.sh to collect information about X server
    crashes from coredumpctl, when available.
  - Updated the nvidia-drm kernel module for compatibility with the
    removal of the DRIVER_PRIME flag in recent Linux kernel versions.
  - Enabled parallel GLSL shader linking by default; i.e., allow
    GL_ARB_parallel_shader_compile to work without first calling
    glMaxShaderCompilerThreadsARB().
  - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC
    Compatible monitors on supported GPUs.For more details, see
    "Configuring Multiple Display Devices on One X Screen" in the README.
    Added support for the GLX_NV_multigpu_context and GL_NV_gpu_multicast
    extensions.For more details, see the "Configuring SLI and Multi-GPU
  

[Desktop-packages] [Bug 1870620] [NEW] can't rotate screen by 90 or 270 degrees

2020-04-03 Thread Andreas Gibhardt
Public bug reported:

1) Description: Ubuntu Focal Fossa (development branch)
Release:20.04

2) gnome-control-center:
  Installiert:   1:3.36.1-1ubuntu2
  Installationskandidat: 1:3.36.1-1ubuntu2
  Versionstabelle:
 *** 1:3.36.1-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

3) I change the rotation of my screen to 90/270 degrees (its the
vertical second screen of my system) using the gnome-control-center

4) the rotation changes are discarded and my two screen overlap as if
the relative position of the screens was applied but not the rotation.

a few weeks back this still worked in the focal channel.

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

** Attachment added: "Bildschirmfoto von 2020-04-03 22-51-28.png"
   
https://bugs.launchpad.net/bugs/1870620/+attachment/5345849/+files/Bildschirmfoto%20von%202020-04-03%2022-51-28.png

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

Title:
  can't rotate screen by 90 or 270 degrees

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

Bug description:
  1) Description:   Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2) gnome-control-center:
Installiert:   1:3.36.1-1ubuntu2
Installationskandidat: 1:3.36.1-1ubuntu2
Versionstabelle:
   *** 1:3.36.1-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) I change the rotation of my screen to 90/270 degrees (its the
  vertical second screen of my system) using the gnome-control-center

  4) the rotation changes are discarded and my two screen overlap as if
  the relative position of the screens was applied but not the rotation.

  a few weeks back this still worked in the focal channel.

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

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


[Desktop-packages] [Bug 1870617] [NEW] Merge fontconfig 2.13.1-3 (main) from Debian unstable (main)

2020-04-03 Thread Amr Ibrahim
Public bug reported:

Please merge fontconfig 2.13.1-3 (main) from Debian unstable (main)

Sorry, I can't work on this merge myself.
It fixes Debian bugs, and they can be related to Ubuntu too.

Explanation of the Ubuntu delta:
  * Really include the symbols file update
  * debian/patches/04_ubuntu_monospace_lcd_filter_conf.patch:
- updated the 53-monospace-lcd-filter.conf syntax to avoid warnings
  which make autopkgtests fail
  * Upload proposed patch from upstream bug #103652. If the fontconfig cache
was built on a system that has nanosecond timestamps and then later
transplanted to one that doesn't - for example by mksquashfs as part of a
live CD build - we consider the cache invalid and rebuild it during the
boot process. Depending on the fonts involved, this can take a significant
amount of time and potentially cause knock-on timeouts. The approach in
this patch is to ignore the nanosecond portion of the cache's value if we
get 0 when stat()ing the referenced directory, meaning it is considered
fresh if the rest of the timestamp matches. (LP: #1749546)
  * Merge with Debian (LP: #1638959, LP: #1702544). Remaining changes:
- debian/source_fontconfig.py, debian/fontconfig.install:
  + Install apport hook
- Add 03_prefer_dejavu.patch:
  + Prefer DejaVu to Bitstream Vera
- Add 04_ubuntu_monospace_lcd_filter_conf.patch:
  + Use legacy lcdfilter with smaller monospace fonts
- Add 05_ubuntu_add_antialiasing_confs.patch:
  + Add config file for antialiasing
- Add 05_lcdfilterlegacy.patch: Recognize const value "lcdfilterlegacy",
  used in Ubuntu before upstream introduced "lcdlegacy"
- Add 07_no_bitmaps.patch:
  + Install 70-no-bitmaps.conf
- Drop debian/fontconfig.NEWS, debian/fontconfig-config.templates,
  debian/fontconfig-config.config, and associatedpo files.
  Modify debian/rules, debian/fontconfig-config.postinst,
  debian/fontconfig-config.postrm, and debian/README.Debian.
  + Don't provide debconf prompts
- Modify debian/rules, debian/fontconfig-config.install,
  debian/fontconfig-config.links, debian/fontconfig-config.postrm,
  and debian/fontconfig-udeb.install:
  + Delay doing the transition from /etc to /usr
  * New upstream release
  * Refresh patches
  * Update Ubuntu patches to use mode="append" and target="pattern"
(LP: #1192175)
  * Drop patches applied in new release:
- 01_fonts_nanum.patch
- 03_locale_c.utf8.patch
- 06_cross.patch
- CVE-2016-5384.patch

Changelog entries since current focal version 2.13.1-2ubuntu2:

fontconfig (2.13.1-3) unstable; urgency=medium

  [ Laurent Bigonville ]
  * debian/rules: Stop looking for fonts in /usr/X11R6/lib/X11/fonts, nothing
is installing fonts there for years and it's causing gnome-settings-daemon
to check the location every few seconds (Closes: #568686)

  [ Fabian Greffrath ]
  * fontconfig-config: extend, clean-up and order fontconfig-config's
font dependencies (Closes: #879503)

  [ Emilio Pozuelo Monfort ]
  * Split documentation into a -doc package to avoid multi-arch problems in
the -dev one (Closes: #935760, #844607)
  * Since we're going through NEW, rename libfontconfig1-dev to
libfontconfig-dev and provide the former.
  * Switch to debhelper-compat.

 -- Emilio Pozuelo Monfort   Wed, 18 Mar 2020 00:56:46
+0100

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

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

Title:
  Merge fontconfig 2.13.1-3 (main) from Debian unstable (main)

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Please merge fontconfig 2.13.1-3 (main) from Debian unstable (main)

  Sorry, I can't work on this merge myself.
  It fixes Debian bugs, and they can be related to Ubuntu too.

  Explanation of the Ubuntu delta:
* Really include the symbols file update
* debian/patches/04_ubuntu_monospace_lcd_filter_conf.patch:
  - updated the 53-monospace-lcd-filter.conf syntax to avoid warnings
which make autopkgtests fail
* Upload proposed patch from upstream bug #103652. If the fontconfig cache
  was built on a system that has nanosecond timestamps and then later
  transplanted to one that doesn't - for example by mksquashfs as part of a
  live CD build - we consider the cache invalid and rebuild it during the
  boot process. Depending on the fonts involved, this can take a significant
  amount of time and potentially cause knock-on timeouts. The approach in
  this patch is to ignore the nanosecond portion of the cache's value if we
  get 0 when stat()ing the referenced directory, meaning it is considered
  fresh if the rest of the timestamp matches. (LP: #1749546)
* Merge with Debian (LP: #1638959, LP: #1702544). Remaining changes:
  - d

[Desktop-packages] [Bug 1806242] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C

2020-04-03 Thread Carcalac
i have the same issue on ubuntu 19.10

Apr  3 22:43:21 HP-15-cs3xxx kernel: [ 8867.271966]
[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe
A (start=532823 end=532824) time 143 us, min 1073, max 1079, scanline
start 1072, end 1081

cat /etc/modprobe.d/i915.conf

options i915 enable_psr=0
options i915 enable_guc=2

5.3.0-45-generic

followed by one of the eight cores going crazy ~100% usage and i have to
reboot because the system becomes slow..

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

Title:
  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe A/B/C

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have this error and arbitrary freezes on the system

  My System:

  Hardware:
  Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 
0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate 
ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: 
Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 
Gigabit + Intel Device a370

  Software:
  OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, 
Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, 
Screen Resolution: 1920x1980

  dmesg output:

  Dec  2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, 
min 894, max 899, scanline start 845, end 903
  Dec  2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup 
failure, AE_NOT_FOUND (20170831/psargs-364)
  Dec  2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized 
for Method [BRT6]
  Dec  2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method 
[BRT6]:  (2 arguments defined for method invocation)
  Dec  2 16:08:50 G5 kernel: [ 2534.448073]   Arg0:   a83faa08 
   Integer 0001
  Dec  2 16:08:50 G5 kernel: [ 2534.448076]   Arg1:   35246c42 
   Integer 
  Dec  2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution 
failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution 
failed \EV5, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution 
failed \SMEE, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution 
failed \SMIE, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution 
failed \NEVT, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution 
failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event 
[0x86]
  Dec  2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event 
[0x86]
  Dec  2 16:20:32 G5 kernel: [ 3237.026638] [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe B (start=88190 end=88191) time 1687 us, 
min 894, max 899, scanline start 864, end 14
  Dec  2 16:22:20 G5 kernel: [ 3344.842212] wlp0s20f3: AP 90:ef:68:2c:31:9b 
changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  instantcrush   1622 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-28 (4 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. G5 5587
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=0017db25-edad-4311-bca6-171f2624432e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/01/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 0M2MWX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd11/01/2018:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn0M2MWX:rv

[Desktop-packages] [Bug 1813423] Re: System freezing or flickering with i915 error [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A

2020-04-03 Thread Carcalac
*** This bug is a duplicate of bug 1806242 ***
https://bugs.launchpad.net/bugs/1806242

i have the same issue on ubuntu 19.10

cat /etc/modprobe.d/i915.conf

options i915 enable_psr=0
options i915 enable_guc=2


5.3.0-45-generic

followed by one of the eight cores going crazy ~100% usage and i have to
reboot because the system becomes slow..

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

Title:
  System freezing or flickering with i915 error
  [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
  pipe A

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  My system keeps freezing on a brand new install of Kubuntu 18.10,
  always with the kern.log error "[drm:intel_pipe_update_end [i915]]
  *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235)
  time 486 us, min 763, max 767, scanline start 760, end 783"

  I think it's probably a duplicate of these bugs which were closed unresolved:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was 
on an older version of Ubuntu)
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because 
it was a duplicate of the first bug)

  It happens far more frequently if I have desktop effects turned on,
  and far less frequently when using a live USB key (at always happens
  eventually though. Usually once every few hours.)

  Please advise how I can help triage / test. My system is a new install
  now, so I'm perfectly willing to modify / reinstall to help testing
  (I've reinstalled 5 times to test things, but never managed to find a
  solution)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Jan 26 14:19:52 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:227a]
  InstallationDate: Installed on 2019-01-18 (8 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager 
modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia 
intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 
i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 
i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 76.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.sku: J9L01UA#ABL
  dmi.product.version: 096C110800405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


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

2020-04-03 Thread Seija Kijin
apport information

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

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL  

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

2020-04-03 Thread Seija Kijin
apport information

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

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  A

[Desktop-packages] [Bug 1870442] RfKill.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1870442/+attachment/5345847/+files/RfKill.txt

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNEC

[Desktop-packages] [Bug 1870442] PciNetwork.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1870442/+attachment/5345845/+files/PciNetwork.txt

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  A

[Desktop-packages] [Bug 1870442] NetworkManager.conf.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1870442/+attachment/5345844/+files/NetworkManager.conf.txt

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL

[Desktop-packages] [Bug 1870442] NetDevice.wlp2s0.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "NetDevice.wlp2s0.txt"
   
https://bugs.launchpad.net/bugs/1870442/+attachment/5345843/+files/NetDevice.wlp2s0.txt

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAU

[Desktop-packages] [Bug 1870442] IpAddr.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1870442/+attachment/5345839/+files/IpAddr.txt

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNEC

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

2020-04-03 Thread Seija Kijin
apport information

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

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PR

[Desktop-packages] [Bug 1870442] NetDevice.lo.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1870442/+attachment/5345842/+files/NetDevice.lo.txt

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNEC

[Desktop-packages] [Bug 1870442] NetDevice.enp1s0.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "NetDevice.enp1s0.txt"
   
https://bugs.launchpad.net/bugs/1870442/+attachment/5345841/+files/NetDevice.enp1s0.txt

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAU

[Desktop-packages] [Bug 1870442] IwConfig.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1870442/+attachment/5345840/+files/IwConfig.txt

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOC

[Desktop-packages] [Bug 1870442] Dependencies.txt

2020-04-03 Thread Seija Kijin
apport information

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

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNEC

[Desktop-packages] [Bug 1870442] Re: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.

2020-04-03 Thread Seija Kijin
** Attachment added: "journalctl.log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870442/+attachment/5345816/+files/journalctl.log

** Tags added: apport-collected

** Description changed:

  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on my
  PC for a brief second before disabling airplane mode and reenabling Wi-
  Fi.
  
  Ubuntu 18.04.4
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.9
+ Architecture: amd64
+ CasperVersion: 1.394.3
+ DistroRelease: Ubuntu 18.04
+ IfupdownConfig:
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
+ IpRoute:
+  default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
+  169.254.0.0/16 dev wlp2s0 scope link metric 1000 
+  192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
+ LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
+ NetworkManager.state:
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
+ Package: network-manager 1.10.6-2ubuntu1.2
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
+ Tags:  bionic
+ Uname: Linux 5.3.0-28-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ nmcli-con:
+  NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
+  NETGEAR18   39a9b5bc-fd79-40c0-bf5d-7a1eb39843a7  wifi  
1585944468  Fri Apr  3 20:07:48 2020  yes  0

[Desktop-packages] [Bug 1870615] [NEW] Wi-Fi fails to connect to my network even when I enter the correct password, until I turn on Airplane Mode and then turn it off.

2020-04-03 Thread Seija Kijin
Public bug reported:

This happens often, but not always, when I boot Ubuntu on my Dell
Inspiron 5570.

Ubuntu 18.04.4

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1.2
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CasperVersion: 1.394.3
Date: Fri Apr  3 20:05:04 2020
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE  TIMESTAMP  
 TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
 NETGEAR18   39a9b5bc-fd79-40c0-bf5d-7a1eb39843a7  wifi  1585944263 
 Fri Apr  3 20:04:23 2020  yes  0 no
/org/freedesktop/NetworkManager/Settings/2  yes wlp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/3  --
 Wired connection 1  abfe1401-bc06-3a2f-b8ad-f79ba4b50d75  ethernet  1585944168 
 Fri Apr  3 20:02:48 2020  yes  4294966297no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
   --
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   39a9b5bc-fd79-40c0-bf5d-7a1eb39843a7  
/org/freedesktop/NetworkManager/ActiveConnection/3 
 enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug bionic

** Attachment added: "journalctl.log"
   
https://bugs.launchpad.net/bugs/1870615/+attachment/5345803/+files/journalctl.log

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

Title:
  Wi-Fi fails to connect to my network even when I enter the correct
  password, until I turn on Airplane Mode and then turn it off.

Status in network-manager package in Ubuntu:
  New

Bug description:
  This happens often, but not always, when I boot Ubuntu on my Dell
  Inspiron 5570.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.2
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  Date: Fri Apr  3 20:05:04 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   39a9b5bc-fd79-40c0-bf5d-7a1eb39843a7  wifi  
1585944263  Fri Apr  3 20:04:23 2020  yes  0 

[Desktop-packages] [Bug 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

2020-04-03 Thread Michael
Was a mistake, miss-clicked and wouldn't let me revert. sorry!

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

2020-04-03 Thread Gunnar Hjalmarsson
@Michael: Why did you close the bug with "Fix Released" without
justification?

** Changed in: ibus (Ubuntu)
   Status: Fix Released => Incomplete

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1867613] Re: Ubuntu dock does not allow drag and move icons anymore

2020-04-03 Thread daftykins
I can reproduce this behaviour, I am unable to drag the icons
consistently when the dock is placed on the bottom of the screen. I've
recorded a quick video which is available here:

https://youtu.be/kWT5vgvoW0I

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

Title:
  Ubuntu dock does not allow drag and move icons anymore

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

Bug description:
  Ubuntu 20.04 daily development branch @ 16/3/2020

  After a clean install daily at 14/3/2020 the ubuntu dock does not allow
  drag and move icons anymore
  you can still mouseclick and hold the icon, but it does not make space
  between other icons to release

  starting an application still showing the icon, and add to favorites
  still works

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 16 12:31:30 2020
  InstallationDate: Installed on 2020-03-14 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1870560] Re: Client does not renew IP after RADIUS COA disconnect

2020-04-03 Thread asylum
Thanks Brian!

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

Title:
  Client does not renew IP after RADIUS COA disconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have been testing RADIUS change of authorization on Ubiquiti
  wireless.  I have tested this on Ubuntu 19.04 as well as Ubuntu 19.10
  and the behavior is the same on both as well as when testing on Debian
  or Fedora.  FWIW this is working with a Windows 10 or Android client
  connected to the same wireless SSID on the same wireless AP, so this
  does not seem to be a configuration issue on the AP from what I can
  see.  Below are the logs from the Ubuntu client as well as the RADIUS
  server.  Please let me know if any further info is needed or if this
  behavior is expected.  Log info is below.  Thanks!

  
  ubuntu@ubuntu:/var/log$ journalctl | grep -Ei 'dhcp'
  Mar 26 21:28:30 ubuntu NetworkManager[1127]:   [1585258110.5810] 
dhcp-init: Using DHCP client 'dhclient'

  Client sends an Access-Request to RADIUS server:

  Thu Mar 26 17:29:13 2020
  Packet-Type = Access-Request
  User-Name = "dshields"
  NAS-Identifier = "7483c28d26de"
  Called-Station-Id = "74-83-C2-8D-26-DE:DF-Ubiquiti-Test"
  NAS-Port-Type = Wireless-802.11
  Service-Type = Framed-User
  Calling-Station-Id = "38-59-F9-81-5C-98"
  Connect-Info = "CONNECT 0Mbps 802.11b"
  Acct-Session-Id = "ABB4DA79B50051CB"
  WLAN-Pairwise-Cipher = 1027076
  WLAN-Group-Cipher = 1027076
  WLAN-AKM-Suite = 1027073
  Framed-MTU = 1400
  EAP-Message = 0x022900061500
  State = 0x4cc366d24aea73b029eb30b6d6318ffc
  Message-Authenticator = 0x48aef4abde67bc109ce1689d34b292cb
  NAS-IP-Address = 10.100.10.235

  Thu Mar 26 17:29:13 2020
  Packet-Type = Access-Request
  User-Name = "dshields"
  NAS-Identifier = "7483c28d26de"
  Called-Station-Id = "74-83-C2-8D-26-DE:DF-Ubiquiti-Test"
  NAS-Port-Type = Wireless-802.11
  Service-Type = Framed-User
  Calling-Station-Id = "38-59-F9-81-5C-98"
  Connect-Info = "CONNECT 0Mbps 802.11b"
  Acct-Session-Id = "ABB4DA79B50051CB"
  WLAN-Pairwise-Cipher = 1027076
  WLAN-Group-Cipher = 1027076
  WLAN-AKM-Suite = 1027073
  Framed-MTU = 1400
  EAP-Message = 
0x022a00841500160303004610424104bbae17c4fd4f2c594c2fe9737cc7919914adc728c0c3080fcf9e0f4cec1e1baced618159446d056286c8ca54ab8eb9142a2b1cfd5c88e110e6a28edf4ce943ed1403030001011603030028c00e45cebb1752d0b5c6323f47be852483a27af729b82ee96e3139d24dfa485e8ffed35de2438d54
  State = 0x4cc366d24be973b029eb30b6d6318ffc
  Message-Authenticator = 0x5d0f1396a39e5b0e1e1a0c6118e1ebea
  NAS-IP-Address = 10.100.10.235

  Authentication succeeds and VLAN 230 is returned to client with Access-Accept:

  Thu Mar 26 17:29:13 2020 : Auth: Login OK: [dshields] (from client 
OPSWAT-AP-AC-PRO port 0 via TLS tunnel)
  Thu Mar 26 17:29:13 2020 : Auth: Login OK: [dshields] (from client 
OPSWAT-AP-AC-PRO port 0 cli 38-59-F9-81-5C-98)

  Thu Mar 26 17:29:13 2020
  Packet-Type = Access-Accept
  User-Name = "dshields"
  MS-MPPE-Recv-Key = 
0x0e4b4cd48f891763a1f1792c71047066b1fd70914f7212cf011f1a367277cd02
  MS-MPPE-Send-Key = 
0xc81a04f1482a75cff7cac78876a95391ab9908d613dd2e2476def943bab5cf4c
  EAP-MSK = 
0x0e4b4cd48f891763a1f1792c71047066b1fd70914f7212cf011f1a367277cd02c81a04f1482a75cff7cac78876a95391ab9908d613dd2e2476def943bab5cf4c
  EAP-EMSK = 
0x55d0a72ab01bd0a5ec49a6e081fcecff37357ba89f8c25767d8033e529e45b116a9cec3044cef37c20297c60b8b3b345be1248859214586ad9e925545cf88c14
  EAP-Session-Id = 
0x15066089550d45a92a0c53f9280e765fbdcf813480da08fdbf5b33de44dd5dc9c15e7d1ea91e31c2135dd3b384f8d628548ab4beb299a79ee60836464d78cfcce5
  EAP-Message = 0x032b0004
  Message-Authenticator = 0x
  Calling-Station-Id = "38-59-F9-81-5C-98"
  Tunnel-Type:0 += VLAN
  Tunnel-Medium-Type:0 += IEEE-802
  Tunnel-Private-Group-Id:0 += "230"

  Laptop sends a DHCP request and gets an IP in VLAN 230:

  Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.1150] dhcp4 
(wlp2s0b1): activation: beginning transaction (timeout in 45 seconds)
  Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.1352] dhcp4 
(wlp2s0b1): dhclient started with pid 2626
  Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPDISCOVER on wlp2s0b1 to 
255.255.255.255 port 67 interval 3 (xid=0x6bec8061)
  Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPOFFER of 10.103.230.59 from 
10.103.230.1
  Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPREQUEST for 10.103.230.59 on 
wlp2s0b1 to 255.255.255.255 port 67 (xid=0x6180

[Desktop-packages] [Bug 1870609] [NEW] decimal point problem in ibus-libpinyin

2020-04-03 Thread Ping-Wu
Public bug reported:

When in Chinese input mode, the "decimal point" is incorrectly shown as
the Chinese punctuation "period". For example, 20.04 will be shown as
20。04。

That is:

(in English input mode) 3 divided by 6 is 0.5.
(in Chinese input mode) 3 除于 6 等于 0。5。

This problem has been solved in ibus-libpinyin 1.11.92:

https://github.com/libpinyin/ibus-
libpinyin/commit/1eb70ce12bed9d6b53c02ac8693ec52abe1d0216

Please update the ibus-libpinyin version in Ubuntu 20.04.

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

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

Title:
  decimal point problem in ibus-libpinyin

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

Bug description:
  When in Chinese input mode, the "decimal point" is incorrectly shown
  as the Chinese punctuation "period". For example, 20.04 will be shown
  as 20。04。

  That is:

  (in English input mode) 3 divided by 6 is 0.5.
  (in Chinese input mode) 3 除于 6 等于 0。5。

  This problem has been solved in ibus-libpinyin 1.11.92:

  https://github.com/libpinyin/ibus-
  libpinyin/commit/1eb70ce12bed9d6b53c02ac8693ec52abe1d0216

  Please update the ibus-libpinyin version in Ubuntu 20.04.

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

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


[Desktop-packages] [Bug 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

2020-04-03 Thread Michael
Had this happen to me as well. Ill try and reproduce but not sure that
will happen. For me i logged out of a session then logged back in and
clicked on "software update" and got the error.

** Changed in: ibus (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1831140] Re: GNOME Magnifier Flickering when using none-full screen modes

2020-04-03 Thread Lee Clark
This bug appears to have been fixed at some point in the development of
gnome 3.6, still present in 3.4 on Ubutnu 19.10 and 18.04.

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

Title:
  GNOME Magnifier Flickering when using none-full screen  modes

Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When using the GNOME magnifier (Zoom) feature the magnified display
  flickers when used in any of the following none full screen modes:
  Left, Right, Top or Bottom screen part. This occurs when the mouse
  moves towards the edge directly opposite to the magnified view. This
  also occurs if 'Magnifier extends outside of screen' is enabled.

  To reproduce:
  * Open GNOME Control Centre.
  * Go to Universal Access.
  * Click on Zoom.
  * Enable Zoom
  * Selct either Top, Bottom, Left or Right from the screen part drop down list.
  * Move the mouse cursor to the opossite edge of the screen to that where the 
magnified view is located.

  I have tested on multiple systems running Ubuntu 18.04, 18.10, 19.04
  and Fedora 30.

  Tested with all extension uninstalled.

  Happy to provide additional details.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 30 19:14:43 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-03-12 (78 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1870600] [NEW] permissions pane only shows currently-connected snap interfaces

2020-04-03 Thread Daniel Llewellyn
Public bug reported:

The applications applet in Gnome Control Center shows permissions that
can be toggled on and off for installed applications and snap packages.
When viewing a Snap package, only permissions that are currently enabled
(interface is connected in Snap terms). Viewing the same Snap package's
permissions in Gnome Software or the Snap Store Snap you can see that
there are more permissions that can be enabled which are not currently.

I have uploaded an example of both views to highlight the discrepency in
a screenshot at:
https://www.dropbox.com/s/zqr35hll94d37yg/photo_2020-04-03_19-49-06.jpg?dl=0

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  3 19:48:07 2020
InstallationDate: Installed on 2020-03-03 (30 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug champagne focal

** Tags added: champagne

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

Title:
  permissions pane only shows currently-connected snap interfaces

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  The applications applet in Gnome Control Center shows permissions that
  can be toggled on and off for installed applications and snap
  packages. When viewing a Snap package, only permissions that are
  currently enabled (interface is connected in Snap terms). Viewing the
  same Snap package's permissions in Gnome Software or the Snap Store
  Snap you can see that there are more permissions that can be enabled
  which are not currently.

  I have uploaded an example of both views to highlight the discrepency
  in a screenshot at:
  https://www.dropbox.com/s/zqr35hll94d37yg/photo_2020-04-03_19-49-06.jpg?dl=0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 19:48:07 2020
  InstallationDate: Installed on 2020-03-03 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1870442] Re: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.

2020-04-03 Thread Seija Kijin
It was a one-only time issue (for now), and yes, let me add the
jounralctl log.

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Desktop-packages] [Bug 1870597] [NEW] Gnome slows down and stutters when I move the mouse while the installer is installing ubuntu 20.04

2020-04-03 Thread Seija Kijin
Public bug reported:

During the freeze, the output of the install had a message from
"gdm-x-session" saying "your system is too slow".

To reproduce:
1. Launch the Ubuntu installer
2. Begin the installation process
3. When the installation process begins, move the cursor around
4. Notice how the PC freezes and drops mouse events

Description:Ubuntu Focal Fossa (development branch)
Release:20.04

gnome-shell:
  Installed: 3.36.0-2ubuntu2
  Candidate: 3.36.0-2ubuntu2
  Version table:
 *** 3.36.0-2ubuntu2 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.0-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CasperVersion: 1.442
Date: Fri Apr  3 14:24:21 2020
DisplayManager: gdm3
GsettingsChanges:
 
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot of screen and instllation output."
   
https://bugs.launchpad.net/bugs/1870597/+attachment/5345770/+files/Screenshot%20from%202020-04-03%2014-27-25.png

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

Title:
  Gnome slows down and stutters when I move the mouse while the
  installer is installing ubuntu 20.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  During the freeze, the output of the install had a message from
  "gdm-x-session" saying "your system is too slow".

  To reproduce:
  1. Launch the Ubuntu installer
  2. Begin the installation process
  3. When the installation process begins, move the cursor around
  4. Notice how the PC freezes and drops mouse events

  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  gnome-shell:
Installed: 3.36.0-2ubuntu2
Candidate: 3.36.0-2ubuntu2
Version table:
   *** 3.36.0-2ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CasperVersion: 1.442
  Date: Fri Apr  3 14:24:21 2020
  DisplayManager: gdm3
  GsettingsChanges:
   
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  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/1870597/+subscriptions

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


[Desktop-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

2020-04-03 Thread Apport retracing service
** Tags added: focal

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Triaged
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f

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

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

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


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

2020-04-03 Thread Apport retracing service
*** This bug is a duplicate of bug 1843982 ***
https://bugs.launchpad.net/bugs/1843982

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1843982, so 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.  Please continue to report any other bugs you may
find.

** Package changed: ubuntu => gnome-shell (Ubuntu)

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1870591/+attachment/5345742/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1870591/+attachment/5345744/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1870591/+attachment/5345749/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1870591/+attachment/5345750/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1870591/+attachment/5345751/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1870591/+attachment/5345754/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1870591/+attachment/5345755/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1843982
   Various programs crashed with SIGSEGV in g_str_hash() from 
g_hash_table_lookup() from update_user()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  system freezes during start
  from tty3: sudo killall gdm3
  and after that i was able to login to desktop

  will return to xubuntu

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 20:38:47 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
   ()
() at /lib/x86_64-linux-gnu/libc.so.6
   g_str_hash () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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


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

2020-04-03 Thread Márcio Oliveira Corbolan
** Changed in: nautilus (Ubuntu)
 Assignee: (unassigned) => Márcio Oliveira Corbolan (marciocorbolan)

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

Title:
  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  after turn on pc

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 25 01:52:06 2019
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-12-22 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f3fb437f962:mov0x380(%rax),%rax
   PC (0x7f3fb437f962) ok
   source "0x380(%rax)" (0x0380) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  separator:
   
  usr_lib_nautilus:

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

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


[Desktop-packages] [Bug 1854621] Re: ubuntu 20.04 daily boots with no background, selecting other background has warped picture

2020-04-03 Thread Brian Murray
We believe that this issue has been fixed with the Beta release of
Ubuntu 20.04. Could you please confirm that the background is no longer
black / missing? Thanks in advance!

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Incomplete

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

Title:
  ubuntu 20.04 daily boots with no background, selecting other
  background has warped picture

Status in ubuntu-meta package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 daily - verified (check disc for defects) prior to boot.
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  On booting, the 20.04 daily has no background when desktop is loaded?
  (ie. top panel is there, dock on left side on black screen)

  When changing background (to any already installed), they are warped
  when selected and made the bacground as if corrupted (but small image
  where selection is made looks valid).


  This issue may relate to video card  [radeon]

  ubuntu@ubuntu:~$ sudo lshw -C video
*-display:0   
 description: VGA compatible controller
 product: RV516 [Radeon X1300/X1550 Series]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e 
ioport:dc00(size=256) memory:c-d
*-display:1 UNCLAIMED
 description: Display controller
 product: RV516 [Radeon X1300/X1550 Series] (Secondary)
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0.1
 bus info: pci@:01:00.1
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress bus_master cap_list
 configuration: latency=0
 resources: memory:fe9f-fe9f

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.440
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.432
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:58:33 2019
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1868216] Re: Please include updated Lithuanian, French and Polish translations from upstream

2020-04-03 Thread Gunnar Hjalmarsson
Uploaded to the focal queue

** Changed in: gnome-getting-started-docs (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Please include updated Lithuanian, French and Polish translations from
  upstream

Status in gnome-getting-started-docs package in Ubuntu:
  Fix Committed

Bug description:
  Please include updated Lithuanian, French and Polish translations from
  upstream: https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/
  It is important to do ASAP because Ubuntu will be in Beta freeze very soon - 
Beta will be released at April 2nd.

  See https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/-/commits/master
  for more information.

  Also I'm attaching Lithuanian, French and Polish translations from GIT
  to this bugreport, please include :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-getting-started-docs/+bug/1868216/+subscriptions

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


[Desktop-packages] [Bug 1870102] Re: please sync gnome-user-docs 3.36.1-1 from Debian and add Lithuanian package

2020-04-03 Thread Gunnar Hjalmarsson
Uploaded to the focal queue

** Changed in: gnome-user-docs (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  please sync gnome-user-docs 3.36.1-1 from Debian and add Lithuanian
  package

Status in gnome-user-docs package in Ubuntu:
  Fix Committed

Bug description:
  Please sync gnome-user-docs 3.36.1-1 from Debian and add gnome-user-docs-lt 
(Lithuanian) package - Lithuanian translation is missing in 3.36.0 and is added 
only in 3.36.1 release.
  I'm currently translating ubuntu-docs to Lithuanian language, so, it would be 
nice to have Ubuntu 20.04 release candidate with Lithuanian documentation :)

  Explanation of FeatureFreeze exception:
  3.36.1-1 contains newly added Lithuanian translation and updates of other 
languages:

  Upstream 3.36.1 NEWS:
   * Updates to GNOME Help (Rafael Fontenelle)
   * Updated translations:
     ca(Jordi Mas)
     es(Daniel Mustieles)
     fi(Jiri Grönroos)
     lt(Aurimas Černius)
     pl(Piotr Drąg)
     pt_BR (Rafael Fontenelle)
     sv(Anders Jonsson)

  debian/changelog since 3.36.0:

  gnome-user-docs (3.36.1-1) unstable; urgency=medium

    * New upstream release

   -- Jeremy Bicha   Sat, 28 Mar 2020 22:24:06 -0400

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

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


[Desktop-packages] [Bug 1870587] [NEW] gnome-calendar segfaults immediately after launch

2020-04-03 Thread James Montgomery
Public bug reported:

Apr 03 13:29:49 JM-Precision-5530 dbus-daemon[1987]: [session uid=1000 
pid=1987] Successfully activated service 'org.gnome.Nautilus'
Apr 03 13:29:49 JM-Precision-5530 dbus-daemon[1987]: [session uid=1000 
pid=1987] Successfully activated service 'org.gnome.Calculator.SearchProvider'
Apr 03 13:29:50 JM-Precision-5530 dbus-daemon[1069]: [system] Successfully 
activated service 'org.freedesktop.timedate1'
Apr 03 13:29:50 JM-Precision-5530 systemd[1]: Started Time & Date Service.
Apr 03 13:29:50 JM-Precision-5530 dbus-daemon[1987]: [session uid=1000 
pid=1987] Successfully activated service 'org.gnome.Calendar'
Apr 03 13:29:51 JM-Precision-5530 dbus-daemon[1069]: [system] Activating via 
systemd: service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.206' (uid=1000 
pid=22475 comm="/usr/bin/gnome-calendar --gapplication-service " 
label="unconfined")
Apr 03 13:29:51 JM-Precision-5530 systemd[1]: Starting Hostname Service...
Apr 03 13:29:51 JM-Precision-5530 dbus-daemon[1069]: [system] Successfully 
activated service 'org.freedesktop.hostname1'
Apr 03 13:29:51 JM-Precision-5530 systemd[1]: Started Hostname Service.
Apr 03 13:29:51 JM-Precision-5530 gnome-calendar[22475]: 
gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
Apr 03 13:29:51 JM-Precision-5530 gnome-calendar[22475]: 
gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
Apr 03 13:29:51 JM-Precision-5530 kernel: gnome-calendar[22475]: segfault at a 
ip 7f3f00e9fb40 sp 7fffa7fabfd8 error 4 in 
libglib-2.0.so.0.6400.1[7f3f00e6e000+84000]
Apr 03 13:29:51 JM-Precision-5530 kernel: Code: 48 85 ff 74 11 0f 1f 44 00 00 
48 89 f8 48 8b 7f 10 48 85 ff 75 f4 c3 0f 1f 00 f3 0f 1e fa 31 c0 48 85 ff 74 
15 0f 1f 44 00 00 <48> 8b 7f 08 83 c0 01 48 85 ff 75 f4 c3 0f 1f 00 c3 66 66 2e 
0f 1f

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-calendar 3.36.0-1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  3 12:41:50 2020
InstallationDate: Installed on 2020-04-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  gnome-calendar segfaults immediately after launch

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Apr 03 13:29:49 JM-Precision-5530 dbus-daemon[1987]: [session uid=1000 
pid=1987] Successfully activated service 'org.gnome.Nautilus'
  Apr 03 13:29:49 JM-Precision-5530 dbus-daemon[1987]: [session uid=1000 
pid=1987] Successfully activated service 'org.gnome.Calculator.SearchProvider'
  Apr 03 13:29:50 JM-Precision-5530 dbus-daemon[1069]: [system] Successfully 
activated service 'org.freedesktop.timedate1'
  Apr 03 13:29:50 JM-Precision-5530 systemd[1]: Started Time & Date Service.
  Apr 03 13:29:50 JM-Precision-5530 dbus-daemon[1987]: [session uid=1000 
pid=1987] Successfully activated service 'org.gnome.Calendar'
  Apr 03 13:29:51 JM-Precision-5530 dbus-daemon[1069]: [system] Activating via 
systemd: service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.206' (uid=1000 
pid=22475 comm="/usr/bin/gnome-calendar --gapplication-service " 
label="unconfined")
  Apr 03 13:29:51 JM-Precision-5530 systemd[1]: Starting Hostname Service...
  Apr 03 13:29:51 JM-Precision-5530 dbus-daemon[1069]: [system] Successfully 
activated service 'org.freedesktop.hostname1'
  Apr 03 13:29:51 JM-Precision-5530 systemd[1]: Started Hostname Service.
  Apr 03 13:29:51 JM-Precision-5530 gnome-calendar[22475]: 
gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
  Apr 03 13:29:51 JM-Precision-5530 gnome-calendar[22475]: 
gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed
  Apr 03 13:29:51 JM-Precision-5530 kernel: gnome-calendar[22475]: segfault at 
a ip 7f3f00e9fb40 sp 7fffa7fabfd8 error 4 in 
libglib-2.0.so.0.6400.1[7f3f00e6e000+84000]
  Apr 03 13:29:51 JM-Precision-5530 kernel: Code: 48 85 ff 74 11 0f 1f 44 00 00 
48 89 f8 48 8b 7f 10 48 85 ff 75 f4 c3 0f 1f 00 f3 0f 1e fa 31 c0 48 85 ff 74 
15 0f 1f 44 00 00 <48> 8b 7f 08 83 c0 01 48 85 ff 75 f4 c3 0f 1f 00 c3 66 66 2e 
0f 1f

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-calendar 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86

[Desktop-packages] [Bug 1870577] [NEW] Dark theme not applied everywhere

2020-04-03 Thread Coeur Noir
Public bug reported:

Hi,

Ubuntu 20.04 ( from live-usb session )

When switching ( from setting, appearance ) to dark theme, it's not
applied everywhere.

Or is it by design ?

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

** Attachment added: "screenshot, expectation"
   
https://bugs.launchpad.net/bugs/1870577/+attachment/5345709/+files/Capture-d-cran-de-2020-04-03-02-18-32.png

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

Title:
  Dark theme not applied everywhere

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hi,

  Ubuntu 20.04 ( from live-usb session )

  When switching ( from setting, appearance ) to dark theme, it's not
  applied everywhere.

  Or is it by design ?

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

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


[Desktop-packages] [Bug 1870575] [NEW] App's name are truncated in full screen grid view

2020-04-03 Thread Coeur Noir
Public bug reported:

Hi,

Ubuntu 20.04, default.

In the global app-menu ( full screen grid view ) app'names are
truncated, only displayed on one line.

There is enough room to display them on two or three lines under each
icon.

Maybe it's not a big readability concern in English but it is in French
and I guess in German and other languages as many app's start with same
first words, i.e. Gestionnaire de… / Éditeur de… / Libre Office…

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

** Attachment added: "screenshot, what's wrong in red, what's good in green"
   
https://bugs.launchpad.net/bugs/1870575/+attachment/5345708/+files/Capture-d-cran-de-2020-04-03-02-04-07.png

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

Title:
  App's name are truncated in full screen grid view

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hi,

  Ubuntu 20.04, default.

  In the global app-menu ( full screen grid view ) app'names are
  truncated, only displayed on one line.

  There is enough room to display them on two or three lines under each
  icon.

  Maybe it's not a big readability concern in English but it is in
  French and I guess in German and other languages as many app's start
  with same first words, i.e. Gestionnaire de… / Éditeur de… / Libre
  Office…

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

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


[Desktop-packages] [Bug 1870560] Re: Client does not renew IP after RADIUS COA disconnect

2020-04-03 Thread Brian Murray
** Package changed: ubuntu => network-manager (Ubuntu)

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

Title:
  Client does not renew IP after RADIUS COA disconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have been testing RADIUS change of authorization on Ubiquiti
  wireless.  I have tested this on Ubuntu 19.04 as well as Ubuntu 19.10
  and the behavior is the same on both as well as when testing on Debian
  or Fedora.  FWIW this is working with a Windows 10 or Android client
  connected to the same wireless SSID on the same wireless AP, so this
  does not seem to be a configuration issue on the AP from what I can
  see.  Below are the logs from the Ubuntu client as well as the RADIUS
  server.  Please let me know if any further info is needed or if this
  behavior is expected.  Log info is below.  Thanks!

  
  ubuntu@ubuntu:/var/log$ journalctl | grep -Ei 'dhcp'
  Mar 26 21:28:30 ubuntu NetworkManager[1127]:   [1585258110.5810] 
dhcp-init: Using DHCP client 'dhclient'

  Client sends an Access-Request to RADIUS server:

  Thu Mar 26 17:29:13 2020
  Packet-Type = Access-Request
  User-Name = "dshields"
  NAS-Identifier = "7483c28d26de"
  Called-Station-Id = "74-83-C2-8D-26-DE:DF-Ubiquiti-Test"
  NAS-Port-Type = Wireless-802.11
  Service-Type = Framed-User
  Calling-Station-Id = "38-59-F9-81-5C-98"
  Connect-Info = "CONNECT 0Mbps 802.11b"
  Acct-Session-Id = "ABB4DA79B50051CB"
  WLAN-Pairwise-Cipher = 1027076
  WLAN-Group-Cipher = 1027076
  WLAN-AKM-Suite = 1027073
  Framed-MTU = 1400
  EAP-Message = 0x022900061500
  State = 0x4cc366d24aea73b029eb30b6d6318ffc
  Message-Authenticator = 0x48aef4abde67bc109ce1689d34b292cb
  NAS-IP-Address = 10.100.10.235

  Thu Mar 26 17:29:13 2020
  Packet-Type = Access-Request
  User-Name = "dshields"
  NAS-Identifier = "7483c28d26de"
  Called-Station-Id = "74-83-C2-8D-26-DE:DF-Ubiquiti-Test"
  NAS-Port-Type = Wireless-802.11
  Service-Type = Framed-User
  Calling-Station-Id = "38-59-F9-81-5C-98"
  Connect-Info = "CONNECT 0Mbps 802.11b"
  Acct-Session-Id = "ABB4DA79B50051CB"
  WLAN-Pairwise-Cipher = 1027076
  WLAN-Group-Cipher = 1027076
  WLAN-AKM-Suite = 1027073
  Framed-MTU = 1400
  EAP-Message = 
0x022a00841500160303004610424104bbae17c4fd4f2c594c2fe9737cc7919914adc728c0c3080fcf9e0f4cec1e1baced618159446d056286c8ca54ab8eb9142a2b1cfd5c88e110e6a28edf4ce943ed1403030001011603030028c00e45cebb1752d0b5c6323f47be852483a27af729b82ee96e3139d24dfa485e8ffed35de2438d54
  State = 0x4cc366d24be973b029eb30b6d6318ffc
  Message-Authenticator = 0x5d0f1396a39e5b0e1e1a0c6118e1ebea
  NAS-IP-Address = 10.100.10.235

  Authentication succeeds and VLAN 230 is returned to client with Access-Accept:

  Thu Mar 26 17:29:13 2020 : Auth: Login OK: [dshields] (from client 
OPSWAT-AP-AC-PRO port 0 via TLS tunnel)
  Thu Mar 26 17:29:13 2020 : Auth: Login OK: [dshields] (from client 
OPSWAT-AP-AC-PRO port 0 cli 38-59-F9-81-5C-98)

  Thu Mar 26 17:29:13 2020
  Packet-Type = Access-Accept
  User-Name = "dshields"
  MS-MPPE-Recv-Key = 
0x0e4b4cd48f891763a1f1792c71047066b1fd70914f7212cf011f1a367277cd02
  MS-MPPE-Send-Key = 
0xc81a04f1482a75cff7cac78876a95391ab9908d613dd2e2476def943bab5cf4c
  EAP-MSK = 
0x0e4b4cd48f891763a1f1792c71047066b1fd70914f7212cf011f1a367277cd02c81a04f1482a75cff7cac78876a95391ab9908d613dd2e2476def943bab5cf4c
  EAP-EMSK = 
0x55d0a72ab01bd0a5ec49a6e081fcecff37357ba89f8c25767d8033e529e45b116a9cec3044cef37c20297c60b8b3b345be1248859214586ad9e925545cf88c14
  EAP-Session-Id = 
0x15066089550d45a92a0c53f9280e765fbdcf813480da08fdbf5b33de44dd5dc9c15e7d1ea91e31c2135dd3b384f8d628548ab4beb299a79ee60836464d78cfcce5
  EAP-Message = 0x032b0004
  Message-Authenticator = 0x
  Calling-Station-Id = "38-59-F9-81-5C-98"
  Tunnel-Type:0 += VLAN
  Tunnel-Medium-Type:0 += IEEE-802
  Tunnel-Private-Group-Id:0 += "230"

  Laptop sends a DHCP request and gets an IP in VLAN 230:

  Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.1150] dhcp4 
(wlp2s0b1): activation: beginning transaction (timeout in 45 seconds)
  Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.1352] dhcp4 
(wlp2s0b1): dhclient started with pid 2626
  Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPDISCOVER on wlp2s0b1 to 
255.255.255.255 port 67 interval 3 (xid=0x6bec8061)
  Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPOFFER of 10.103.230.59 from 
10.103.230.1
  Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPREQUEST for 10.103.230.59 on 
wlp2s0

[Desktop-packages] [Bug 1870560] [NEW] Client does not renew IP after RADIUS COA disconnect

2020-04-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have been testing RADIUS change of authorization on Ubiquiti wireless.
I have tested this on Ubuntu 19.04 as well as Ubuntu 19.10 and the
behavior is the same on both as well as when testing on Debian or
Fedora.  FWIW this is working with a Windows 10 or Android client
connected to the same wireless SSID on the same wireless AP, so this
does not seem to be a configuration issue on the AP from what I can see.
Below are the logs from the Ubuntu client as well as the RADIUS server.
Please let me know if any further info is needed or if this behavior is
expected.  Log info is below.  Thanks!


ubuntu@ubuntu:/var/log$ journalctl | grep -Ei 'dhcp'
Mar 26 21:28:30 ubuntu NetworkManager[1127]:   [1585258110.5810] 
dhcp-init: Using DHCP client 'dhclient'

Client sends an Access-Request to RADIUS server:

Thu Mar 26 17:29:13 2020
Packet-Type = Access-Request
User-Name = "dshields"
NAS-Identifier = "7483c28d26de"
Called-Station-Id = "74-83-C2-8D-26-DE:DF-Ubiquiti-Test"
NAS-Port-Type = Wireless-802.11
Service-Type = Framed-User
Calling-Station-Id = "38-59-F9-81-5C-98"
Connect-Info = "CONNECT 0Mbps 802.11b"
Acct-Session-Id = "ABB4DA79B50051CB"
WLAN-Pairwise-Cipher = 1027076
WLAN-Group-Cipher = 1027076
WLAN-AKM-Suite = 1027073
Framed-MTU = 1400
EAP-Message = 0x022900061500
State = 0x4cc366d24aea73b029eb30b6d6318ffc
Message-Authenticator = 0x48aef4abde67bc109ce1689d34b292cb
NAS-IP-Address = 10.100.10.235

Thu Mar 26 17:29:13 2020
Packet-Type = Access-Request
User-Name = "dshields"
NAS-Identifier = "7483c28d26de"
Called-Station-Id = "74-83-C2-8D-26-DE:DF-Ubiquiti-Test"
NAS-Port-Type = Wireless-802.11
Service-Type = Framed-User
Calling-Station-Id = "38-59-F9-81-5C-98"
Connect-Info = "CONNECT 0Mbps 802.11b"
Acct-Session-Id = "ABB4DA79B50051CB"
WLAN-Pairwise-Cipher = 1027076
WLAN-Group-Cipher = 1027076
WLAN-AKM-Suite = 1027073
Framed-MTU = 1400
EAP-Message = 
0x022a00841500160303004610424104bbae17c4fd4f2c594c2fe9737cc7919914adc728c0c3080fcf9e0f4cec1e1baced618159446d056286c8ca54ab8eb9142a2b1cfd5c88e110e6a28edf4ce943ed1403030001011603030028c00e45cebb1752d0b5c6323f47be852483a27af729b82ee96e3139d24dfa485e8ffed35de2438d54
State = 0x4cc366d24be973b029eb30b6d6318ffc
Message-Authenticator = 0x5d0f1396a39e5b0e1e1a0c6118e1ebea
NAS-IP-Address = 10.100.10.235

Authentication succeeds and VLAN 230 is returned to client with Access-Accept:

Thu Mar 26 17:29:13 2020 : Auth: Login OK: [dshields] (from client 
OPSWAT-AP-AC-PRO port 0 via TLS tunnel)
Thu Mar 26 17:29:13 2020 : Auth: Login OK: [dshields] (from client 
OPSWAT-AP-AC-PRO port 0 cli 38-59-F9-81-5C-98)

Thu Mar 26 17:29:13 2020
Packet-Type = Access-Accept
User-Name = "dshields"
MS-MPPE-Recv-Key = 
0x0e4b4cd48f891763a1f1792c71047066b1fd70914f7212cf011f1a367277cd02
MS-MPPE-Send-Key = 
0xc81a04f1482a75cff7cac78876a95391ab9908d613dd2e2476def943bab5cf4c
EAP-MSK = 
0x0e4b4cd48f891763a1f1792c71047066b1fd70914f7212cf011f1a367277cd02c81a04f1482a75cff7cac78876a95391ab9908d613dd2e2476def943bab5cf4c
EAP-EMSK = 
0x55d0a72ab01bd0a5ec49a6e081fcecff37357ba89f8c25767d8033e529e45b116a9cec3044cef37c20297c60b8b3b345be1248859214586ad9e925545cf88c14
EAP-Session-Id = 
0x15066089550d45a92a0c53f9280e765fbdcf813480da08fdbf5b33de44dd5dc9c15e7d1ea91e31c2135dd3b384f8d628548ab4beb299a79ee60836464d78cfcce5
EAP-Message = 0x032b0004
Message-Authenticator = 0x
Calling-Station-Id = "38-59-F9-81-5C-98"
Tunnel-Type:0 += VLAN
Tunnel-Medium-Type:0 += IEEE-802
Tunnel-Private-Group-Id:0 += "230"

Laptop sends a DHCP request and gets an IP in VLAN 230:

Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.1150] dhcp4 
(wlp2s0b1): activation: beginning transaction (timeout in 45 seconds)
Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.1352] dhcp4 
(wlp2s0b1): dhclient started with pid 2626
Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPDISCOVER on wlp2s0b1 to 
255.255.255.255 port 67 interval 3 (xid=0x6bec8061)
Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPOFFER of 10.103.230.59 from 
10.103.230.1
Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPREQUEST for 10.103.230.59 on 
wlp2s0b1 to 255.255.255.255 port 67 (xid=0x6180ec6b)
Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPACK of 10.103.230.59 from 
10.103.230.1 (xid=0x6bec8061)
Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.7935] dhcp4 
(wlp2s0b1):   address 10.103.230.59
Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.7936] dhcp4 
(wlp2s0b1):   plen 24 (255.255.255.0)
Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.7936] dhcp4 
(wlp2s0b1):   gateway 10.103.23

[Desktop-packages] [Bug 1870574] [NEW] After install in the window 'Ready to go' 'Open software now' does nothing

2020-04-03 Thread corrado venturini
Public bug reported:

Fix for bug #1869591 should be released but I have again the problem
installing from Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-initial-setup 3.36.0-1ubuntu4
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  3 18:19:15 2020
ExecutablePath: /usr/libexec/gnome-initial-setup
InstallationDate: Installed on 2020-04-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
SourcePackage: gnome-initial-setup
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  After install in the window 'Ready to go'  'Open software now'  does
  nothing

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  Fix for bug #1869591 should be released but I have again the problem
  installing from Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-initial-setup 3.36.0-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 18:19:15 2020
  ExecutablePath: /usr/libexec/gnome-initial-setup
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1867000] Re: Clicking "Open in Software" in GNOME Settings does not open Snap Store

2020-04-03 Thread AsciiWolf
Adding this as a downstream patch would resolve (workaround) this issue:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/662

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

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

Title:
  Clicking "Open in Software" in GNOME Settings does not open Snap Store

Status in snap-store:
  New
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  This happens on latest Ubuntu Focal (without deb gnome-software
  /ubuntu-software packages installed, only Snap Store snap). When
  clicking the "Open in Software" button on Applications tab of GNOME
  Settings, nothing happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-store/+bug/1867000/+subscriptions

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


[Desktop-packages] [Bug 1870152] Re: 'System Sounds' string showing not translated

2020-04-03 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-control-center -
1:3.36.1-1ubuntu3

---
gnome-control-center (1:3.36.1-1ubuntu3) focal; urgency=medium

  * debian/patches/0001-sound-Fix-translation-of-System-Sounds.patch:
- Fix system sounds not being translated (LP: #1870152)

 -- Robert Ancell   Thu, 02 Apr 2020
13:47:54 +1300

** Changed in: gnome-control-center (Ubuntu)
   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/1870152

Title:
  'System Sounds' string showing not translated

Status in gnome-control-center:
  Unknown
Status in Ubuntu Translations:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  Please check attachment

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

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


[Desktop-packages] [Bug 1870550] Re: PCI/internal sound card not detected

2020-04-03 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The sound card is not detected on my machine

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 00:51:33 2020
  InstallationDate: Installed on 2020-02-25 (37 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.46
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8UR41PA#ABG
  dmi.sys.vendor: HP

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

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


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

2020-04-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The sound card is not detected on my machine

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 00:51:33 2020
InstallationDate: Installed on 2020-02-25 (37 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/02/2020
dmi.bios.vendor: AMI
dmi.bios.version: F.13
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 86FA
dmi.board.vendor: HP
dmi.board.version: 87.46
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
dmi.product.sku: 8UR41PA#ABG
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug bionic
-- 
PCI/internal sound card not detected
https://bugs.launchpad.net/bugs/1870550
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to alsa-driver in Ubuntu.

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


[Desktop-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2020-04-03 Thread Dan Streetman
Thanks!  Could you check the rfkill code, also?  I think instead of
patching the testcase, it would be better fix rfkill so the change is
effective as soon as it returns; that way users won't experience this
and have to add their own sleep after calling rfkill.

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  New
Status in network-manager source package in Focal:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

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

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


[Desktop-packages] [Bug 1870519] Re: Ubuntu 20.04 Dock - Autohide not working

2020-04-03 Thread Sebastien Bacher
Thank you for your bug report. What session do you use? Is that ubuntu and it's 
dock or dash to dock in a GNOME session?
Could you add your 'journalctl -b 0' log to the bug after triggering the issue?

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

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

Title:
  Ubuntu 20.04 Dock - Autohide not working

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

Bug description:
  Hello,

  Ubuntu 20.04 beta (Apr 2nd 2020)

  1. Set in dconf editor under
  /org/gnome/shell/extensions/dash-to-dock/
  autohide:true
  docker-fixed:false

  2. Maximize some desktop window and the dock disappears.
  Now, move mouse to the dock area but the dock will never appear.

  (on 18.04 this works properly - using the same dconf properties in
  both 20.04 and 18.04)

  It should auto appear when you move the mouse where the dock was
  hidden.

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

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


[Desktop-packages] [Bug 1870564] [NEW] Libreoffice's option "Customize" is imcompatble to decrease its Window size in Ubuntu 19.10

2020-04-03 Thread Pranav bhattarai
Public bug reported:

As discussed here in detail:

https://ask.libreoffice.org/en/question/236517/i-think-we-need-
scroolbar-in-los-customize-option-so-that-users-can-peacefull-use-the-
option-which-are-not-visible-in-the-screen/

I was wondering if it's happening in Ubuntu distros only. Since our
GNOME is unique.

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

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

Title:
   Libreoffice's option "Customize" is imcompatble to decrease its
  Window size in Ubuntu 19.10

Status in libreoffice package in Ubuntu:
  New

Bug description:
  As discussed here in detail:

  https://ask.libreoffice.org/en/question/236517/i-think-we-need-
  scroolbar-in-los-customize-option-so-that-users-can-peacefull-use-the-
  option-which-are-not-visible-in-the-screen/

  I was wondering if it's happening in Ubuntu distros only. Since our
  GNOME is unique.

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

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


  1   2   >