As of today's Lubuntu 19.04 with lxqt-session 0.14.1, I can confirm this
is now fixed in that it is possible to set other values for the default
browser.
That said, not all browsers show up in the list when installed. falkon,
chromium-browser, and dillo do not show up. They can be added with the
** Changed in: lxqt-config (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/1795539
Title:
only falkon and firefox can be set as default browser
To
Hmmm, this happened to me after I tried to manually install Vagrant from
source on an Ubuntu 18.04 system, and then tried to go back to the
official Ubuntu Vagrant.
So I ran the following command to determine if I had any extra manually-
installed Ruby gems on my system that were not compatible
Oh, sorry, meant the command to be:
comm -23 <(find / -xdev -type f|sort) <(sort /var/lib/dpkg/info/*.list)
| grep gem | sort
grep gem not 'Ruby'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I expected to boot within 20-30 sec. Why?
My old laptop G50-80 i7, 8GB DDR3, SSD take less than 30 sec. average boot time
is 15 sec.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821027
Title:
On the first day using this laptop, I try to fix the boot time problem.
Once you blacklist "thunderbolt_power;thunderbolt" in fwupd, it improve
boot time. But it still take 1 mins to boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
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/1823268
Title:
[Expired for Ubuntu because there has been no activity for 60 days.]
** Changed in: 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/1815529
Title:
user
[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/1814593
[Expired for flatpak (Ubuntu) because there has been no activity for 60
days.]
** Changed in: flatpak (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I will say, though, that there are many examples across various Linucies
(that's the plural, right? ☺) suggesting to use the BROWSER variable to change
the default browser. Case in point:
https://wiki.archlinux.org/index.php/Environment_Variables#Default_programs
And I might add another point:
[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.
** Description changed:
STEPS TO REPRODUCE
- 1. Install firefox
- 2. Set `BROWSER=firefox`
- 3. Open firefox and make sure it is the default browser
- 4. Install chromium-browser
- 5. Open chromium-browser and set it as the default browser
- 6. Click on a link or use `xdg-open URL`
+ 1.
** Changed in: freeplayer (Debian)
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/1757643
Title:
Please port your package away from Qt 4
To manage
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug will contain
(In reply to Torsten from comment #0)
> Created attachment 143902 [details]
> Xorg Log containing the error
>
> Since kernel 4.19.26 and later (4.19.25 and earlier works), with Intel
> integrated graphics i915 (Intel® HD Graphics 3000), Xorg fails to start
> with: "(EE) modeset(0): failed to set
That was my exact issue when I was in Kubuntu 18.10.
In 19.04, this happens even after boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822767
Title:
Desktop is flickering/out of focus
To
This bug was fixed in the package linux-aws - 5.0.0-1003.3
---
linux-aws (5.0.0-1003.3) disco; urgency=medium
* linux-aws: 5.0.0-1003.3 -proposed tracker (LP: #1824375)
[ Ubuntu: 5.0.0-11.12 ]
* linux: 5.0.0-11.12 -proposed tracker (LP: #1824383)
* hns3:
I reviewed edk2 version 0~20181115.85588389-2ubuntu1 as checked into
disco. This review barely scratches the surface of the package.
It appears there's roughly 20 CVEs for sources in this package. We've
accidentally mis-filed eight of them.
This package provides a boot environment; I must admit
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824375
Title:
linux-aws: 5.0.0-1003.3 -proposed tracker
To manage notifications about this bug go to:
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: New => Confirmed
** Tags removed: block-proposed-disco
** Tags removed: block-proposed
** Description changed:
This bug will
This bug was fixed in the package systemd - 240-6ubuntu5
---
systemd (240-6ubuntu5) disco; urgency=medium
* systemd-stable: cherrypick many bugfixes from the v240-stable branch.
Includes many documentation fixes, memory safety (use after free, read
overruns, etc), networkd
There's a lintian error and a warning that probably deserve
investigation:
E: edk2 source: source-contains-unsafe-symlink
EmulatorPkg/Unix/Host/X11IncludeHack
W: edk2 source: unknown-field-in-dsc build-indep-architecture
https://lintian.debian.org/tags/source-contains-unsafe-symlink.html
** Changed in: kernel-sru-workflow/promote-to-release
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
Public bug reported:
found by system
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
I confirm this issue. I see flickering/screen flashing after waking from
sleep on a GTX 1080 card, NVidia driver 418.56. Disabling compositiing
kills the flicker, but flicker returns upon compositing e-enable.
Plamsa and kwin restarts fail to rectify. Reboot is the only sure fix.
** Changed in:
Here's a reduced set of cppcheck results -- I've removed results in
Python, Lua, OpenSSL, and maybe a few more paths out of the results. I
believe upstream need to add cppcheck into their processes.
Every one I've inspected so far represents a real bug. The bugs may not
be easy to hit in
This bug was fixed in the package linux-azure - 5.0.0-1003.3
---
linux-azure (5.0.0-1003.3) disco; urgency=medium
* linux-azure: 5.0.0-1003.3 -proposed tracker (LP: #1824376)
[ Ubuntu: 5.0.0-11.12 ]
* linux: 5.0.0-11.12 -proposed tracker (LP: #1824383)
* hns3:
Public bug reported:
When doing 'stress-ng --class cpu?', not all stressors are listed when
comparing with the kernel reference. One example of a mismatch is the
'hanoi' stressor.
** Affects: stress-ng (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- When doing
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug will contain
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug will contain
This bug was fixed in the package linux-gcp - 5.0.0-1003.3
---
linux-gcp (5.0.0-1003.3) disco; urgency=medium
* linux-gcp: 5.0.0-1003.3 -proposed tracker (LP: #1824377)
[ Ubuntu: 5.0.0-11.12 ]
* linux: 5.0.0-11.12 -proposed tracker (LP: #1824383)
* hns3:
This bug was fixed in the package linux-raspi2 - 5.0.0-1006.6
---
linux-raspi2 (5.0.0-1006.6) disco; urgency=medium
* linux-raspi2: 5.0.0-1006.6 -proposed tracker (LP: #1824374)
[ Ubuntu: 5.0.0-11.12 ]
* linux: 5.0.0-11.12 -proposed tracker (LP: #1824383)
* hns3:
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: New => Confirmed
** Tags removed: block-proposed-disco
** Tags removed: block-proposed
** Description changed:
This bug will
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
** Changed in: kernel-sru-workflow/promote-to-release
Status: New => Confirmed
** Tags removed: block-proposed-disco
** Tags removed: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Changed in: kernel-sru-workflow/promote-to-release
Status: New => Confirmed
** Tags removed: block-proposed-disco
** Tags removed: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
Public bug reported:
At random intervals the screen suddenly pixelates.
The issue does not happen when using the linux kernel v4.17.19-041719
but happens when using other kernels greater than v4.17.19-041719 upto
and including 5.0.0-8.9
Please let me know if you need any other logs and I can
*** This bug is a duplicate of bug 1666495 ***
https://bugs.launchpad.net/bugs/1666495
Instead of copying a .local/share/zeitgeist directory from somewhere,
you can just run "zeitgeist-datahub" from the command line. That
created the .sqlite files for me, at least.
--
You received this bug
A “safe graphics” mode has just been added to 19.04. It is present in
the latest daily test image, which can be found at
http://cdimage.ubuntu.com/daily-live/current/. 19.04 will be release on
Apr 18.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I think I have fixed the rest, including the modifier issue affecting
e.g. Serbian-Latin and Catalan-Valencia.
* Re-opened the bug; new merge proposal for disco (if not too late)
* Added a bug task for bionic; separate merge proposal for that
And @momcilo: The PPA has been updated, so you can
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: New => Confirmed
** Tags removed: block-proposed-disco
** Tags removed: block-proposed
** Description changed:
This bug will
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824377
Title:
linux-gcp: 5.0.0-1003.3 -proposed tracker
To manage notifications about this bug go to:
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824376
Title:
linux-azure: 5.0.0-1003.3 -proposed tracker
To manage notifications about this bug go to:
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
I may have not understood the terminology. Can you be more specific? I used
ubuntu-bug to file the issue and I see a crash report with these details.
Do you have enough to identify this as a bug?
Is there a specific indication of crash are we looking at?
Let me know if you suggest some other
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824383
Title:
linux: 5.0.0-11.12 -proposed tracker
To manage notifications about this bug go to:
This bug was fixed in the package kmod - 25-1ubuntu4
---
kmod (25-1ubuntu4) disco; urgency=medium
* Drop bochs-drm from the blacklist. (LP: #1795857)
-- Timo Aaltonen Fri, 12 Apr 2019 11:23:05 +0300
** Changed in: kmod (Ubuntu Disco)
Status: Confirmed => Fix Released
networkd-dispatcher, on its own, does not configure or control network
interfaces. It listens on d-bus for events from systemd-networkd. So
this is almost certainly a symptom rather than the cause of your
interface stability issues, *unless* you have given networkd-dispatcher
some script to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
This does appear to be hardware related because I encounter no problem
on a box with Intel G41 graphics but the X4500 is a no-go with gdm3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824588
** Tags added: kernel-block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824592
Title:
linux-fips: 4.15.0-1005.6 -proposed tracker
To manage notifications about this bug go to:
Between these changes, should be sorted:
software-properties (0.97.11) disco; urgency=medium
* Added software-properties-lxqt.desktop and software-properties-
drivers-lxqt.desktop to software-properties-qt.install
-- Hans P Moller Thu, 11 Apr 2019 12:04:11
-0400
software-properties
This issue was fixed in the openstack/neutron 12.0.6 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501206
Title:
router:dhcp ports are open resolvers
To manage notifications about this
This issue was fixed in the openstack/neutron 13.0.3 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501206
Title:
router:dhcp ports are open resolvers
To manage notifications about this
This issue was fixed in the openstack/neutron 12.0.6 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813007
Title:
[SRU] [OSSA-2019-002] Unable to install new flows on compute nodes
when
This issue was fixed in the openstack/neutron 13.0.3 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813007
Title:
[SRU] [OSSA-2019-002] Unable to install new flows on compute nodes
when
This issue was fixed in the openstack/neutron 13.0.3 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818614
Title:
[SRU] Various L3HA functional tests fails often
To manage notifications
This issue was fixed in the openstack/neutron 12.0.6 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818614
Title:
[SRU] Various L3HA functional tests fails often
To manage notifications
This issue was fixed in the openstack/neutron 11.0.7 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501206
Title:
router:dhcp ports are open resolvers
To manage notifications about this
This issue was fixed in the openstack/neutron 11.0.7 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813007
Title:
[SRU] [OSSA-2019-002] Unable to install new flows on compute nodes
when
This issue was fixed in the openstack/neutron 11.0.7 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818614
Title:
[SRU] Various L3HA functional tests fails often
To manage notifications
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824578
Title:
Screen lock doesn't lock Launcher (left-sidebar) and Status Menus
** Changed in: xournal (Debian)
Status: New => 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/1801521
Title:
hopelessly outdated version 0.4.8-1build1
To manage notifications
This bug was fixed in the package ubuntu-advantage-tools - 19.4
---
ubuntu-advantage-tools (19.4) disco; urgency=medium
* Drop the self-test assert in the apt-hook, it's making the subiquity
server install fail (LP: #1824523)
-- Andreas Hasenack Fri, 12 Apr 2019 17:59:16
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
BTW fix is in:
lubuntu-default-settings (19.04.2) disco; urgency=medium
[ Hans P Möller ]
* Set tap to click as default for touchpad
[ Raman Sarda ]
* Added entries for (almost) all file types to mimeapps.list
-- Hans P Möller Sat, 06 Apr 2019 20:41:56
-0300
--
You received this
No problem, make it public.
** Information type changed from Private Security to Public Security
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hello, our InRelease and Release files on our archive mirrors appear to
include information for other architectures:
eg
$ ls -l InRelease
-rw-r--r-- 1 mirror mirror 256316 Apr 12 14:55 InRelease
$ grep -e binary-arm64 -e binary-s390x -e binary-armhf -e binary-ppc64el
got a few more tweaks to the storage test, and it's now more
consistently passing on all other architectures but ppc64le.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814373
Title:
storage / luks
No, my integrated MX150 with Nvidia driver 390.116 is working fine with
5.0.7. I'm using Ubuntu 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/1752165
Title:
TB16 dock freezes X on hotplug
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
I'm sorry for not fixing this yet. A few higher priority bugs kept me
busy lately. I will look at fixing it next Monday, with a bit of hope it
may be easy and I can get it done without shuffling other planned work.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug was fixed in the package unity-greeter -
18.04.0+19.04.20190410-0ubuntu1
---
unity-greeter (18.04.0+19.04.20190410-0ubuntu1) disco; urgency=medium
[ Khurshid Alam ]
* src/list-stack.vala: Fix build with vala 0.43.x
[ Luke Yelavich ]
* Remove at-spi load/kill code
** Summary changed:
- linux-fips: -proposed tracker
+ linux-fips: 4.15.0-1005.6 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team)
--- Comment From wil...@us.ibm.com 2019-04-12 18:13 EDT---
I upgraded a built the following packages, I am continuing to see the same
error with the new versions.
kernel 5.0.7-stable
dpdk-19.02
rdma-core (master branch, commit 4bb3583c228566958e2c6f34392c9e39e799bacf)
--
You received
** Also affects: nfs-utils (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925943
Importance: Unknown
Status: Unknown
** Also affects: nfs-utils via
http://bugzilla.linux-nfs.org/show_bug.cgi?id=334
Importance: Unknown
Status: Unknown
--
You received
I found that turning auto-login off resulted in booting to a black
screen so after unsuccessfully trying the nomodeset boot option I
installed 'lightdm-gtk-greeter' and 'lightdm' from recovery mode which
gives me a working system. I had encountered no problems with desktop
behavior but this box
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Tags added: rls-bb-incoming
** Tags removed: rls-bb-incoming
** Tags added: rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824591
Title:
Badge in ubuntu session doesn't follow
*** This bug is a duplicate of bug 1824592 ***
https://bugs.launchpad.net/bugs/1824592
** This bug is no longer a duplicate of bug 1824039
linux-fips: 4.15.0-1004.5 -proposed tracker
** This bug has been marked a duplicate of bug 1824592
linux-fips: -proposed tracker
--
You received
Eric I compare optimized Windows 10 with the bare minimum options and
configured for energy saving rather than performance. Since I'm not good
at linux I can't do the same there to have an accurate result. This
feels like testing apples with oranges but still is the most I can do. I
will try
Windows 10 when installed and at first day(s) make a lot of tests for
system health and configuration, especially when idle, even .NET
compilations. Another factor is the edition you use with/without store
and universal apps that run in the background. Most of all you need to
use the power profile
*** This bug is a duplicate of bug 1824592 ***
https://bugs.launchpad.net/bugs/1824592
** This bug is no longer a duplicate of bug 1824039
linux-fips: 4.15.0-1004.5 -proposed tracker
** This bug has been marked a duplicate of bug 1824592
linux-fips: -proposed tracker
--
You received
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+
+ -- swm properties --
+
*** This bug is a duplicate of bug 1824592 ***
https://bugs.launchpad.net/bugs/1824592
** Tags removed: kernel-sru-derivative-of-1822820
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1822817
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Bionic)
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/1824592
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug:
I'd like to confirm Andrew Conway's report. Restarting snapd does not
change anything.
Could you at least up the priority of the bug. After all it's been there
for quite a while, it's been confirmed and people have worked and are
working on it. Just a little push to solve it. Pretty please! :-)
** Summary changed:
- Ubuntu Disco logs out to black screen
+ Ubuntu Disco boots to or logs out to black screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824588
Title:
Ubuntu Disco boots to
Hello,
I am sorry, but this is NOT a bug. It seems you are unhappy with some
programs/packages you have installed (either by yourself, or
automatically), but it is not at all clear what, where, why, and how.
Right now this sounds much more like usage issues than actual bugs (a
bug is an error in
Also, you may want to try https://askubuntu.com/ before opening a bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824565
Title:
I'm just trying to make my compouter more stable.
To manage
Public bug reported:
See: https://i.imgur.com/oOMCEl2.png
The badge sould have green background, while it's red with green border
** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
--
You
** Changed in: lubuntu-default-settings (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/1769420
Title:
missing mimeapps.list for cosmic
To manage
Hello, verification is completed with no issues. Results in the doc:
https://docs.google.com/document/d/1xB29Pgwqp_Cpbp53_XsHC3s-Bmh3nYjfkU72DpP1imc/edit?usp=sharing
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic verification-needed-trusty
Public bug reported:
Just testing Disco and wanted to see what login options are available
after adding 'gnome-shell-extensions' and found that logging out lands
me on a black screen that's unresponsive to any keyboard input. I'll
test on some slightly different hardware soon.
ProblemType: Bug
1 - 100 of 488 matches
Mail list logo
