[Bug 1630238] Re: [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer Chromebook R11

2020-07-13 Thread You-Sheng Yang
In bug 1881319 we're having trouble with ELAN touchpads due to
elants_i2c being marked built-in in this bug. I created a PPA in
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1881319 that mark it
back to m while preserving PINCTRL_CHERRYVIEW as y. So I'm crossing post
this message to those had been affected to find some help from you for
verification of this proposed change. Thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630238

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)

2020-07-13 Thread You-Sheng Yang
Please try test kernel in
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1881319, which marks
CONFIG_TOUCHSCREEN_ELAN as m only. We'll also need verification from
users of bug 1630238 before committing to ubuntu kernel to prevent
regression loop. This ppa is currently not yet available, but is
supposed to finish to build in a couple of hours.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881319

Title:
  Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as
  touch panel)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887201] Re: [snap] web bluetooth does not work

2020-07-13 Thread Olivier Tilloy
Now available as revision 1228 in the candidate channel. Please test and
let me know whether this works:

snap refresh chromium --candidate

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887201

Title:
  [snap] web bluetooth does not work

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885693] Re: Unwanted reboot after screen is locked

2020-07-13 Thread Jacob Bunk Nielsen
After running "xset s off -dpms" I haven't seen any crashes for a few
days. I used to have a few crashes every day when connecting to the
dock.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885693

Title:
  Unwanted reboot after screen is locked

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-07-13 Thread Seyeong Kim
@corey.bryant

Hello. I just checked that even I did "sudo add-apt-repository cloud-
archive:mitaka-proposed"

neutron version is the same as mitaka-staging

neutron-linuxbridge-agent/trusty-proposed,trusty,now
2:8.4.0-0ubuntu7.5~cloud0 all [installed]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662324

Title:
  linux bridge agent disables ipv6 before adding an ipv6 address

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1662324/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887481] [NEW] crash on opening of deluge-gtk

2020-07-13 Thread pleabargain
Public bug reported:

user clicked on deluge-gtk desktop icon
deluge began to open then crashed
no warning
no error message

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: deluge-gtk 2.0.3-2
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 14 09:14:45 2020
InstallationDate: Installed on 2015-08-23 (1786 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: deluge
UpgradeStatus: Upgraded to focal on 2020-06-06 (37 days ago)

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887481

Title:
  crash on opening of deluge-gtk

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887479] [NEW] No pkg-config file in libdocopt-dev

2020-07-13 Thread Alexander Sashnov
Public bug reported:

No pkg-config file in libdocopt-dev. It causes build process failed
because it relies on finding a library via pkg-config:

Steps to reproduce:

$ git clone g...@github.com:openzim/zim-tools.git
$ cd zim-tools/
$ mkdir build
$ cd build/
$ meson ..

Actual result:

 The Meson build system
 Version: 0.45.1
 Source dir: /home/alex/tmp/zim-tools
 Build dir: /home/alex/tmp/zim-tools/build
 Build type: native build
 Project name: zim-tools
 Native C compiler: ccache cc (gcc 7.5.0 "cc (Ubuntu 7.5.0-3ubuntu1~18.04) 
7.5.0")
 Native C++ compiler: ccache c++ (gcc 7.5.0 "c++ (Ubuntu 7.5.0-3ubuntu1~18.04) 
7.5.0")
 Build machine cpu family: x86_64
 Build machine cpu: x86_64
 Found pkg-config: /usr/bin/pkg-config (0.29.1)
 Native dependency libzim found: YES 6.1.4
 Dependency rt found: NO

meson.build:20:0: ERROR: Native dependency 'docopt' not found

(please, don't mind this 'rt' library absence, it's OK).


In /home/alex/tmp/zim-tools/build/meson-logs/meson-log.txt:

 Determining dependency 'docopt' with pkg-config executable 
'/usr/bin/pkg-config'
 meson.build:20:0: ERROR: Native dependency 'docopt' not found


Expected result:

Meson should find libdocopt via pkg-config


Additional info

 $ dpkg -L libdocopt-dev | grep pc
 

Other packages have it, for example:

 $ dpkg -L libzstd-dev | grep pc
 /usr/lib/x86_64-linux-gnu/pkgconfig/libzstd.pc

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libdocopt-dev 0.6.2-2
Uname: Linux 4.19.91-041991-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 14 12:41:18 2020
Dependencies:
 gcc-8-base 8.4.0-1ubuntu1~18.04
 libc6 2.27-3ubuntu1
 libdocopt0 0.6.2-2
 libgcc1 1:8.4.0-1ubuntu1~18.04
 libstdc++6 8.4.0-1ubuntu1~18.04
InstallationDate: Installed on 2019-10-27 (260 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: docopt.cpp
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: docopt.cpp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887479

Title:
  No pkg-config file in libdocopt-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docopt.cpp/+bug/1887479/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887478] [NEW] missing symlinks for login and logout files used by gnome

2020-07-13 Thread Yousuf 'Jay' Philips
Public bug reported:

Merge request submitted upstream in Debian to fix the issue.
https://salsa.debian.org/gnome-team/sound-theme-freedesktop/-/merge_requests/1

** Affects: sound-theme-freedesktop (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887478

Title:
  missing symlinks for login and logout files used by gnome

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1887478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853195] Re: dpdk 18.11.4-1ubuntu1 ADT test failure with linux 5.4.0-6.7 => need DPDK 19.11 in Focal

2020-07-13 Thread Christian Ehrhardt 
This is only open for the DKMS issues in DPDK 17.11 @ Bionic.
But those were fine recently with DPDK 17.11.9 for example.

See http://autopkgtest.ubuntu.com/packages/d/dpdk/bionic/amd64

We just forgot to close this bug task when the related stable release
included a fix :-/

** Changed in: dpdk (Ubuntu Bionic)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853195

Title:
  dpdk 18.11.4-1ubuntu1 ADT test failure with linux 5.4.0-6.7 => need
  DPDK 19.11 in Focal

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887397] Re: perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1

2020-07-13 Thread zanyrain
The same thing happens to me when I'm trying to rebuild Linux 5.7 kernel
on debian testing.


gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wdate-time -D_FORTIFY_SOURCE=2 
-I/home/zanyrain/r7000-dev/linux-5.7.6/tools/perf 
-I/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf 
-isystem /home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/include 
-Wbad-function-cast -Wdeclaration-after-statement -Wformat-security 
-Wformat-y2k -Winit-self -Wmissing-declarations -Wmissing-prototypes 
-Wnested-externs -Wno-system-headers -Wold-style-definition -Wpacked 
-Wredundant-decls -Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef 
-Wwrite-strings -Wformat -Wstrict-aliasing=3 -Wshadow 
-DHAVE_ARCH_X86_64_SUPPORT 
-I/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/arch/x86/include/generated
 -DHAVE_SYSCALL_TABLE_SUPPORT -DHAVE_PERF_REGS_SUPPORT 
-DHAVE_ARCH_REGS_QUERY_REGISTER_OFFSET -O6 -fno-omit-frame-pointer -ggdb3 
-funwind-tables -Wall -Wextra -std=gnu99 -fstack-protector-all 
-D_FORTIFY_SOURCE=2 -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE 
-I/home/zanyrain/r7000-dev/linux-5.7.6/tools/lib/perf/include 
-I/home/zanyrain/r7000-dev/linux-5.7.6/tools/perf/util/include 
-I/home/zanyrain/r7000-dev/linux-5.7.6/tools/perf/arch/x86/include 
-I/home/zanyrain/r7000-dev/linux-5.7.6/tools/include/ 
-I/home/zanyrain/r7000-dev/linux-5.7.6/tools/arch/x86/include/uapi 
-I/home/zanyrain/r7000-dev/linux-5.7.6/tools/include/uapi 
-I/home/zanyrain/r7000-dev/linux-5.7.6/tools/arch/x86/include/ 
-I/home/zanyrain/r7000-dev/linux-5.7.6/tools/arch/x86/ 
-I/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf//util
 -I/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/ 
-I/home/zanyrain/r7000-dev/linux-5.7.6/tools/perf/util 
-I/home/zanyrain/r7000-dev/linux-5.7.6/tools/perf 
-I/home/zanyrain/r7000-dev/linux-5.7.6/tools/lib/ 
-DHAVE_SYNC_COMPARE_AND_SWAP_SUPPORT -DHAVE_PTHREAD_ATTR_SETAFFINITY_NP 
-DHAVE_PTHREAD_BARRIER -DHAVE_EVENTFD -DHAVE_GET_CURRENT_DIR_NAME -DHAVE_GETTID 
-DHAVE_FILE_HANDLE -DHAVE_DWARF_GETLOCATIONS_SUPPORT -DHAVE_GLIBC_SUPPORT 
-DHAVE_AIO_SUPPORT -DHAVE_SCHED_GETCPU_SUPPORT -DHAVE_SETNS_SUPPORT 
-DHAVE_CSTRACE_SUPPORT  -DHAVE_LIBELF_SUPPORT -DHAVE_LIBELF_MMAP_SUPPORT 
-DHAVE_ELF_GETPHDRNUM_SUPPORT -DHAVE_GELF_GETNOTE_SUPPORT 
-DHAVE_ELF_GETSHDRSTRNDX_SUPPORT -DHAVE_DWARF_SUPPORT  -DHAVE_LIBBPF_SUPPORT 
-DHAVE_BPF_PROLOGUE -DHAVE_JITDUMP -DHAVE_DWARF_UNWIND_SUPPORT 
-DNO_LIBUNWIND_DEBUG_FRAME -DHAVE_LIBUNWIND_SUPPORT  -DHAVE_SLANG_SUPPORT 
-DHAVE_LIBPERL_SUPPORT -DHAVE_TIMERFD_SUPPORT -DHAVE_LIBPYTHON_SUPPORT 
-DHAVE_CPLUS_DEMANGLE_SUPPORT -DHAVE_ZLIB_SUPPORT -DHAVE_LZMA_SUPPORT 
-DHAVE_LIBCAP_SUPPORT -DHAVE_BACKTRACE_SUPPORT -DHAVE_LIBNUMA_SUPPORT 
-DHAVE_KVM_STAT_SUPPORT -DHAVE_PERF_READ_VDSO32 -DHAVE_PERF_READ_VDSOX32 
-DHAVE_LIBBABELTRACE_SUPPORT  -DHAVE_AUXTRACE_SUPPORT 
-I/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/ 
-Wl,-z,relro -Xlinker 
--dynamic-list=/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/plugins/libtraceevent-dynamic-list
 \

/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/perf-in.o
 
/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/pmu-events/pmu-events-in.o
 -Wl,--whole-archive 
/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/libapi.a
 
/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/libtraceevent.a
 
/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/libsubcmd.a
 
/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/libperf.a
 
/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/libbpf.a
  -Wl,--no-whole-archive -Wl,--start-group -lpthread -lrt -lm -ldl 
-lopencsd_c_api -lopencsd -lelf -ldw -lunwind-x86_64 -lunwind -llzma -lslang 
-lperl -ldl -lm -lpthread -lc -lcrypt -lpython3.8 -lcrypt -lpthread -ldl -lutil 
-lm -lm -lutil -liberty -lz -llzma -lcap -lnuma -lbabeltrace-ctf 
-Wl,--end-group -o 
/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/perf
/usr/bin/ld:/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
/usr/bin/ld:/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
/usr/bin/ld:/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/plugins/libtraceevent-dynamic-list:2:
 syntax error in dynamic list
collect2: error: ld returned 1 exit status
make[5]: *** [Makefile.perf:629: 
/home/zanyrain/r7000-dev/linux-5.7.6/debian/build/build-tools/tools/perf/perf] 
Error 1
make[5]: Leaving directory '/home/zanyrain/r7000-dev/linux-5.7.6/tools/perf'
make[4]: *** [Makefile.perf:225: sub-make] Error 2

[Bug 1881996] Re: Enable e1000e S0ix on Tiger Lake

2020-07-13 Thread Hsuan-Yu Lin
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881996

Title:
  Enable e1000e S0ix on Tiger Lake

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1881996/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887235] Re: System hangs, syslog filled with `org.gnome.Shell.desktop` reports

