date:20180519

** Bug watch added: Wine Bugzilla #7767
   https://bugs.winehq.org/show_bug.cgi?id=7767

** Changed in: wine
   Importance: Medium => Unknown

** Changed in: wine
   Status: Invalid => Unknown

** Changed in: wine
 Remote watch: Wine Bugzilla #8571 => Wine Bugzilla #7767

** Summary changed:

- rosetta stone won't install via WINE in Feisty
+ rosetta stone won't install via WINE

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

Title:
  rosetta stone won't install via WINE

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

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

[Bug 116080] Re: Incomplete uninstall of wine applications

this was apparently fixed upstream

** Changed in: wine (Ubuntu)
   Status: Triaged => 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/116080

Title:
  Incomplete uninstall of wine applications

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

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

[Bug 844582] Re: "Invalid argument" when trying to scan

** Changed in: gscan2pdf (Ubuntu)
   Status: Expired => Invalid

** Changed in: sane-backends (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: sane-backends (Ubuntu)
 Assignee: Rolf Leggewie (r0lf) => (unassigned)

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

Title:
  "Invalid argument" when trying to scan

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

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

[Bug 1644205] Re: Please backport wine 1.8.5-1ubuntu1 (universe) from yakkety to xenial

** Summary changed:

- Please backport wine 1.8.5-1ubuntu1 (universe) from yakkety
+ Please backport wine 1.8.5-1ubuntu1 (universe) from yakkety to xenial

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

Title:
  Please backport wine 1.8.5-1ubuntu1 (universe) from yakkety to xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/xenial-backports/+bug/1644205/+subscriptions

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

Re: [Bug 1706097] Re: gvfsd-mtp crashed with SIGSEGV

2018-05-19 Thread michael deer

I was running android marshmallow on a coolpad quattro 2. Ubuntu 17.10
wasn't allowing me to transfer media/ files to specific folders but i was
allowed to copy/ move stuff as long as just the device was the destination.
Im running 18.04 now and so far so good. I only have 4GB of ram but not
nearly as many freezes as 17.10. My new phone (Blu S1) runs android nougat
and i haven't had one connection error message yet, old or new phone.

On Sat, May 19, 2018 at 3:46 PM, K. Tibor <1706...@bugs.launchpad.net>
wrote:

> I've never seen this one fixed. There is a clean install of 18.04 here,
> I also have a new Android phone - tried to connect my phone using MTP
> today, and segfault happens everytime in libgvfsdaemon.so...
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1725871).
> https://bugs.launchpad.net/bugs/1706097
>
> Title:
>   gvfsd-mtp crashed with SIGSEGV
>
> Status in gvfs:
>   Unknown
> Status in gvfs package in Ubuntu:
>   Fix Released
> Status in gnome-shell package in Fedora:
>   Unknown
>
> Bug description:
>   I get this every day when I have connected my Android phone for
>   charging its battery.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 17.10
>   Package: gvfs-backends 1.32.1-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
>   Uname: Linux 4.11.0-10-generic x86_64
>   ApportVersion: 2.20.6-0ubuntu4
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: GNOME
>   Date: Mon Jul 24 11:29:55 2017
>   ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
>   InstallationDate: Installed on 2015-04-30 (816 days ago)
>   InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
>   ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6
> /org/gtk/gvfs/exec_spaw/8
>   ProcEnviron:
>LANG=en_US.UTF-8
>LANGUAGE=en_US
>PATH=(custom, user)
>SHELL=/bin/bash
>XDG_RUNTIME_DIR=
>   SegvAnalysis:
>Segfault happened at: 0x7fea768b6cc9:mov0x18(%rax),%rax
>PC (0x7fea768b6cc9) ok
>source "0x18(%rax)" (0x0018) not located in a known VMA region
> (needed readable region)!
>destination "%rax" ok
>   SegvReason: reading NULL VMA
>   Signal: 11
>   SourcePackage: gvfs
>   StacktraceTop:
>() at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
>() at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
>() at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
>() at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
>() at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
>   Title: gvfsd-mtp crashed with SIGSEGV
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare
> sudo wireshark
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gvfs/+bug/1706097/+subscriptions
>

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

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

[Bug 1628479] Re: Please backport wine-development 1.9.20-1ubuntu1 (universe) from yakkety to xenial

** Summary changed:

- Please backport wine-development 1.9.20-1ubuntu1 (universe) from yakkety
+ Please backport wine-development 1.9.20-1ubuntu1 (universe) from yakkety to 
xenial

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

Title:
  Please backport wine-development 1.9.20-1ubuntu1 (universe) from
  yakkety to xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/xenial-backports/+bug/1628479/+subscriptions

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

[Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

2018-05-19 Thread Hui Wang

@benste,

Please upload the log of "pactl list".  Let me take a look.

thx.

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

Title:
  The analogue audio does not work on the Dell USB Dock

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

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

[Bug 1765346] Re: [LENOVO 20C6CTO1WW] hibernate/resume failure

Daniel Nespoulous, please advise to all of the following:

1) To see if this still affects upstream, could you please test the
latest mainline kernel (now 4.17-rc5) and advise to the results?

Also, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