2020-07-13 Thread Daniel van Vugt
OK then, please just run these commands (after the problem has been
happening):

  journalctl -b0 > journal.txt
  gsettings list-recursively org.gnome.shell > shell-settings.txt

and attach the resulting two text files here.

Please also attach a screenshot of your desktop (use the PrtScn key and
then look in your Pictures directory), so we can see if there's anything
obviously unusual.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887235

Title:
  System hangs, syslog filled with `org.gnome.Shell.desktop` reports

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886736] Re: My PC froze, got a black screen multiple times, and locked me out 3 times before I could log back in and use my PC again

2020-07-13 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886736

Title:
  My PC froze, got a black screen multiple times, and locked me out 3
  times before I could log back in and use my PC again

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886269] Re: ps/2 mouse not working

2020-07-13 Thread You-Sheng Yang
@Jatinderpal, couldn't get you. So you've reinstalled your system, get
upgraded, then is your PS/2 mouse working as expected now? If not, and
yet the kernel parameter still works for you, then you may choose not to
fix it and carry it forever. Leave this bug in INCOMPLETE state and it
will expire after 60 days.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886269

Title:
  ps/2 mouse not working

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878544] Re: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub)

2020-07-13 Thread koba
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu)
   Status: Fix Committed => In Progress

** Changed in: linux (Ubuntu)
   Status: In Progress => Invalid

** Changed in: linux (Ubuntu)
 Assignee: koba (kobako) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878544

Title:
  kernel NULL pointer dereference when plugging/unpluggin USB-c (power
  or hub)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887476] [NEW] crash without warning on adding via xdg

2020-07-13 Thread pleabargain
Public bug reported:

user clicked magnet torrent
deluge opened
user selected target download folder
deluge crashed without warning

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: deluge-gtk 2.0.3-2
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 14 07:48:16 2020
InstallationDate: Installed on 2015-08-23 (1786 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: deluge
UpgradeStatus: Upgraded to focal on 2020-06-06 (37 days ago)

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887476

Title:
  crash without warning on adding via xdg

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

2020-07-13 Thread Chris Guiver
Description was edits:


1: current/up-to-date summary @ top
my boxes still impacted
---
2: Original detail

original detail now includes Sudodus' boxes, at least some of them.
quite a bit of my 'thoughts/doubts' were removed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1861177] Autopkgtest regression report (libseccomp/2.4.3-1ubuntu3.18.04.3)

2020-07-13 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted libseccomp (2.4.3-1ubuntu3.18.04.3) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

lxc/3.0.3-0ubuntu1~18.04.1 (arm64)
systemd/unknown (armhf)
systemd/237-3ubuntu10.41 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#libseccomp

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861177

Title:
  seccomp_rule_add is very slow

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

2020-07-13 Thread You-Sheng Yang
** Tags added: hwe-touchpad

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-07-13 Thread Seyeong Kim
I'm going to verify mitaka this week. building trusty-mitaka env now

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662324

Title:
  linux bridge agent disables ipv6 before adding an ipv6 address

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1662324/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

2020-07-13 Thread Chris Guiver
** Description changed:

+ When reported the groovy daily was failing on most boxes..
+ Changes have been made and now it fails to boot on far fewer boxes.
+ Occurs if ISO is written via `dd`, `mkusb` or `Startup Disk Creator`
+ 
+ Boxes still impacted are (guiverc's boxes)
+ 
+ hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
+ hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915)
+ 
+ ---
+ Original detail follows - (with minimal edits)
+ 
  This is very similar to https://bugs.launchpad.net/bugs/1883040
  
  Boxes that have failed to boot it are
-   
+ 
  dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 
pro/xt)
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
+ dell [optiplex] 780 (c2q-q9400, 4gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)
  hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
  hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
  sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
  
- I can't get md5sums because of errors at
- http://iso.qa.ubuntu.com/qatracker/milestones/413/builds/216043/downloads,
- so I just re-ran zsync to verify download & it confirms 100% downloaded,
- so I'm assuming that isn't at fault.
+ --  sudodus' boxes
+ Acer [Aspire] E3-111-P60S (Pent.N3530, 4GB, Intel HD Graphics, Realtek 
RTL8111/81681/8411 GB Ethernet, Qualcomm Atheros AR9462 Wireless, Bluetooth 
Atheros A315-53, 500 GB hd)
+ 
+ Dell [Optiplex] 7010 ( i5-3470 , 16 GB, Intel Graphics 2500, Intel
+ 82579LM GB Ethernet ,1TB hd) VirtualBox
+ 
+ Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 
chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 
b/g/N, Bluetooth 4.0, 500 GB hd)
+ --
  
  The ISO was written twice to two different thumb-drives. Same issue each
  time on same boxes.
  
  On a number of boxes it’s wanting me to download aka
  https://bugs.launchpad.net/ubuntu-cdimage/+bug/1883040 however it’s done
  that on boxes not impacted by that bug, which makes me think thumb-
  drive/squashfs errs related.  Also results of boot appeared different on
  varying boxes (inconsistent; dc7700 reported no thumb-drive; d755-5 also
  did that sometimes, sometimes it got to wanting to download - those two
  boxes were impacted by prior report; the remaining boxes were more
  consistent in response..; but if trouble reading data on thumb-drive
  then the slower boxes (dc7700/d755-5) may have more issues & thus be
  less consistent?)
  
- Further I noted @leok has recorded a valid test today which means a real
- issue is unlikely (this severe anyway), thus thumb-drives & me (operator
- error) not ruled out.
- 
  I'll file this as a bug report so I can close my failed QA-tests, but
  I'm considering changing the status to 'incomplete', and re-testing
  tomorrow, OR it needs me to re-write ISO from a different box to a
  third-thumb-drive as I don't think I've ruled out media issues given
  Leok's report.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886148] Re: failure to boot groovy daily

2020-07-13 Thread Chris Guiver
Lubuntu groovy daily 2020-07-13  (identical file as per #49)

I used (due comment #47) `Startup Disk Creator` on my main box to write
this media and it's still failing on

hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915)

The media is good, booting normally (passing checks) on
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)


On both old HP boxes I get bright/faster pattern of flashes on the thumb-drive 
very briefly on selecting USB DEVICE for booting, then I get the hdd's grub 
menu appear and flashing on thumb-drive returns to normal as if BIOS/box 
firmware gave up on usb-media. 

In my opinion, media written via `dd`, `mkusb` & `Startup Disk Creator`
is identical (I don't use persistence or options in QA-testing so simple
'live' media with mkusb/dus)


No change to prior attempts since this bug was discovered on the dc7700 & 
dc7900, except initially it failed to boot on most if not all my boxes when 
initially reported.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148

Title:
  failure to boot groovy daily

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1862503] Re: Installer crashed when using btrfs

2020-07-13 Thread Launchpad Bug Tracker
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862503

Title:
  Installer crashed when using btrfs

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875340] Re: snap refresh schedule allows laptops to miss updates

2020-07-13 Thread Launchpad Bug Tracker
[Expired for snapd (Ubuntu) because there has been no activity for 60
days.]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875340

Title:
  snap refresh schedule allows laptops to miss updates

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875532] Re: trying to compile gcc make build and getting errors

2020-07-13 Thread Launchpad Bug Tracker
[Expired for gcc-9 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gcc-9 (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875532

Title:
  trying to compile gcc make build and getting errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878613] Re: UI freeze

2020-07-13 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878613

Title:
  UI freeze

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878610] Re: Ubuntu installer crashed

2020-07-13 Thread Launchpad Bug Tracker
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878610

Title:
  Ubuntu installer crashed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1855318] Re: autofs tries to find .xdg-volume-info and autorun.inf

2020-07-13 Thread Launchpad Bug Tracker
[Expired for autofs (Ubuntu) because there has been no activity for 60
days.]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855318

Title:
  autofs tries to find .xdg-volume-info and autorun.inf

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873594] Re: sporadic black screen freeze on lenovo e595 Ryzen 3700U

2020-07-13 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873594

Title:
  sporadic black screen freeze on lenovo e595 Ryzen 3700U

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878512] Re: install crash from usb flash drive

2020-07-13 Thread Launchpad Bug Tracker
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878512

Title:
  install crash from usb flash drive

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887235] Re: System hangs, syslog filled with `org.gnome.Shell.desktop` reports

2020-07-13 Thread Sirad
I am afraid the comment `apport-collect 1887235` fails on my system with the 
following error: `ERROR: The python3-launchpadlib package is not installed. 
This functionality is not available.`.
I have followed 
https://help.ubuntu.com/community/ReportingBugs#Error:_The_launchpadlib_Python_module_is_not_installed
 but the error persists.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887235

Title:
  System hangs, syslog filled with `org.gnome.Shell.desktop` reports

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878482] Re: EPSON WF 3520 driver problem - PpdFiles: Error

2020-07-13 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878482

Title:
  EPSON WF 3520 driver problem - PpdFiles: Error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878667] Re: Gnome Shell freezes and then shows the window previews of Firefox twice, one over the over

2020-07-13 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878667

Title:
  Gnome Shell freezes and then shows the window previews of Firefox
  twice, one over the over

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887016] Re: Openssh default config has two PasswordAuthentication params

2020-07-13 Thread Rulon Oboev
What image are you using?

I've got the same problem with 20.04-live-server-amd64.iso
(https://releases.ubuntu.com/20.04/ubuntu-20.04-live-server-amd64.iso)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887016

Title:
  Openssh default config has two PasswordAuthentication params

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877601] Re: /usr/share/alsa missing within snap

2020-07-13 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877601

Title:
  /usr/share/alsa missing within snap

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871680] Re: Some snaps such as VLC crashes on start

2020-07-13 Thread Launchpad Bug Tracker
[Expired for snapd (Ubuntu) because there has been no activity for 60
days.]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871680

Title:
  Some snaps such as VLC crashes on start

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)

2020-07-13 Thread Hui Wang
Yes, linux-module-extra is needed since all audio driver kernel modules
are in this deb.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886341

Title:
  Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal
  audio devices to fail to load w/o unacceptable workaround (Lenovo
  IdeaPad 5 15IIL05)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)

2020-07-13 Thread Corbin
It actually didn't work for me, but that is likely because i did not
load linux-modules-extra. THe download link for the deb keeps failing,
but I'll try again tomorrow. So please disregard until then.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886341

Title:
  Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal
  audio devices to fail to load w/o unacceptable workaround (Lenovo
  IdeaPad 5 15IIL05)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887473] Status changed to Confirmed

2020-07-13 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887473

Title:
  timer_settime02 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887235] Re: System hangs, syslog filled with `org.gnome.Shell.desktop` reports

2020-07-13 Thread Sirad
I have a completely vanilla ubuntu install, nothing non-standard. (I
don't even know how to install extensions tbh xD.)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887235

Title:
  System hangs, syslog filled with `org.gnome.Shell.desktop` reports

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1886269] Re: ps/2 mouse not working

2020-07-13 Thread Jatinderpal Singh
Yes please, I tried as you suggested to install new kernel, but the problem
was that my system was hacked by some other bug with the name 'kluser', I
tried everything but in vain, so I reinstalled system and then kept on
upgrading because updating was still hacked by the bug as it was indeed
imbedded in the hard drive, then I gave command to reinstall original sound
and graphic drivers and the mouse started working. Now I don't know how
that happened but I still believe that reminiscence of old bug is there and
computer sometimes misbehave. As I have fully upgraded the system with 20FF
and keeping that misbehaving also now suggest please should I do it again
or not, as my professional work also suffers being my only computer. Thanks
a lot.

On Mon, 13 Jul, 2020, 13:01 You-Sheng Yang, <1886...@bugs.launchpad.net>
wrote:

> Please test kernels from
> https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1886269 . Before we
> may continue to send a fix to upsteam kernel mailing list for review, so
> that you don't have to carry that boot parameter, we will need your
> confirmation that this fix actually works.
>
> The PPA may take up to 10 hours from now to complete, but when it's done
> please test one of the kernels with:
>
> 1. remove that grub boot parameter. If you etched that into
> /etc/default/grub directly before, please temporarily remove that
> parameter and run `sudo update-grub` to sync the generated config.
>
> 2. Run `sudo add-apt-repository ppa:vicamo/ppa-1886269` to add the
> repository.
>
> 3. Run following command to install ppa kernel:
>
>$ sudo apt install \
>linux-modules-extra-4.15.0-112-generic=4.15.0-112.113+lp1886269 \
>linux-image-unsigned-4.15.0-112-generic=4.15.0-112.113+lp1886269 \
>linux-headers-4.15.0-112-generic=4.15.0-112.113+lp1886269 \
>linux-headers-4.15.0-112=4.15.0-112.113+lp1886269
>
> 4. Reboot and select kernel "4.15.0-112-generic".
>
> 5. Attach dmesg log here.
>
> Thank you.
>
> ** Description changed:
>
>   ps/2 mouse not working , gave some command in terminal , this bug came
>   out.
> +
> + See https://ark.intel.com/content/www/us/en/ark/products/39683/intel-
> + desktop-board-dg41rq.html
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7.1
>   ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
>   Uname: Linux 4.15.0-109-generic x86_64
>   .tmp.unity_support_test.0:
> -
> +
>   ApportVersion: 2.20.9-0ubuntu7.15
>   Architecture: amd64
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Jul  4 19:25:07 2020
>   DistUpgraded: 2020-07-03 12:12:10,464 DEBUG Running PostInstallScript:
> './xorg_fix_proprietary.py'
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   GraphicsCard:
> -  Intel Corporation 4 Series Chipset Integrated Graphics Controller
> [8086:2e32] (rev 03) (prog-if 00 [VGA controller])
> -Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics
> Controller [8086:d613]
> +  Intel Corporation 4 Series Chipset Integrated Graphics Controller
> [8086:2e32] (rev 03) (prog-if 00 [VGA controller])
> +Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics
> Controller [8086:d613]
>   InstallationDate: Installed on 2020-06-30 (4 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic
> root=UUID=7093ceae-5eb7-497e-8809-023c282ce7a1 ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   UpgradeStatus: Upgraded to bionic on 2020-07-03 (1 days ago)
>   dmi.bios.date: 01/08/2009
>   dmi.bios.vendor: Intel Corp.
>   dmi.bios.version: RQG4110H.86A.0009.2009.0108.1005
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: DG41RQ
>   dmi.board.vendor: Intel Corporation
>   dmi.board.version: AAE54511-203
>   dmi.chassis.type: 3
>   dmi.modalias:
> dmi:bvnIntelCorp.:bvrRQG4110H.86A.0009.2009.0108.1005:bd01/08/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-203:cvn:ct3:cvr:
>   version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
>   version.libdrm2: libdrm2 2.4.101-2~18.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
>   version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
>   version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.5-1ubuntu1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20171229-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
>   xserver.bootTime: Fri Jul  3 08:17:23 2020
>   xserver.configfile: default
>   xserver.errors:
> -
> +
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
> -
> +
>   xserver.version: 2:1.18.4-0ubuntu0.8
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> http

[Bug 1887473] [NEW] timer_settime02 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

2020-07-13 Thread Po-Hsu Lin
Public bug reported:

Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other 
arches)
And B/E/F s390x as well.