2) If reproducible in the latest upstream release, could you please
provide all the missing information from
https://wiki.ubuntu.com/DebuggingKernelHibernate ?

** Tags added: kernel-bug-exists-upstream-4.17-rc1 latest-bios-2.27

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

Title:
  [LENOVO 20C6CTO1WW] hibernate/resume failure

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

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

[Bug 1766067] Re: Dell XPS 9370 freezes at login screen/shortly after login with kernels after 4.15.0-13

Maximilian Federle, the next step is to fully reverse commit bisect from
kernel 4.16.3 to 4.17-rc1 in order to identify the last bad commit,
followed immediately by the first good one. Once this good commit has
been identified, it may be reviewed for backporting. Could you please do
this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions, or providing a commit
from a kernel version bisect is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of
bisecting.

It is most helpful that after the fix commit (not kernel version) has
been identified, you then mark this report Status Confirmed.

Thank you for your help.

** Tags removed: kernel-bug-exists-upstream
** Tags added: bios-outdated-1.3.2 kernel-fixed-upstream 
kernel-fixed-upstream-4.17-rc1 needs-reverse-bisect

** Tags added: regression-release

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

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

Title:
  Dell XPS 9370 freezes at login screen/shortly after login with kernels
  after 4.15.0-13

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

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

[Bug 1771615] Re: LibreOffice Apps do not appear in the panel taskbar

2018-05-19 Thread Scott Cowles Jacobs

Well, today was interesting...!

I brought up LO-W from the context menu of a document that I wished to
edit.

The day before, I had to do a hard shutdown (nouveau video-crashed) with
several LO-W windows open, so now LO_W put up the window where it shows
documents that need to be recovered.

When it finished recovery, all three recovered document windows were in
the panel taskbar, but I STILL needed alt-tab to be able to bring up the
window of the document that I originally planned to edit today, as it
was NOT in the taskbar!

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

Title:
  LibreOffice Apps do not appear in the panel taskbar

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

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

[Bug 1744775] Re: "Operation was cancelled" when trying to use Transparency Unit in Canon 9000F Mark II

2018-05-19 Thread A.

I have confirmed that this a user issue rather than a bug. I was able to
get the scanner to work if you properly perform the procedure and remove
the white background piece. It unlatches and can be removed.

** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/sane-backends/+question/669402

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

Title:
  "Operation was cancelled" when trying to use Transparency Unit in
  Canon 9000F Mark II

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

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

[Bug 1766006] Re: kworker taking 100% cpu one one single core

Anil Gobburi, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766006/comments/21
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

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

Title:
  kworker taking 100% cpu one one single core

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

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

[Bug 1771726] Re: After gsch2pcb, pcb fails to open the new pcb file

2018-05-19 Thread Chad Parker

Thanks Mitch.

Point 1 is sort of iffy. In general, it would be nice to support spaces
in filenames. Whether we like it or not, the computing world is moving
in a direction where it is expected that you can do this.

Point 2 is the real problem here, that gsch2pcb doesn't produce the
correct output as a result of there being a space in the footprint
filename. The bug is in the gsch2pcb.scm gnetlist backend... written in
scheme... Maybe I can get one of the gschem/gnetlist developers to fix
this.

Point 3 is a bug in pcb, that pcb provides no explanation as to why it
failed to load the file. Unfortunately, this may be a difficult bug to
fix as our parser is not easy to work with. I'll have to dig into this
at some point, but it's going to take a fair bit of time to work out.

Possible workarounds:
1. Forego putting the footprint into gschem, and then add the footprint 
manually in pcb using File > Load element data to paste-buffer and then 
renaming the element with the correct refdes. 

2. Create a copy of the offending footprint files, rename them without
spaces, label the parts with those footprint names in gschem, and then
point gsch2pcb at your local footprint library with the renamed parts.

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

Title:
  After gsch2pcb,  pcb fails to open the new pcb file

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

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

[Bug 1722379] Re: Touchpad not working after resume

2018-05-19 Thread Jarad Downing

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

This bug is affecting me (for the first time btw and I've run every
kernel from 4.4 up). I'm running 4.15.0-20-generic #21-Ubuntu SMP Tue
Apr 24 06:16:15 UTC 2018 on a Dell latitude e6520.

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

Title:
  Touchpad not working after resume

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

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

[Bug 1723799] Re: touchpad not working after resume on kernel 4.13

2018-05-19 Thread Jarad Downing

This bug has started affecting me on 4.15.0-20-generic #21-Ubuntu. Not
sure if it's been reported on that release, not sure how to report it on
the correct release.

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

Title:
  touchpad not working after resume on kernel 4.13

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

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