<<>>
tag=timer_settime02 stime=1594698491
cmdline="timer_settime02"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
timer_settime02.c:78: INFO: Testing variant: syscall with old kernel spec
timer_settime02.c:89: INFO: Testing for setting new_set pointer to NULL:
timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: 
EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL 
(22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:89: INFO: Testing for setting tv_nsec to a negative value:
timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: 
EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL 
(22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:89: INFO: Testing for setting tv_nsec value too high:
timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: 
EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL 
(22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:89: INFO: Testing for passing pointer to invalid timer_id:
timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: 
EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL 
(22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:89: INFO: Testing for passing invalid address for new_value:
timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EFAULT (14)
timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EFAULT (14)
timer_set

[Bug 1887473] Re: timer_settime02 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

2020-07-13 Thread Po-Hsu Lin
This issue can be found on 4.4.0-185-generic as well.

It looks like a test case issue after commit:
50a2cb874188c ("syscalls: Fix issues around calling syscalls with old timespec")
https://github.com/linux-test-project/ltp/commit/50a2cb874188c89e03501f9d68585d3e256f3fc7

The test will pass after revert to
50a2cb874188c89e03501f9d68585d3e256f3fc7^

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887473

Title:
  timer_settime02 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887469] Re: timer_settime01 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

2020-07-13 Thread Po-Hsu Lin
It looks like a test case issue after commit:
50a2cb874188c ("syscalls: Fix issues around calling syscalls with old timespec")
https://github.com/linux-test-project/ltp/commit/50a2cb874188c89e03501f9d68585d3e256f3fc7

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887469

Title:
  timer_settime01 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884933] Re: Backport casper changes from groovy to support interactive network boot on focal, and improved interractive boot UX on server

2020-07-13 Thread Michael Hudson-Doyle
Hm so multipath -r fails in this system? Can you test in a way that
doesn't use the interactive boot set up this ticket is about? Because I
don't think it's relevant but it would be nice to be sure.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884933

Title:
  Backport casper changes from groovy to support interactive network
  boot on focal, and improved interractive boot UX on server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1884933/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887469] Re: timer_settime01 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

2020-07-13 Thread Po-Hsu Lin
This issue can be found on 4.4.0-185-generic as well.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887469

Title:
  timer_settime01 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887469] Status changed to Confirmed

2020-07-13 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887469

Title:
  timer_settime01 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887469] [NEW] timer_settime01 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

2020-07-13 Thread Po-Hsu Lin
Public bug reported:

Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other 
arches)
And B/E/F s390x as well.

<<>>
tag=timer_settime01 stime=1594697076
cmdline="timer_settime01"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
timer_settime01.c:142: INFO: Testing variant: syscall with old kernel spec
timer_settime01.c:70: INFO: Testing for general initialization:
timer_settime01.c:125: PASS: CLOCK_REALTIME was successful
timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:70: INFO: Testing for setting old_value:
timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:70: INFO: Testing for using periodic timer:
timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:70: INFO: Testing for using absolute time:
timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)
timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22)
timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22)

HINT: You _MAY_ be missing kernel fixes, see:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f18ddc13af98

Summary:
passed   1
failed   46
skipped  8
warnings 0
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<>>

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-186-generic 4.4.0-186.216
ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228
Uname: Linux 4.4.0-186-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access '/dev/snd

[Bug 1882885] Re: FP Auth enroll for Multi user Scenario

2020-07-13 Thread PRASAD HEGDE
Attaching the fprintd log from journactl..

** Attachment added: "temp.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882885/+attachment/5392461/+files/temp.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882885

Title:
  FP Auth  enroll for Multi user Scenario

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1690085]

2020-07-13 Thread massivebaze
It amazing tho, but most of all thanks for this.i would like to visit here 
https://vibenext.com/
https://massivebaze.xyz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690085

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1690085]

2020-07-13 Thread pmenzel+bugzilla.kernel.org
(In reply to Ashesh Ambasta from comment #699)

> Created attachment 290243 [details]
> attachment-20700-0.html

I am getting:

> Sorry, you are not authorized to access attachment #290243.

[…]

> AMD did publish an errata in which they claim an issue like this exists; 
> but a solution is ruled out. Which is further bad news. There was some 
> discussion on a fix being at the kernel level, but that isn't anywhere 
> in sight either. I believe these CPU's are plagued by several issues, 
> which probably makes a fix for this at the kernel level hard. However, 
> Windows seems to have managed to fix it.

That’s interesting. Could you please share the URL to these statements?

[…]

raulvior.bcn, Asheesh: Please always remove the cited parts, as
otherwise the Web issue page gets even more convoluted. Thanks.


> Anyway; rants aside, this is my current take on the CPU.
> 
> On 7/12/20 3:58 PM, bugzilla-dae...@bugzilla.kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=196683
> >
> > --- Comment #698 from raulvior@gmail.com ---
> > Did you ask for an RMA? Did it work?
> > (In reply to Ashesh Ambasta from comment #692)
> >> As a last resort, I've tried `idle=halt` on this machine. And yet my
> >> system just crashed after 3 weeks of uptime.
> >>
> >> I'm done with AMD. I will RMA this processor to try things out, but
> >> overall, if that doesn't work, this thing is headed to the junkyard and
> >> I'm going to live with Intel.
> >>
> >> At least in the 13 or so odd Intel systems I've tried, I've not had
> >> exhasperating issues like these where the company is positively trying
> >> to ignore this ongoing issue.
> >>
> >> This is disgusting from AMD.
> >>
> >> On 6/11/20 6:03 PM, bugzilla-dae...@bugzilla.kernel.org wrote:
> >>> https://bugzilla.kernel.org/show_bug.cgi?id=196683
> >>>
> >>> --- Comment #689 from raulvior@gmail.com ---
> >>> (In reply to raulvior.bcn from comment #653)
>  (In reply to txrx from comment #651)
> 
>  Typical Current Idle might not be working. Read the sensor output. If
>  voltage is not higher than without enabling it, try to increase the core
>  voltage.
> 
>  My Ryzen 7 1800X seems to not produce hangs since I upgraded to 1003ABB
> >> with
>  an ASUS Crosshair VI Hero and enabled Typical current idle.
> 
> 
> > I was able to update my BIOS to version 18, but my system still locks
> up.
> > I tried the following with the new BIOS:
> >- use factory defaults
> >- disable SMT
> >- disable SMT with Typical Current Idle
> >- all of the above with SVM disabled/enabled
> > Right now I set the power supply idle control to "Low ..." and will
> >> report
> > back.
> >
> >>> The motherboard kept hanging. I had to remove the Vitals GNOME Extension.
> >> It
> >>> seems that polling voltage values hangs the motherboard... Still, there
> are
> >>> times that the computer does not come back from suspend. There's
> something
> >>> wrong with the BIOS/UEFI.
> >>>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690085

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887459] Re: clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

2020-07-13 Thread Po-Hsu Lin
** Description changed:

  Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other 
arches)
  And B/E/F s390x as well.
+ 
+ This is a new test case added between this and the last cycle.
  
  <<>>
  tag=clock_gettime04 stime=1594692118
  cmdline="clock_gettime04"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
  tst_test.c:1292: BROK: Test killed by SIGFPE!
  
  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>
  
  Error message can be found in syslog:
   report_user_fault: 159 callbacks suppressed
   User process fault: interruption code 0009 ilc:2 in 
clock_gettime04[113b0+22000]
   CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P   O
4.4.0-186-generic #216-Ubuntu
   task: 0007aa6de348 ti: 0007ada34000 task.ti: 0007ada34000
   User PSW : 070510018000 000113b18878
  R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:1 PM:0 EA:3
   User GPRS:  0b0cd725 000113b1d026 
000113b1d00e
   0b0cd725 000113b19bc4 
03ffe687e770
  000113b28f38 03ff941fe128 000113b28ec8 
075fcbb9
  03ff941a5000 000113b1d098 000113b1843e 
03ffe687e1f8
   User Code: 000113b1886a: e300a0380016  llgf%r0,56(%r10)
     000113b18870: a749   lghi%r4,0
    #000113b18874: b9870040   dlgr%r4,%r0
    >000113b18878: c0508328   larl%r5,113b28ec8
     000113b1887e: eb140002000d   sllg%r1,%r4,2
     000113b18884: e3119012   lt  %r1,0(%r1,%r9)
     000113b1888a: a784009a   brc 8,113b189be
     000113b1888e: e3405044   lg  %r4,64(%r5)
   Last Breaking-Event-Address:
    [<000113b18860>] 0x113b18860
  
  Kernel tainted flag is 4097 after a clean boot, it won't be changed after the 
test:
  $ cat /proc/sys/kernel/tainted
  4097
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-186-generic 4.4.0-186.216
  ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228
  Uname: Linux 4.4.0-186-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon Jul 13 22:02:08 2020
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
  
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-186-generic N/A
   linux-backports-modules-4.4.0-186-generic  N/A
   linux-firmware 1.157.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887459

Title:
  clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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-07-13 Thread hugh chao
the origin change was in 
'''
commit 9dadfd82504afa114b39e508e4580cb0212468ea (tag: pkg/import/2.00-20)
Author: Colin Watson 
Date:   Thu Nov 14 10:49:31 2013 +

+ Set vt.handoff=7 for smooth handoff to kernel graphical mode.
'''

https://git.launchpad.net/~hugh712/ubuntu/+source/grub2/commit/?h=ubuntu/devel&id=9dadfd82504afa114b39e508e4580cb0212468ea


then it's been changed in bionic as:
'''
commit db84c3cc6faa4750d12c451f7a0c20560d0893bd
Author: Mathieu Trudel-Lapierre 
Date:   Fri Feb 9 16:30:45 2018 -0500

Add configure option to use vt.handoff=1
'''
https://git.launchpad.net/~hugh712/ubuntu/+source/grub2/commit/?h=bionic&id=c9b225dd94935e17dc8196dcaea524d4897bef4d

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1786013] Autopkgtest regression report (linux-gcp-5.4/5.4.0-1021.21~18.04.1)

2020-07-13 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-gcp-5.4 (5.4.0-1021.21~18.04.1) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/0.7.5-1ubuntu16.9 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-gcp-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786013

Title:
  Packaging resync

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885757] Autopkgtest regression report (linux-gcp-5.4/5.4.0-1021.21~18.04.1)

2020-07-13 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-gcp-5.4 (5.4.0-1021.21~18.04.1) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/0.7.5-1ubuntu16.9 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-gcp-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885757

Title:
  seccomp_bpf fails on powerpc

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884159] Autopkgtest regression report (linux-gcp-5.4/5.4.0-1021.21~18.04.1)

2020-07-13 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-gcp-5.4 (5.4.0-1021.21~18.04.1) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/0.7.5-1ubuntu16.9 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-gcp-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884159

Title:
  Update lockdown patches

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1826848] Autopkgtest regression report (linux-gcp-5.4/5.4.0-1021.21~18.04.1)

2020-07-13 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-gcp-5.4 (5.4.0-1021.21~18.04.1) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/0.7.5-1ubuntu16.9 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-gcp-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826848

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3
  / 5.4 kernel

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881137] Autopkgtest regression report (linux-gcp-5.4/5.4.0-1021.21~18.04.1)

2020-07-13 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-gcp-5.4 (5.4.0-1021.21~18.04.1) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/0.7.5-1ubuntu16.9 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-gcp-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881137

Title:
  Introduce the new NVIDIA 418-server and 440-server series, and update
  the current NVIDIA drivers

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886668] Autopkgtest regression report (linux-gcp-5.4/5.4.0-1021.21~18.04.1)

2020-07-13 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-gcp-5.4 (5.4.0-1021.21~18.04.1) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/0.7.5-1ubuntu16.9 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-gcp-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886668

Title:
  linux 4.15.0-109-generic network DoS regression vs -108

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887459] Re: clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

2020-07-13 Thread Po-Hsu Lin
This issue can be reproduced on 4.4.0-185-generic s390x

** Tags added: kqa-blocker sru-20200629 ubuntu-ltp-syscalls

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887459

Title:
  clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886247] Re: Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found

2020-07-13 Thread You-Sheng Yang
Verified 5.6.0-1020-oem:

  $ modinfo 
./lib/modules/5.6.0-1020-oem/kernel/drivers/net/wireless/realtek/rtw88/rtwpci.ko
 | grep ^alias:
  alias:  pci:v10ECdD723sv*sd*bc*sc*i*
  alias:  pci:v10ECdC82Fsv*sd*bc*sc*i*
  alias:  pci:v10ECdC822sv*sd*bc*sc*i*
  alias:  pci:v10ECdB822sv*sd*bc*sc*i*

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886247

Title:
  Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887393] Re: The system-lock-screen icon has a twisted/deformed path

2020-07-13 Thread Bug Watch Updater
** Changed in: yaru
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887393

Title:
  The system-lock-screen icon has a twisted/deformed path

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887389] Re: Microphone icon outlines can look fuzzy on certain screens

2020-07-13 Thread Bug Watch Updater
** Changed in: yaru
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887389

Title:
  Microphone icon outlines can look fuzzy on certain screens

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887464] [NEW] package phpmyadmin (not installed) failed to install/upgrade: installed phpmyadmin package post-installation script subprocess returned error exit status 1

2020-07-13 Thread Swagoto Sadhukhan
Public bug reported:

at the time  of install pgpmyadmin  it gaet the error

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: phpmyadmin (not installed)
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jul 14 07:59:38 2020
ErrorMessage: installed phpmyadmin package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2020-05-29 (45 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: phpmyadmin
Title: package phpmyadmin (not installed) failed to install/upgrade: installed 
phpmyadmin package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887464

Title:
  package phpmyadmin (not installed) failed to install/upgrade:
  installed phpmyadmin package post-installation script subprocess
  returned error exit status 1

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887419] Re: Lollypop music player mixes Yaru and Adwaita symbols

2020-07-13 Thread Bug Watch Updater
** Changed in: yaru
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887419

Title:
  Lollypop music player mixes Yaru and Adwaita symbols

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887420] Re: network-cellular-connected-symbolic isn't monochrome

2020-07-13 Thread Bug Watch Updater
** Changed in: yaru
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887420

Title:
  network-cellular-connected-symbolic isn't monochrome

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887459] Re: clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

2020-07-13 Thread Po-Hsu Lin
** Description changed:

  Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other 
arches)
  And B/E/F s390x as well.
  
  <<>>
  tag=clock_gettime04 stime=1594692118
  cmdline="clock_gettime04"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
  tst_test.c:1292: BROK: Test killed by SIGFPE!
  
  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>
  
  Error message can be found in syslog:
   report_user_fault: 159 callbacks suppressed
   User process fault: interruption code 0009 ilc:2 in 
clock_gettime04[113b0+22000]
   CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P   O
4.4.0-186-generic #216-Ubuntu
   task: 0007aa6de348 ti: 0007ada34000 task.ti: 0007ada34000
   User PSW : 070510018000 000113b18878
  R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:1 PM:0 EA:3
   User GPRS:  0b0cd725 000113b1d026 
000113b1d00e
   0b0cd725 000113b19bc4 
03ffe687e770
  000113b28f38 03ff941fe128 000113b28ec8 
075fcbb9
  03ff941a5000 000113b1d098 000113b1843e 
03ffe687e1f8
   User Code: 000113b1886a: e300a0380016  llgf%r0,56(%r10)
     000113b18870: a749   lghi%r4,0
    #000113b18874: b9870040   dlgr%r4,%r0
    >000113b18878: c0508328   larl%r5,113b28ec8
     000113b1887e: eb140002000d   sllg%r1,%r4,2
     000113b18884: e3119012   lt  %r1,0(%r1,%r9)
     000113b1888a: a784009a   brc 8,113b189be
     000113b1888e: e3405044   lg  %r4,64(%r5)
   Last Breaking-Event-Address:
    [<000113b18860>] 0x113b18860
  
- Kernel tainted flag:
+ Kernel tainted flag is 4097 after a clean boot, it won't be changed after the 
test:
  $ cat /proc/sys/kernel/tainted
  4097
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-186-generic 4.4.0-186.216
  ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228
  Uname: Linux 4.4.0-186-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon Jul 13 22:02:08 2020
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
  
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-186-generic N/A
   linux-backports-modules-4.4.0-186-generic  N/A
   linux-firmware 1.157.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887459

Title:
  clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887461] [NEW] nvidia-430 amd64 430.64=0ubuntu0~gpu14.04.1 broke xwindows on Ubuntu 14.04

2020-07-13 Thread Ross Campbell
Public bug reported:

when I did apt-get update && apt-get dist-upgrade, I saw that nvidia-430
package had the version 64 update that was just released a few days ago.

After installing it, my system wouldn't boot to xwindows.
Failsafe boot to gui wouldn't work either

The error messages looked similar to this bug report for nvidia drivers:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053

Here's what my xorg.[0,failsafe].log showed:

[43.645] (++) Log file: "/var/log/Xorg.failsafe.log", Time: Mon Jul 13 
18:41:16 2020
[43.645] (++) Using config file: "/etc/X11/xorg.conf.failsafe"
[43.645] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[43.645] Parse error on line 7 of section OutputClass in file 
/usr/share/X11/xorg.conf.d/nvidia-drm-outputclass.conf
"OutputClass" is not a valid section name.
[43.645] (EE) Problem parsing the config file
[43.645] (EE) Error parsing the config file
[43.645] (EE)
Fatal server error:
[43.645] (EE) no screens found(EE)


I have a *directory* named what the file is looking for (at least now after I 
downgraded nvidia...)

here is the contents:

/usr/share/X11/xorg.conf.d/50-nvidia-drm-outputclass.conf# cat 
nvidia-drm-outputclass.conf
# This xorg.conf.d configuration snippet configures the X server to
# automatically load the nvidia X driver when it detects a device driven by the
# nvidia-drm.ko kernel module.  Please note that this only works on Linux 
kernels
# version 3.9 or higher with CONFIG_DRM enabled, and only if the nvidia-drm.ko
# kernel module is loaded before the X server is started.

Section "OutputClass"
Identifier "nvidia"
MatchDriver"nvidia-drm"
Driver "nvidia"
EndSection


basically, in the progress of filing this bug report, I downgraded to 
nvidia-418 and my system was about to boot again.

To me, that says that nvidia-430.64 at least on Ubuntu 14.04 has a
regression

** Affects: nvidia-graphics-drivers-384 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887461

Title:
  nvidia-430 amd64 430.64=0ubuntu0~gpu14.04.1 broke xwindows on Ubuntu
  14.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887459] Status changed to Confirmed

2020-07-13 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887459

Title:
  clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887459] Re: clock_gettime04 from ubuntu_ltp_syscalls failed on X s390x

2020-07-13 Thread Po-Hsu Lin
** Description changed:

  Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on
  other arches)
  
  <<>>
  tag=clock_gettime04 stime=1594692118
  cmdline="clock_gettime04"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
  tst_test.c:1292: BROK: Test killed by SIGFPE!
  
  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>
  
  Error message can be found in syslog:
-  report_user_fault: 159 callbacks suppressed 
-  User process fault: interruption code 0009 ilc:2 in 
clock_gettime04[113b0+22000]
-  CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P   O
4.4.0-186-generic #216-Ubuntu
-  task: 0007aa6de348 ti: 0007ada34000 task.ti: 0007ada34000
-  User PSW : 070510018000 000113b18878
- R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:1 PM:0 EA:3
-  User GPRS:  0b0cd725 000113b1d026 
000113b1d00e
-  0b0cd725 000113b19bc4 
03ffe687e770
- 000113b28f38 03ff941fe128 000113b28ec8 
075fcbb9
- 03ff941a5000 000113b1d098 000113b1843e 
03ffe687e1f8
-  User Code: 000113b1886a: e300a0380016  llgf%r0,56(%r10)
-000113b18870: a749   lghi%r4,0
-   #000113b18874: b9870040   dlgr%r4,%r0
-   >000113b18878: c0508328   larl%r5,113b28ec8
-000113b1887e: eb140002000d   sllg%r1,%r4,2
-000113b18884: e3119012   lt  %r1,0(%r1,%r9)
-000113b1888a: a784009a   brc 8,113b189be
-000113b1888e: e3405044   lg  %r4,64(%r5)
-  Last Breaking-Event-Address:
-   [<000113b18860>] 0x113b18860
+  report_user_fault: 159 callbacks suppressed
+  User process fault: interruption code 0009 ilc:2 in 
clock_gettime04[113b0+22000]
+  CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P   O
4.4.0-186-generic #216-Ubuntu
+  task: 0007aa6de348 ti: 0007ada34000 task.ti: 0007ada34000
+  User PSW : 070510018000 000113b18878
+ R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:1 PM:0 EA:3
+  User GPRS:  0b0cd725 000113b1d026 
000113b1d00e
+  0b0cd725 000113b19bc4 
03ffe687e770
+ 000113b28f38 03ff941fe128 000113b28ec8 
075fcbb9
+ 03ff941a5000 000113b1d098 000113b1843e 
03ffe687e1f8
+  User Code: 000113b1886a: e300a0380016  llgf%r0,56(%r10)
+    000113b18870: a749   lghi%r4,0
+   #000113b18874: b9870040   dlgr%r4,%r0
+   >000113b18878: c0508328   larl%r5,113b28ec8
+    000113b1887e: eb140002000d   sllg%r1,%r4,2
+    000113b18884: e3119012   lt  %r1,0(%r1,%r9)
+    000113b1888a: a784009a   brc 8,113b189be
+    000113b1888e: e3405044   lg  %r4,64(%r5)
+  Last Breaking-Event-Address:
+   [<000113b18860>] 0x113b18860
+ 
+ Kernel tainted flag:
+ $ cat /proc/sys/kernel/tainted 
+ 4097
  
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-186-generic 4.4.0-186.216
  ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228
  Uname: Linux 4.4.0-186-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon Jul 13 22:02:08 2020
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
  
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-186-generic N/A
   linux-backports-modules-4.4.0-186-generic  N/A
   linux-firmware 1.157.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

** Description chang

[Bug 1887459] [NEW] clock_gettime04 from ubuntu_ltp_syscalls failed on X s390x

2020-07-13 Thread Po-Hsu Lin
Public bug reported:

Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on
other arches)

<<>>
tag=clock_gettime04 stime=1594692118
cmdline="clock_gettime04"
contacts=""
analysis=exit
<<>>
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
tst_test.c:1292: BROK: Test killed by SIGFPE!

Summary:
passed   0
failed   0
skipped  0
warnings 0
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=2 corefile=no
cutime=0 cstime=0
<<>>

Error message can be found in syslog:
 report_user_fault: 159 callbacks suppressed
 User process fault: interruption code 0009 ilc:2 in 
clock_gettime04[113b0+22000]
 CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P   O
4.4.0-186-generic #216-Ubuntu
 task: 0007aa6de348 ti: 0007ada34000 task.ti: 0007ada34000
 User PSW : 070510018000 000113b18878
R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:1 PM:0 EA:3
 User GPRS:  0b0cd725 000113b1d026 000113b1d00e
 0b0cd725 000113b19bc4 03ffe687e770
000113b28f38 03ff941fe128 000113b28ec8 075fcbb9
03ff941a5000 000113b1d098 000113b1843e 03ffe687e1f8
 User Code: 000113b1886a: e300a0380016  llgf%r0,56(%r10)
   000113b18870: a749   lghi%r4,0
  #000113b18874: b9870040   dlgr%r4,%r0
  >000113b18878: c0508328   larl%r5,113b28ec8
   000113b1887e: eb140002000d   sllg%r1,%r4,2
   000113b18884: e3119012   lt  %r1,0(%r1,%r9)
   000113b1888a: a784009a   brc 8,113b189be
   000113b1888e: e3405044   lg  %r4,64(%r5)
 Last Breaking-Event-Address:
  [<000113b18860>] 0x113b18860

Kernel tainted flag:
$ cat /proc/sys/kernel/tainted 
4097


ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-186-generic 4.4.0-186.216
ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228
Uname: Linux 4.4.0-186-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.23
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Date: Mon Jul 13 22:02:08 2020
HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:

ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-186-generic N/A
 linux-backports-modules-4.4.0-186-generic  N/A
 linux-firmware 1.157.23
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: New


** Tags: apport-bug package-from-proposed s390x third-party-packages xenial

** Description changed:

  Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on
  other arches)
  
  <<>>
  tag=clock_gettime04 stime=1594692118
  cmdline="clock_gettime04"
  contacts=""
  analysis=exit
  <<>>
  tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
  tst_test.c:1292: BROK: Test killed by SIGFPE!
  
  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>
  
+ Error message can be found in syslog:
+  report_user_fault: 159 callbacks suppressed 
+  User process fault: interruption code 0009 ilc:2 in 
clock_gettime04[113b0+22000]
+  CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P   O
4.4.0-186-generic #216-Ubuntu
+  task: 0007aa6de348 ti: 0007ada34000 task.ti: 0007ada34000
+  User PSW : 070510018000 000113b18878
+ R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:1 PM:0 EA:3
+  User GPRS:  0b0cd725 000113b1d026 
000113b1d00e
+  0b0cd725 000113b19bc4 
03ffe687e770
+ 000113b28f38 03ff941fe128 000113b28ec8 
075fcbb9
+ 03ff941a5000 000113b1d098 000113b1843e 
03ffe687e1f8
+  User Code: 000113b1886a

[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-07-13 Thread cynicalsomething
I have the same experience as ridiekel. Fixes the issue reported, but
performance takes a huge hit with a choppy mouse.

RTX 2070 Super
Driver 440.100
L Monitor: 1080
C Monitor: 4k
R Monitor: 4k

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870736

Title:
  [nvidia] Screen scaling 125% gives 200%

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887404] Re: the information was send by the system

2020-07-13 Thread Daniel van Vugt
Please explain what kind of problem you are having.

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887404

Title:
  the information was send by the system

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887411] Re: system-users-symbolic icon has unclear visual metaphor

2020-07-13 Thread Daniel van Vugt
** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887411

Title:
  system-users-symbolic icon has unclear visual metaphor

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887420] Re: network-cellular-connected-symbolic isn't monochrome

2020-07-13 Thread Daniel van Vugt
** Bug watch added: github.com/ubuntu/yaru/issues #2192
   https://github.com/ubuntu/yaru/issues/2192

** Also affects: yaru via
   https://github.com/ubuntu/yaru/issues/2192
   Importance: Unknown
   Status: Unknown

** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Low

** Changed in: yaru-theme (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887420

Title:
  network-cellular-connected-symbolic isn't monochrome

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877023] Re: Unhandled exception in check_ignored()

2020-07-13 Thread Seth Arnold
Hello, please use CVE-2020-15701 for this issue. Thanks

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-15701

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877023

Title:
  Unhandled exception in check_ignored()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887419] Re: Lollypop music player mixes Yaru and Adwaita symbols

2020-07-13 Thread Daniel van Vugt
** Bug watch added: github.com/ubuntu/yaru/issues #2208
   https://github.com/ubuntu/yaru/issues/2208

** Also affects: yaru via
   https://github.com/ubuntu/yaru/issues/2208
   Importance: Unknown
   Status: Unknown

** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Low

** Changed in: yaru-theme (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887419

Title:
  Lollypop music player mixes Yaru and Adwaita symbols

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887393] Re: The system-lock-screen icon has a twisted/deformed path

2020-07-13 Thread Daniel van Vugt
** Bug watch added: github.com/ubuntu/yaru/issues #2201
   https://github.com/ubuntu/yaru/issues/2201

** Also affects: yaru via
   https://github.com/ubuntu/yaru/issues/2201
   Importance: Unknown
   Status: Unknown

** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Low

** Changed in: yaru-theme (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887393

Title:
  The system-lock-screen icon has a twisted/deformed path

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887389] Re: Microphone icon outlines can look fuzzy on certain screens

2020-07-13 Thread Daniel van Vugt
** Bug watch added: github.com/ubuntu/yaru/issues #2185
   https://github.com/ubuntu/yaru/issues/2185

** Also affects: yaru via
   https://github.com/ubuntu/yaru/issues/2185
   Importance: Unknown
   Status: Unknown

** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Low

** Changed in: yaru-theme (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887389

Title:
  Microphone icon outlines can look fuzzy on certain screens

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887356] Re: System crashes while loading an application in cisco webex meeting

2020-07-13 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887356

Title:
  System crashes while loading an application in cisco webex meeting

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887455] Re: Trying to install as VM. Crashes in the middle of Location

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