[Bug 1770412] Re: package wine-stable (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/bin/wine-stable', que também está no pacote wine 3.0-1

When are people going to stop installing random packages from random
places and then come back to launchpad to report a "bug"?  Closing as
PEBKAC.

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

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

Title:
  package wine-stable (not installed) failed to install/upgrade: a
  tentar sobre-escrever '/usr/bin/wine-stable', que também está no
  pacote wine 3.0-1

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

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

[Bug 1772214] Re: pcmanfm-qt segfaults after some tricks (Lubuntu Next 18.04 and dailybuild of 19.05.2018)

2018-05-19 Thread Alf Gaida

Anyways - one can consider all libfm-qt and pcmanfm-qt bugs for versions
< 0.13 not relevant for cosmic - libfm-qt and pcmanfm-qt got heavy
modifications for 0.13 so most of the 0.12.0 bugs are not relevant for
cosmic (massive parts of libfm-qt are rewritten in c++ and don't use the
old libfm stuff anymore). The interesting thing will be to catch bugs in
the new version and iron them out until 18.10

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

Title:
  pcmanfm-qt segfaults after some tricks (Lubuntu Next 18.04 and
  dailybuild of 19.05.2018)

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

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

[Bug 1772222] [NEW] dangling symlink in /etc/rsyslog.d breaks rsyslogd

2018-05-19 Thread Paul Collins

Public bug reported:

Since upgrading from artful to bionic, I noticed that /var/log/kern.log,
etc., were not being updated on my machine.

In comparing to another machine running a fresh install of bionic, I
discovered that this seems to be the culprit:

[agnew(etc)] ls -l /etc/rsyslog.d/99-conjure-up.conf 
lrwxrwxrwx 1 root root 45 Jun 14  2017 /etc/rsyslog.d/99-conjure-up.conf -> 
/usr/share/conjure-up/conjure-up-rsyslog.conf
[agnew(etc)] ls -l /usr/share/conjure-up/conjure-up-rsyslog.conf
ls: cannot access '/usr/share/conjure-up/conjure-up-rsyslog.conf': No such file 
or directory
[agnew(etc)] _

Before deletion:

[agnew(etc)] sudo lsof -n -p $(cat /run/rsyslogd.pid) | grep /var/log
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
  Output information may be incomplete.
[agnew(etc)] _

After deletion:

[agnew(etc)] sudo rm /etc/rsyslog.d/99-conjure-up.conf 
[agnew(etc)] sudo service rsyslog restart

[agnew(etc)] sudo lsof -n -p $(cat /run/rsyslogd.pid) | grep /var/log
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
  Output information may be incomplete.
rsyslogd 30686 syslog8w   REG  253,122782   15213384 
/var/log/syslog
rsyslogd 30686 syslog9w   REG  253,1 2065   15219687 
/var/log/auth.log
[agnew(etc)] _

It didn't occur to me to check the service status until writing this bug
report, but in fact it does report the problem on startup:

May 20 14:39:27 agnew rsyslogd[31786]: error during parsing file 
/etc/rsyslog.d/postfix.conf, on or before line 1: error accessing config file 
or directory '/etc/rsyslog.d/99-conjure
May 20 14:39:27 agnew rsyslogd[31786]: CONFIG ERROR: there are no active 
actions configured. Inputs will run, but no output whatsoever is created. 
[v8.32.0 try http://www.rsyslog.com

However, it's unlikely this warning will be discovered until it's too
late, if ever -- consider a remote syslogging setup on a machine that
has since been decommissioned or reinstalled -- and so it would probably
better for rsyslogd to cope with dangling symlinks.  Indeed, given the
age of the symlink, this is a regression from artful or earlier.

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

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

** Also affects: rsyslog (Ubuntu Bionic)
   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/177

Title:
  dangling symlink in /etc/rsyslog.d breaks rsyslogd

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

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

[Bug 1772214] Re: pcmanfm-qt segfaults after some tricks (Lubuntu Next 18.04 and dailybuild of 19.05.2018)

2018-05-19 Thread Alf Gaida

importance can be lowered - fixed in 0.13.0

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

Title:
  pcmanfm-qt segfaults after some tricks (Lubuntu Next 18.04 and
  dailybuild of 19.05.2018)

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

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

[Bug 1772225] [NEW] [regression] delayed window update in bionic

Public bug reported:

I recently reinstalled my laptop, going from i386 trusty to amd64
bionic. I kept using wine32 with an existing ~/.wine installation. I
make of use of http://arm.64hosts.com/ which starts in a non-maximized
window. The screen is not redrawn after maximizing until clicking in
the window or otherwise moving the mouse inside the window. This is a
regression over my previous experience.

** Affects: wine (Ubuntu)
Importance: Low
Status: New

** Tags: bionic regression-release

** Attachment added: "the window content is not refreshed after maximizing"

https://bugs.launchpad.net/bugs/1772225/+attachment/5141804/+files/window_not_redrawn_upon_resize.png

** Description changed:

I recently reinstalled my laptop, going from i386 trusty to amd64
bionic. I kept using wine32 with an existing ~/.wine installation. I
- make of http://arm.64hosts.com/ which starts in a non-maximized window.
- The screen is not redrawn after maximizing until clicking in the window
- or otherwise moving the mouse inside the window. This is a regression
- over my previous experience.
+ make of use of http://arm.64hosts.com/ which starts in a non-maximized
+ window. The screen is not redrawn after maximizing until clicking in
+ the window or otherwise moving the mouse inside the window. This is a
+ regression over my previous experience.

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

Title:
[regression] delayed window update in bionic

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

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

[Bug 1772224] [NEW] [regression] jagged fonts in bionic

Public bug reported:

I recently reinstalled my laptop, going from i386 trusty to amd64
bionic.  I kept using wine32 with an existing ~/.wine installation and
noticed that the fonts in an application I use (http://arm.64hosts.com/)
are not showing in the best quality.

** Affects: wine (Ubuntu)
 Importance: Low
 Status: New


** Tags: bionic regression-release

** Attachment added: "example of jagged fonts in the popup"
   
https://bugs.launchpad.net/bugs/1772224/+attachment/5141803/+files/jagged_fonts.png

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

Title:
  [regression] jagged fonts in bionic

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

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

[Bug 1529528] Re: Update the package to version 0.9.9

Updated in newer releases of ubuntu:

 "radare2" versions published in Ubuntu
Cosmic (2.4.0+dfsg-1): universe/devel
Bionic (2.3.0+dfsg-2): universe/devel
Artful (1.6.0+dfsg-1): universe/devel 

** Changed in: radare2 (Ubuntu)
   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/1529528

Title:
  Update the package to version 0.9.9

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

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

[Bug 1438014] Re: gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts

Reported to gnome's gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/180
Reference: GNOME/gtk#180

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

Title:
  gnome-terminal-server and mate-terminal crash when setting keyboard
  shortcuts

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

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

[Bug 1062412] Re: strace crashed with SIGSEGV in __GI_raise()

> Note that the CUPS version which I had run under strace had a segfault
bug, but this should not make strace crash.

Actually, there is a code in strace.c (main -> terminate() ) to raise the 
signal which killed the traced process. Strace does it exactly before exit
https://github.com/strace/strace/blob/1d98b287a4cb6901d369d78126d481508f9e35ef/strace.c#L2655

if (exit_code > 0xff) {
...
/* Child was killed by a signal, mimic that.  */
exit_code &= 0xff;
signal(exit_code, SIG_DFL);
...
raise(exit_code);
...
exit(exit_code);

Code was added in 2008-09-29 commit
https://github.com/strace/strace/commit/a68096576afc07e51d33b49c432d658b27a7f13c
> (main): Exit/kill ourself with straced child's exitcode/signal.

Same for other reports in
https://errors.ubuntu.com/?package=strace=year like Bug #1430741

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

Title:
  strace crashed with SIGSEGV in __GI_raise()

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

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

[Bug 1430741] Re: strace crashed with SIGABRT in __GI_raise()

Probably Spotify Linux Client process did crash with SIGABRT. strace
detects that child was killed with the signal and raises same signal for
itself just before exit (like in Bug #1062412)

There is a code in strace.c (main -> terminate() ) to raise the signal which 
killed the traced process. Strace does it exactly before exit
https://github.com/strace/strace/blob/1d98b287a4cb6901d369d78126d481508f9e35ef/strace.c#L2655

if (exit_code > 0xff) {
...
/* Child was killed by a signal, mimic that.  */
exit_code &= 0xff;
signal(exit_code, SIG_DFL);
...
raise(exit_code);
...
exit(exit_code);

Code was added in 2008-09-29 commit
https://github.com/strace/strace/commit/a68096576afc07e51d33b49c432d658b27a7f13c
> (main): Exit/kill ourself with straced child's exitcode/signal.

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

Title:
  strace crashed with SIGABRT in __GI_raise()

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

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

[Bug 1716409] Re: Unable to install flatpakref on Ubuntu artful

2018-05-19 Thread Ads20000

Strange, installing Flatpaks seems to work fine in 0.11.3-3 now (with
gnome-software 3.28.1-0ubuntu4.18.04.1 (the new version is a patch for
snaps from bionic-proposed, nothing to do with Flatpak I don't think)).
Glad that an Ubuntu dev is on it with keeping Flatpak up to date! :D

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

Title:
  Unable to install flatpakref on Ubuntu artful

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

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

[Bug 1767180] Re: Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work using the Realtek 8822BE driver

Bob, to confirm this is an upstream issue, could you please test the
latest mainline kernel available (4.17-rc5) and advise to the results?

Also, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

** Tags removed: kernel-bug-exists-upstream
** Tags added: apport-collected artful bionic kernel-bug-exists-upstream-4.16.6 
staging xenial

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

** Tags added: latest-bios-1301

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

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

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

[Bug 1767356] Re: Long boot time (approx 5 minuntes!), long shutdown

deeks9000, in order to allow additional upstream mainline kernel developers to 
examine the issue, at your earliest convenience, could you please test the 
latest mainline kernel available from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind 
the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the report 
description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest mainline kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** Tags added: bios-outdated-f.34 regression-update

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

** Tags added: artful

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

Title:
  Long boot time (approx 5 minuntes!), long shutdown

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

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

[Bug 1767360] Re: 16.04 LTS boot failure with linux-image-4.4.0-122-generic, linux-image-4.4.0-121-generic or linux-image-4.4.0-119-generic

Rod B., the next step is to fully reverse commit bisect from kernel 4.4
to 4.16 in order to identify the last bad commit, followed immediately
by the first good one. Once this good commit has been identified, it may
be reviewed for backporting. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions, or providing a commit
from a kernel version bisect is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of
bisecting.

It is most helpful that after the fix commit (not kernel version) has
been identified, you then mark this report Status Confirmed.

Thank you for your help.

** Description changed:

  I am reporting this using the most recent auto updated version of the
  kernel linux-image-4.4.0-122-generic. But boot also fails on the two
  previous auto updated images linux-image-4.4.0-121-generic and linux-
  image-4.4.0-119-generic.
  
  Last bootable kernel was linux-image-4.4.0-116-generic which is what I
  have to run to update and submit this report.
  
  The boot failures occur on two Asus S200E laptops. It does not effect my
  desktop.
  
- I can't seem to get any details about why boot is failing. It "blows up"
- and returns to BIOS warn start during or right after the ramdisk is
- loaded. It also does not matter if I select "recovery mode" kernel. I
- can boot my older kernels like 4.4.0-116-generic without a problem.
  
- Below is a link to a video of the failure. I boot the kernels in this
- order: 121, 119, 116.
- 
+ Below is a link to a video of the failure. I boot the kernels in this order: 
121, 119, 116.
  https://drive.google.com/file/d/1l_-aiRw-a5by9RkQzfDDQfHF5LbHygeZ/view
  
  I ran memory test on both laptops - no problems found.
  
  I removed options quite and splash in hopes it might show more info but
  it did not help.
  
  For what it is worth I used gunzip to test the integrity of the
  compressed initrd.img files. No errors from gunzip.
  
  The disk UUID and other options I can see from Grub edit ('e') are
  identical.
  
  Before 121 kernel update was release I uninstalled and reinstalled 119
  but that did not help. IE: sudo apt-get --purge remove linux-
  image-4.4.0-119-generic; sudo apt-get install linux-generic
  
- 
- $ lsb_release -rd
- 
- Description:  Ubuntu 16.04.4 LTS
- Release:  16.04
- 
- 
- $ cat /proc/version_signature
- 
- Ubuntu 4.4.0-116.140-generic 4.4.98  (but this is the version that boots
- so I can submit this report)
- 
- 
- $ sudo lspci -vnvn 
- 
- 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
-   Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
-   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
-   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
-   Kernel driver in use: ivb_uncore
- 
- 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller])
-   Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
-   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
-   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
-   Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
-   Address: fee0200c  Data: 41d1
-   Capabilities: [d0] Power Management version 2
-   Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
-   Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
-   Capabilities: [a4] PCI Advanced Features
-   AFCap: TP+ FLR+
-   AFCtrl: FLR-
-   AFStatus: TP-
-   Kernel driver in use: i915
-   Kernel modules: i915
- 
- 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI])
-   Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
-   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
-   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
-   PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
-   Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
-   DevCap: MaxPayload 128 bytes, PhantFunc 0
-   ExtTag- RBE+
-   DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
-   RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
-   MaxPayload 128 bytes, MaxReadReq 128 bytes
-   DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
-   LnkCap: Port

[Bug 1767452] Re: kernel oops when I undocked

Frew Schmidt, please address all of the following:

1) Could you please execute the following via a terminal to attach debugging 
logs:
apport-collect 1767452

2) The next step is to fully reverse commit bisect from kernel 4.16.6 to
4.17-rc3 in order to identify the last bad commit, followed immediately
by the first good one. Once this good commit has been identified, it may
be reviewed for backporting. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions, or providing a commit
from a kernel version bisect is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of
bisecting.

It is most helpful that after the fix commit (not kernel version) has
been identified, you then mark this report Status Confirmed.

Thank you for your help.

** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.17-rc3
needs-reverse-bisect

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

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

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

Title:
  kernel oops when I undocked

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

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

[Bug 1767603] Re: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel

Philip Taylor, please advise to all of the following:

1) While booted into default Ubuntu kernel 4.15 and having removed all 
WORKAROUNDs, could you please execute the following from a terminal to gather 
relevant debug logs:
apport-collect 1767603

2) The next step is to fully commit bisect from kernel 4.13 to 4.15 in
order to identify the last good kernel commit, followed immediately by
the first bad one. This will allow for a more expedited analysis of the
root cause of your issue. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions, or providing a commit
from a kernel version bisect is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of
bisecting.