This package failure looks like it was caused by bad ISO download,
corrupted install media, or device failure. eg. look in the logs and
you'll see messages like these :-

Jul 14 01:34:05 ubuntu kernel: [  284.520787] SQUASHFS error: zlib 
decompression failed, data probably corrupt
Jul 14 01:34:05 ubuntu kernel: [  284.520791] SQUASHFS error: 
squashfs_read_data failed to read block 0x18427661
Jul 14 01:34:05 ubuntu kernel: [  284.521949] SQUASHFS error: zlib 
decompression failed, data probably corrupt

Examining the information you have given us, this does not appear to be
a useful bug report so I am closing it, as it appears to be a bad ISO or
faulty device (inc. bad write-to-device). If you believe I'm in error,
please leave a comment explaining why and change the status back to
'New'. I suggest you verify your ISO download, and use the 'check disc
for defects' option to validate your media before install to ensure a
good download & write.

Possibly useful : https://tutorials.ubuntu.com/tutorial/tutorial-how-to-
verify-ubuntu#0 and
https://help.ubuntu.com/community/Installation/CDIntegrityCheck  (where
CD refers to your install media, be it CD, DVD, HDD, SSD, thumb-drive
etc)

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887455

Title:
  Trying to install as VM. Crashes in the middle of Location

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887296] Re: Moving popup windows drags the application's main window behind it

2020-07-13 Thread Daniel van Vugt
We do not consider Gnome's defaults in this area unreasonable. In the
years the feature has existed there have been practically no complaints
about it. So that's why this bug is marked 'Won't Fix'. We could also
use the status value of 'Opinion'.

Indeed you don't need to install an additional package, you can just
run:

  gsettings set org.gnome.mutter attach-modal-dialogs false

I agree such a setting should be easier to access. That would be an
enhancement for Settings (gnome-control-center).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887296

Title:
  Moving popup windows drags the application's main window behind it

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868520] Re: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2

2020-07-13 Thread Daniel van Vugt
Note that bionic was never affected by this bug. Although it did lack
the code change that fixed it :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868520

Title:
  Wayland apps fail to run with zwp_linux_dmabuf error (failed to import
  supplied dmabufs: Unsupported buffer format 808669784
  [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010])

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887446] Re: Area of desktop behind the Launcher is filled with random noise

2020-07-13 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1855757 ***
https://bugs.launchpad.net/bugs/1855757

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


** This bug has been marked a duplicate of bug 1855757
   [nvidia] Background image corrupted after standby or resume from suspend

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887446

Title:
  Area of desktop behind the Launcher is filled with random noise

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887455] [NEW] Trying to install as VM. Crashes in the middle of Location

2020-07-13 Thread Lydia C
Public bug reported:

Trying to install as VM. Crashes in the middle of Location

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.4
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CasperVersion: 1.376.2
Date: Mon Jul 13 20:34:18 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubiquity-2.21.63.4 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887455

Title:
  Trying to install as VM. Crashes in the middle of Location

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)

2020-07-13 Thread Hui Wang
OK, thx. I will SRU the patches in the testing kernel first.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886341

Title:
  Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal
  audio devices to fail to load w/o unacceptable workaround (Lenovo
  IdeaPad 5 15IIL05)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887451] Re: Volume up/down key sound should not be affected by system sounds volume

2020-07-13 Thread teo1978
** Description changed:

  It's unbelievable the level of OBVIOUS idiocy that I see myself forced
  to report.
  
  This one is absolutely demential.
  
  When you hit the volume +/- keys to turn the volume up and down, a short
  sound plays so you can get an idea of how loud you are setting the
  volume (and also you get confirmation that it works). I love that. Let's
  leave aside the fact that you should be able to turn this feature on or
  off individually if you wanted to without turning off ALL system sounds,
  but I don't care about that because I do want this feature.
  
  Now, OBVIOUSLY, the maximum volume of these sounds should be fixed, and
  the final volume at which they play should be multiplied only by the
  current output volume, and NOT also by the system sounds volume that you
  set in Settings => Sound => System sounds.
  
  For example, I have reduced the System Sounds volume a lot because the
  "thud" sound that plays (for example) when you hit the tab key in a
  terminal is ridiculously loud.
  
  However, because of this idiocy, the two are linked, so now, when I use
  the volume keys to set the overall output volume, the testing volume
- sounds are super dim because they are affected by the System Sounds
+ sounds are super quiet because they are affected by the System Sounds
  volume.
  
  They are meant to allow you to test the overall global output volume, so
  their scale must always be 100%. You should be able to turn them on and
  off, and it would be nice to have an individual volume for them alone,
  but to have them linked to the general System Sounds volume is just
  idiotic.
  
  Guys I'm getting tired of reporting bugs that are painfully idiotic
  design decisions. I cannot believe the people taking design decisions in
  Gnome and/or Ubuntu are so fucking clueless.
  
  This is pathetic. For fuck's sake.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 14 01:58:49 2020
  InstallationDate: Installed on 2013-10-11 (2467 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to focal on 2020-07-12 (1 days ago)

** Description changed:

  It's unbelievable the level of OBVIOUS idiocy that I see myself forced
  to report.
  
  This one is absolutely demential.
  
  When you hit the volume +/- keys to turn the volume up and down, a short
  sound plays so you can get an idea of how loud you are setting the
  volume (and also you get confirmation that it works). I love that. Let's
  leave aside the fact that you should be able to turn this feature on or
  off individually if you wanted to without turning off ALL system sounds,
  but I don't care about that because I do want this feature.
  
  Now, OBVIOUSLY, the maximum volume of these sounds should be fixed, and
  the final volume at which they play should be multiplied only by the
  current output volume, and NOT also by the system sounds volume that you
  set in Settings => Sound => System sounds.
  
  For example, I have reduced the System Sounds volume a lot because the
  "thud" sound that plays (for example) when you hit the tab key in a
  terminal is ridiculously loud.
  
  However, because of this idiocy, the two are linked, so now, when I use
  the volume keys to set the overall output volume, the testing volume
  sounds are super quiet because they are affected by the System Sounds
  volume.
  
  They are meant to allow you to test the overall global output volume, so
  their scale must always be 100%. You should be able to turn them on and
- off, and it would be nice to have an individual volume for them alone,
- but to have them linked to the general System Sounds volume is just
- idiotic.
+ off, and it would be nice to have a separate volume for them (and to
+ choose the sound sample, too), but to have them linked to the general
+ System Sounds volume is just idiotic.
  
  Guys I'm getting tired of reporting bugs that are painfully idiotic
  design decisions. I cannot believe the people taking design decisions in
  Gnome and/or Ubuntu are so fucking clueless.
  
  This is pathetic. For fuck's sake.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 14 01:58:49 2020
  InstallationDate: Installed on 2013-10-11 (2467 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: meta-gnome3
  UpgradeStatus

[Bug 1882623] Re: VM enter into hung status after triggering a crash

2020-07-13 Thread lilideng
Last time I did verification against gallery image, the default kernel version 
is 4.4.0-148-generic.
And I tried below kernel, found the kernel linux-image-4.15.0-1042-azure is the 
first one which we hit this bug, it is not specific for the esm kernel.

#   Kernel Version/Package  Result
0   Default kernel 4.4.0-148-generic => Good
1   linux-image-4.15.0-1023-azure => Good
2   linux-image-4.15.0-1030-azure   
3   linux-image-4.15.0-1031-azure   
4   linux-image-4.15.0-1032-azure   
5   linux-image-4.15.0-1035-azure   
6   linux-image-4.15.0-1036-azure => Good 
7   linux-image-4.15.0-1037-azure   
8   linux-image-4.15.0-1039-azure   
9   linux-image-4.15.0-1040-azure => Good
10  linux-image-4.15.0-1041-azure => Good
11  linux-image-4.15.0-1042-azure => Bad
12  linux-image-4.15.0-1045-azure => Bad

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882623

Title:
  VM enter into hung status after triggering a crash

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887451] [NEW] Volume up/down key sound should not be affected by system sounds volume

2020-07-13 Thread teo1978
Public bug reported:

It's unbelievable the level of OBVIOUS idiocy that I see myself forced
to report.

This one is absolutely demential.

When you hit the volume +/- keys to turn the volume up and down, a short
sound plays so you can get an idea of how loud you are setting the
volume (and also you get confirmation that it works). I love that. Let's
leave aside the fact that you should be able to turn this feature on or
off individually if you wanted to without turning off ALL system sounds,
but I don't care about that because I do want this feature.

Now, OBVIOUSLY, the maximum volume of these sounds should be fixed, and
the final volume at which they play should be multiplied only by the
current output volume, and NOT also by the system sounds volume that you
set in Settings => Sound => System sounds.

For example, I have reduced the System Sounds volume a lot because the
"thud" sound that plays (for example) when you hit the tab key in a
terminal is ridiculously loud.

However, because of this idiocy, the two are linked, so now, when I use
the volume keys to set the overall output volume, the testing volume
sounds are super dim because they are affected by the System Sounds
volume.

They are meant to allow you to test the overall global output volume, so
their scale must always be 100%. You should be able to turn them on and
off, and it would be nice to have an individual volume for them alone,
but to have them linked to the general System Sounds volume is just
idiotic.

Guys I'm getting tired of reporting bugs that are painfully idiotic
design decisions. I cannot believe the people taking design decisions in
Gnome and/or Ubuntu are so fucking clueless.

This is pathetic. For fuck's sake.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome (not installed)
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 14 01:58:49 2020
InstallationDate: Installed on 2013-10-11 (2467 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: meta-gnome3
UpgradeStatus: Upgraded to focal on 2020-07-12 (1 days ago)

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


** Tags: amd64 apport-bug focal

** Description changed:

  It's unbelievable the level of OBVIOUS idiocy that I see myself forced
  to report.
  
  This one is absolutely demential.
  
  When you hit the volume +/- keys to turn the volume up and down, a short
  sound plays so you can get an idea of how loud you are setting the
  volume (and also you get confirmation that it works). I love that. Let's
  leave aside the fact that you should be able to turn this feature on or
  off individually if you wanted to without turning off ALL system sounds,
  but I don't care about that because I do want this feature.
  
  Now, OBVIOUSLY, the maximum volume of these sounds should be fixed, and
  the final volume at which they play should be multiplied only by the
  current output volume, and NOT also by the system sounds volume that you
  set in Settings => Sound => System sounds.
  
  For example, I have reduced the System Sounds volume a lot because the
  "thud" sound that plays (for example) when you hit the tab key in a
  terminal is ridiculously loud.
  
  However, because of this idiocy, the two are linked, so now, when I use
  the volume keys to set the overall output volume, the testing volume
  sounds are super dim because they are affected by the System Sounds
  volume.
  
  They are meant to allow you to test the overall global output volume, so
  their scale must always be 100%. You should be able to turn them on and
  off, and it would be nice to have an individual volume for them alone,
  but to have them linked to the general System Sounds volume is just
  idiotic.
  
- 
  Guys I'm getting tired of reporting bugs that are painfully idiotic
- design decision. I cannot believe the people taking design decisions in
- Gnome are so fucking clueless.
+ design decisions. I cannot believe the people taking design decisions in
+ Gnome and/or Ubuntu are so fucking clueless.
  
  This is pathetic. For fuck's sake.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 14 01:58:49 2020
  InstallationDate: Installed on 2013-10-11 (2467 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to focal on 2020-07-12 (1 days ago)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub

[Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager

2020-07-13 Thread David W Craig
I will have to read up on this, and I am in a situation where I have to
rely on this as my only computer for a while.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882442

Title:
  Upgrade from 18.04 to 20.04 deactivates internal monitor in display
  manager

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887449] [NEW] I'm forced to select my user from a list of one before I can type the password on login

2020-07-13 Thread teo1978
Public bug reported:

On Ubuntu 16.04, in order to log in, I only needed to type in my
password.

I seem to remember that there was a setting where you could choose,
whether to be asked to type username and password, or choose the
username from a list and enter the password, or have a given user pre-
selected and only type the password, which is my preferred way.

Since I upgraded to 20.04, when the login screen shows up, I first need
to click on my username, as if I was selecting it from a list where it's
the only one, and only then I can type the password.

It used to be: type the password. Now it is: one mouse click and then
type the password.

Regardless of whether or not I have only one user or more than one, I
should have the choice to make my login routine less painful by having a
given user be already selected by default (you can always go back one
step by clicking on the back arrow).


Thank you for actively working on making ubuntu worse at every major release.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome (not installed)
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 14 01:46:08 2020
InstallationDate: Installed on 2013-10-11 (2467 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: meta-gnome3
UpgradeStatus: Upgraded to focal on 2020-07-12 (1 days ago)

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887449

Title:
  I'm forced to select my user from a list of one before I can type the
  password on login

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887408] Re: [needs-packaging] google-osconfig-agent

2020-07-13 Thread Brian Murray
*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu.  As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have Wishlist importance.  Subsequently, I'm
setting this bug's status to Wishlist.

** Changed in: ubuntu
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887408

Title:
   [needs-packaging] google-osconfig-agent

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887446] Re: Area of desktop behind the Launcher is filled with random noise

2020-07-13 Thread teo1978
Actually, now that I've been able to restore the shortcut for showing
desktop (yeah, I could have minimized all the windows manually one by
one), I realize that MY ENTIRE FUCKING DESKTOP is filled with noise.


I attach a screenshot of the whole desktop (I blurred out the icons)

** Attachment added: "Screenshot from 2020-07-14 01-37-20.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1887446/+attachment/5392430/+files/Screenshot%20from%202020-07-14%2001-37-20.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887446

Title:
  Area of desktop behind the Launcher is filled with random noise

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1446565] Re: enhance manpage of ddclient with explanation of options

2020-07-13 Thread Bug Watch Updater
** Changed in: ddclient (Debian)
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446565

Title:
  enhance manpage of ddclient with explanation of options

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630661] Re: provide systemd unit for ddclient