It is most helpful that after the fix commit (not kernel version) has
been identified, you then mark this report Status Confirmed.

Thank you for your help.

** Tags removed: bug-exists-upstream
** Tags added: bionic kernel-bug-exists-upstream 
kernel-bug-exists-upstream-4.17-rc3 needs-bisect regression-release

** Description changed:

  I can confirm the following bug in kernel version 4.15 in bionic,
  
  https://bugzilla.kernel.org/show_bug.cgi?id=199035
  
- I have thus booted into 4.13, and temporarily worked around the bug. If
- you need any further information please tell me.
+ WORKAROUND: Boot into kernel 4.13.
+ 
+ WORKAROUND: Disable bluetooth in BIOS.

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

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

Title:
  BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14
  kernel

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

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

[Bug 1767611] Re: ath10k_pci crash leading to unstable wifi on 18.04

Mitch, please address all of the following:

1) To gather system debugging information, could you please execute the 
following via a terminal:
apport-collect 1767611

2) To clarify, this issue only happens after resuming from suspend (i.e.
after booting from a shutdown, performing subsequent power ups from
shutdown or restarts without suspending don't cause the issue)?

3) The next step is to fully commit bisect from kernel 4.13 to 4.15 in
order to identify the last good kernel commit, followed immediately by
the first bad one. This will allow for a more expedited analysis of the
root cause of your issue. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions, or providing a commit
from a kernel version bisect is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of
bisecting.

It is most helpful that after the fix commit (not kernel version) has
been identified, you then mark this report Status Confirmed.

Thank you for your help.

** Tags added: kernel-bug-exists-upstream-4.17-rc3 needs-bisect
regression-release

** Description changed:

  Ubuntu 18.04.
  mitch@mitch-YOGA:~$ uname -a
  Linux mitch-YOGA 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
- 
  
  Same laptop, device, working fine on 17.10. No crashes, stable wifi.
  
  Apr 28 12:11:09 mitch-YOGA kernel: [12303.503506] IPv6: 
ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
  Apr 28 12:12:04 mitch-YOGA kernel: [12359.164491] ath10k_pci :01:00.0: 
failed to set 5g txpower 20: -11
  Apr 28 12:12:04 mitch-YOGA kernel: [12359.164498] ath10k_pci :01:00.0: 
failed to setup tx power 20: -11
  Apr 28 12:12:04 mitch-YOGA kernel: [12359.164503] ath10k_pci :01:00.0: 
failed to recalc tx power: -11
  Apr 28 12:12:08 mitch-YOGA kernel: [12362.236455] ath10k_pci :01:00.0: 
failed to set inactivity time for vdev 0: -11
  Apr 28 12:12:08 mitch-YOGA kernel: [12362.236460] ath10k_pci :01:00.0: 