2020-07-13 Thread Bug Watch Updater
** Changed in: ddclient (Debian)
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630661

Title:
  provide systemd unit for ddclient

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1446565] Re: enhance manpage of ddclient with explanation of options

2020-07-13 Thread Bug Watch Updater
** Changed in: ddclient
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446565

Title:
  enhance manpage of ddclient with explanation of options

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887446] [NEW] Area of desktop behind the Launcher is filled with random noise

2020-07-13 Thread teo1978
Public bug reported:

The screenshot speaks for itself.

Stuff like this used to happen occasionally up to 16.04, sually after
resuming from suspend, but normally the areas would get redrawn properly
sooner or later.

But since I upgraded to 20.04 I've seen display garbage like this a lot
more often, and this particular instance has been like this for hours
now.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 13 18:51:51 2020
DistUpgraded: 2020-07-12 20:55:12,554 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
DkmsStatus:
 nvidia-340, 340.108, 5.3.0-62-generic, x86_64: installed
 nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
 NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
InstallationDate: Installed on 2013-10-11 (2466 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Acer Aspire V3-571G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago)
dmi.bios.date: 10/15/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.07
dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
dmi.product.family: Type1Family
dmi.product.name: Aspire V3-571G
dmi.product.sku: Aspire V3-_0648_V2.07
dmi.product.version: V2.07
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Sun Jul 12 20:59:51 2020
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.8-2ubuntu2.1

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


** Tags: amd64 apport-bug focal third-party-packages ubuntu

** Attachment added: "Screenshot from 2020-07-13 18-51-36.png"
   
https://bugs.launchpad.net/bugs/1887446/+attachment/5392401/+files/Screenshot%20from%202020-07-13%2018-51-36.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887446

Title:
  Area of desktop behind the Launcher is filled with random noise

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887404]

2020-07-13 Thread darkakrog76
1AdvuJTbqaAJdNc2ur2vAddg66WzX19q1N

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887404

Title:
  the information was send by the system

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887445] [NEW] libnvidia-gl-440 does not specify exact dependencies on libnvidia-compute-440 or libnvidia-common-440

2020-07-13 Thread James Smith
Public bug reported:

Inspecting the package:


$ dpkg --info libnvidia-gl-440_440.100-0ubuntu0.18.04.1_amd64.deb
 new Debian package, version 2.0.
 size 62889184 bytes: control archive=2352 bytes.
 729 bytes,17 lines  control
1531 bytes,18 lines  md5sums
2554 bytes,   106 lines   *  preinst  #!/bin/sh
 461 bytes,12 lines  shlibs
  74 bytes, 2 lines  triggers
 Package: libnvidia-gl-440
 Source: nvidia-graphics-drivers-440
 Version: 440.100-0ubuntu0.18.04.1
 Architecture: amd64
 Maintainer: Ubuntu Core Developers 
 Installed-Size: 206436
 Depends: libnvidia-common-440, libc6 (>= 2.2.5), libgcc1 (>= 1:4.2), 
libnvidia-compute-440, libx11-6, libxext6
 Conflicts: libnvidia-gl
 Replaces: libnvidia-gl, nvidia-384 (<< 390.25), nvidia-390 (<< 390.25-0ubuntu1)
 Provides: libegl-vendor, libglx-vendor, libnvidia-gl
 Section: non-free/libs
 Priority: optional
 Multi-Arch: same
 Homepage: http://www.nvidia.com
 Description: NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
  This package provides the NVIDIA OpenGL/GLX/EGL/GLES libraries and the
  Vulkan ICD.


when attempting to pin libnvidia-gl-440 to version 440.59-0ubuntu0.18.04.1,
I discovered that version 440.100 gets installed for libnvidia-compute-440 and 
libnvidia-common-440. This causes applications to break, because NVRM expects 
exact matches between the kernel
driver version (440.59) and the libraries:


[  720.451125] NVRM: API mismatch: the client has the version 440.100, but
   NVRM: this kernel module has the version 440.59.  Please
   NVRM: make sure that this kernel module and all NVIDIA driver
   NVRM: components have the same version.


I've worked around this locally by looking up the dependencies of 
libnvidia-gl-440, and pinning those with exact-matches as well.

This could be resolved by specifying these dependencies inside the
package as exact matches.

** Affects: nvidia-graphics-drivers-440 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887445

Title:
  libnvidia-gl-440 does not specify exact dependencies on libnvidia-
  compute-440 or libnvidia-common-440

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876322] Re: kazam on Focal: No audio recorded

2020-07-13 Thread Jesse Glick
Upstream issue (incl. workaround) and patch:
https://github.com/hzbd/kazam/issues/39
https://github.com/hzbd/kazam/pull/40

** Bug watch added: github.com/hzbd/kazam/issues #39
   https://github.com/hzbd/kazam/issues/39

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876322

Title:
  kazam on Focal: No audio recorded

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

  1   2   3   4   5   >