failed to setup powersave: -11
  Apr 28 12:12:08 mitch-YOGA kernel: [12362.236488] wlp1s0: deauthenticating 
from 54:a0:50:d8:ca:00 by local choice (Reason: 3=DEAUTH_LEAVING)
  Apr 28 12:12:11 mitch-YOGA kernel: [12365.308434] ath10k_pci :01:00.0: 
failed to set inactivity time for vdev 0: -11
  Apr 28 12:12:11 mitch-YOGA kernel: [12365.308441] ath10k_pci :01:00.0: 
failed to setup powersave: -11
  Apr 28 12:12:14 mitch-YOGA kernel: [12368.380355] ath10k_pci :01:00.0: 
failed to set PS Mode 0 for vdev 0: -11
  Apr 28 12:12:14 mitch-YOGA kernel: [12368.380360] ath10k_pci :01:00.0: 
failed to setup powersave: -11
  Apr 28 12:12:14 mitch-YOGA kernel: [12368.380366] ath10k_pci :01:00.0: 
failed to setup ps on vdev 0: -11
  Apr 28 12:12:19 mitch-YOGA kernel: [12373.500277] ath10k_pci :01:00.0: 
failed to flush transmit queue (skip 0 ar-state 1): 0
  Apr 28 12:12:22 mitch-YOGA kernel: [12376.572243] ath10k_pci :01:00.0: 
failed to install key for vdev 0 peer 54:a0:50:d8:ca:00: -11
  Apr 28 12:12:22 mitch-YOGA kernel: [12376.572251] wlp1s0: failed to remove 
key (0, 54:a0:50:d8:ca:00) from hardware (-11)
  Apr 28 12:12:25 mitch-YOGA kernel: [12379.644315] ath10k_pci :01:00.0: 
failed to delete peer 54:a0:50:d8:ca:00 for vdev 0: -11
  Apr 28 12:12:25 mitch-YOGA kernel: [12379.644328] ath10k_pci :01:00.0: 
found sta peer 54:a0:50:d8:ca:00 (ptr  id 133) entry on vdev 0 
after it was supposedly removed
  Apr 28 12:12:25 mitch-YOGA kernel: [12379.644457] WARNING: CPU: 0 PID: 757 at 
/build/linux-5s7Xkn/linux-4.15.0/net/mac80211/sta_info.c:1001 
__sta_info_destroy_part2+0x169/0x170 [mac80211]
  Apr 28 12:12:25 mitch-YOGA kernel: [12379.644460] Modules linked in: pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ccm arc4 bnep 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic btusb btrtl 
hid_sensor_accel_3d btbcm btintel bluetooth uvcvideo hid_sensor_als 
hid_sensor_trigger videobuf2_vmalloc industrialio_triggered_buffer kfifo_buf 
videobuf2_memops hid_sensor_iio_common videobuf2_v4l2 ecdh_generic industrialio 
videobuf2_core hid_sensor_custom videodev joydev media nls_iso8859_1 
hid_sensor_hub hid_multitouch snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core 
snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep ath10k_pci 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_pcm ath10k_core 
kvm_intel
  Apr 28 12:12:25 mitch-YOGA kernel: [12379.644566]  ath kvm mac80211 irqbypass 
snd_seq_midi crct10dif_pclmul snd_seq_midi_event crc32_pclmul cfg80211 
ghash_clmulni_intel snd_rawmidi pcbc snd_seq aesni_intel aes_x86_64 crypto_simd 
glue_helper cryptd intel_cstate intel_rapl_perf input_leds snd_seq_device 
snd_timer wmi_bmof serio_raw intel_wmi_thunderbolt snd idma64 virt_dma 
soundcore mei_me mei

[Bug 1767701] Re: amdgpu WQHD resolution not working

Jochen Schroeder, please respond to all of the following:

1) To capture relevant debugging logs, could you please undo the WORKAROUND, 
boot into a Ubuntu kernel (not upstream) and execute the following in a 
terminal:
apport-collect 1767701

2) The next step is to fully reverse commit bisect from kernel 4.15 to
4.16.5 in order to identify the last bad commit, followed immediately by
the first good one. Once this good commit has been identified, it may be
reviewed for backporting. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions, or providing a commit
from a kernel version bisect is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of
bisecting.

It is most helpful that after the fix commit (not kernel version) has
been identified, you then mark this report Status Confirmed.

Thank you for your help.

** Tags added: bionic kernel-fixed-upstream kernel-fixed-upstream-4.16.5
needs-reverse-bisect regression-release

** Description changed:

  After upgrade to bionic the highest detected resolution of my monitor
  was 1920x1200 instead of the 2560x1440 that it is capable of and that
  worked previously.
  
  My graphics card is a Radeon RX480 and this seems to be related to the
  AMDGPU DC changes in kernel 4.15.
  
- Passing amdgpu.dc=0 as boot parameter fixes the issue and the correct
- resolution is detected. This is also fixed on latest 4.16.5 upstream
- kernel from the kernel ppa, i.e. the maximum resolution is correctly
- detected without amdgpu.dc=0 as boot parameter.
+ This is also fixed on latest 4.16.5 upstream kernel from the kernel ppa,
+ i.e. the maximum resolution is correctly detected without amdgpu.dc=0 as
+ boot parameter.
  
  attached are the xorg files after booting the 4.15 and 4.16.5 kernels
  both without amdgpu.dc=0. The main difference seems to be the probed
  modes.
+ 
+ WORKAROUND: Pass kernel boot parameter:
+ amdgpu.dc=0

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

Title:
  amdgpu WQHD resolution not working

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

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

[Bug 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected

Sandy Patterson, please address all of the following:

1. Is this something that started to happen after an update? If so,
which and when precisely?

2. In order to allow additional upstream mainline kernel developers to examine 
the issue, at your earliest convenience, could you please test the latest 
mainline kernel available from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind 
the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the report 
description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest mainline kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** Tags added: bios-outdated-1.2.7

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

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

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

Title:
  Kernel crash when booting laptop with hdmi monitor connected

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

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

[Bug 1768191] Re: mate-dock-applet Does not respect 'skip-tasklist' from wmctrl or gdevilspie

2018-05-19 Thread Omadas

This bug was patched by the project owner on git-hub.  Marking as
Solved.

** Changed in: mate-dock-applet (Ubuntu)
   Status: New => Fix Committed

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

Title:
  mate-dock-applet Does not respect 'skip-tasklist' from wmctrl or
  gdevilspie

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-dock-applet/+bug/1768191/+subscriptions

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

[Bug 1768152] Re: Brightness controll doesn't work - Samsung R560

Thomas, the next step is to fully commit bisect from kernel 4.4 to 4.15
in order to identify the last good kernel commit, followed immediately
by the first bad one. This will allow for a more expedited analysis of
the root cause of your issue. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions, or providing a commit
from a kernel version bisect is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of
bisecting.

It is most helpful that after the fix commit (not kernel version) has
been identified, you then mark this report Status Confirmed.

Thank you for your help.

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

** Summary changed:

- Brightness controll doesn't work - Samsung R560
+ [Samsung NP-R560-AS05DE] Brightness control doesn't work

** Tags added: kernel-bug-exists-upstream-4.17-rc3 needs-bisect
regression-release

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

Title:
  [Samsung NP-R560-AS05DE] Brightness control doesn't work

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

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

[Bug 1772214] Re: pcmanfm-qt segfaults after some tricks (Lubuntu Next 18.04 and dailybuild of 19.05.2018)

2018-05-19 Thread Simon Quigley

I can confirm this.

Thanks for the report!

** Changed in: pcmanfm-qt (Ubuntu)
   Status: New => Confirmed

** Changed in: pcmanfm-qt (Ubuntu)
   Importance: Undecided => High

** Changed in: pcmanfm-qt (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

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

Title:
  pcmanfm-qt segfaults after some tricks (Lubuntu Next 18.04 and
  dailybuild of 19.05.2018)

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

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

[Bug 1768208] Re: OLED X1 yoga lenove, screen ubuntu, brightness issue

marvin, please address the all of the following:

1. When using 16.10, were you able to adjust the brightness via keyboard
key press, or you could only adjust the brightness via xrandr?

2. In order to allow additional upstream mainline kernel developers to examine 
the issue, at your earliest convenience, could you please test the latest 
mainline kernel available from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind 
the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the report 
description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest mainline kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** Tags added: bios-outdated-1.36 regression-potential

** Changed in: linux (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/1768208

Title:
  OLED X1 yoga lenove, screen ubuntu, brightness issue

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

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

[Bug 1772192] Re: Missing setting to disable touchpad

2018-05-19 Thread Pedro Côrte-Real

Found the issue. I had installed a shell extension for touchpad
disabling in 16.04 when I couldn't find a setting. Without that
extension I get a bunch of touchpad options indeed. Sorry for the false
alarm, and thanks for looking into it.

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

Title:
  Missing setting to disable touchpad

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

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

[Bug 1772192] Re: Missing setting to disable touchpad

2018-05-19 Thread Jeremy Bicha

This bug report is being closed due to your last comment regarding this
being fixed. For future reference you can manage the status of your own
bugs by clicking on the current status in the yellow line and then
choosing a new status in the revealed drop down box. You can learn more
about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you
again for taking the time to report this bug and helping to make Ubuntu
better. Please submit any future bugs you may find.

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

** Changed in: gnome-control-center (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/1772192

Title:
  Missing setting to disable touchpad

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

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

[Bug 1769331] Re: broken upgrade/ full install bionic from ubuntu-budgie 17.10

stre...@bluewin.ch, please respond to all of the following:

1) Could you please perform the following in Ubuntu 17.10 to gather information 
about your working setup via a terminal:
apport-collect 1769331

2) Could you please provide debugging logs from a live environment of
http://cdimage.ubuntu.com/daily-live/current/ following
https://help.ubuntu.com/community/DebuggingSystemCrash ?

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

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

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

Title:
  broken upgrade/ full install bionic from ubuntu-budgie 17.10

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

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

[Bug 1772192] Re: Missing setting to disable touchpad

2018-05-19 Thread Pedro Côrte-Real

No switch for me. Screenshot attached.

** Attachment added: "Screenshot of my settings screen"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1772192/+attachment/5141793/+files/MouseAndTouchpad.png

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

Title:
  Missing setting to disable touchpad

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

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

[Bug 1747752] Re: kaccessibility missing orca dependency

2018-05-19 Thread Bug Watch Updater

** Changed in: meta-kde (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/1747752

Title:
  kaccessibility missing orca dependency

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

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

[Bug 485745] Re: Evince presents PDF with mis-rendered Hebrew

** Package changed: evince (Ubuntu) => poppler (Ubuntu)

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

Title:
  Evince presents PDF with mis-rendered Hebrew

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

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

[Bug 1769013] Re: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main)

2018-05-19 Thread Omer Akram

Please backport this to Bionic. Java there is pretty much broken for my
use cases, installing ca-certificates-java from Cosmic fixed my issues.

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

Title:
  Please merge ca-certificates-java 20180413 (main) from Debian unstable
  (main)

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

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

[Bug 1772192] Re: Missing setting to disable touchpad

2018-05-19 Thread Jeremy Bicha

On my computer, I have a Touchpad On/Off switch in Settings > Devices >
Mouse & Touchpad. Could you check there?

If you don't have a switch there, could you take a screenshot of that
page?

** Changed in: gnome-control-center (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/1772192

Title:
  Missing setting to disable touchpad

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

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

[Bug 1772214] [NEW] pcmanfm-qt segfaults after some tricks (Lubuntu Next 18.04 and dailybuild of 19.05.2018)

2018-05-19 Thread Dima

Public bug reported:

1,2) Please see the apport attachment.
3) Steps to reproduce:
1. Open pcmanfm-qt.
2. Go to root dir /
3. Change the view of the dir to "Detailed list"
4. Open /etc dir with double click. If it opened in Icon View mode then step 
back and try to enter to /etc

4) pcmanfm-qt segfaults in my case. My current related dmesg output:
"
[   99.878774] pcmanfm-qt[1051]: segfault at 560d40011390 ip 560d40011390 
sp 7ffe107ca5d8 error 15
[  190.640536] pcmanfm-qt[1237]: segfault at 556c0b82dba0 ip 556c0b82dba0 
sp 7fffefd12e08 error 15
[ 1214.139394] pcmanfm-qt[1320]: segfault at 7f242900dda0 ip 7f2428e39cde 
sp 7ffc37114630 error 4 in libc-2.27.so[7f2428da2000+1e7000]
[ 1668.239954] pcmanfm-qt[3154]: segfault at 7fcb0f14f2b0 ip 7fcb0f14f2b0 
sp 7ffe60521188 error 15 in libc-2.27.so[7fcb0f14e000+2000]
"

The last two is after installing of apport. But it maybe unrelated.
I've tried it on Lubuntu Next daily-build of 19.05.2018. And the problem is 
existing on it.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pcmanfm-qt 0.12.0-5
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: LXQt
Date: Sat May 19 21:58:55 2018
LiveMediaBuild: Lubuntu-Next 18.04 LTS "Bionic Beaver" - Release amd64 
(20180503)
SourcePackage: pcmanfm-qt
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pcmanfm-qt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic lubuntu-next

** Attachment added: "$strace -o pcmanfm-qt.txt pcmanfm-qt"
   
https://bugs.launchpad.net/bugs/1772214/+attachment/5141789/+files/pcmanfm-qt.txt

** Tags added: lubuntu-next

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

Title:
  pcmanfm-qt segfaults after some tricks (Lubuntu Next 18.04 and
  dailybuild of 19.05.2018)

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

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

[Bug 1769421] Re: [18.04] [Bionic]drm_kms_helper causes long delay at boot