This is a fresh installation of Ubuntu 18.04.1
In Ubuntu 16.04.5 with the kernel linux-generic-hwe-16.04 on this equipment
problems were not observed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Photo screen"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788286/+attachment/5180090/+files/IMG_20180823_200038.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Joseph for taking the issue.
I didn't made any update.
As I've mentioned I had rectified no power supply problem, ICs were replaced.
Although as I ran 'fsck' to check filesystem errors, it reported 1 bad sector
on my linux partition.
Could this be the possible cause? Any suggestions!
Hi charlie,
thank you for your answer.
I confirm I'm using VMware me too.
Last kernel 4.15.0-33 doesn't fix the issue.
Last kernel not affected is 4.15.0-30.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You mention BIOS, but you have filed this bug report against shim which
is a UEFI bootloader. Is your system running UEFI? How does your boot
menu look? Can you post the output of 'efibootmgr -v' when booted from
the live CD?
You can also run 'apport-collect 1788781' when booted from the
Public bug reported:
trying to install a text browser in order to get www-browser
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: lynx 2.8.9dev16-3
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
apport information
** Tags added: apport-collected
** Description changed:
when cheese starts, shortly the view of the webcam is visible and then shows
an error.
When run from the command line, the terminal shows:
(cheese:6379): Gtk-WARNING **: 01:08:46.810: Theme parsing error:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1788725/+attachment/5180132/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1788725/+attachment/5180134/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1788725/+attachment/5180138/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1788725/+attachment/5180137/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1788725/+attachment/5180133/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1788725/+attachment/5180129/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1788725/+attachment/5180139/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1788725/+attachment/5180131/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1788725/+attachment/5180140/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725
Title:
I didn't get a chance to try with secure boot disabled because the
upgrade ran the recovery. I will disable secure boot and try again.
Earlier message in full from earlier in installation:
Your system has UEFI Secure Boot enabled in firmware, and the following kernels
present on your system
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1788725/+attachment/5180141/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1788725/+attachment/5180130/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1788725/+attachment/5180135/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1788725/+attachment/5180136/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1788725/+attachment/5180128/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788725
Title:
** Summary changed:
- linux: -proposed tracker
+ linux: 4.4.0-135.161 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) =>
Hi,
you seem to have all kinds of services already running, in your log I found:
Apache stumbling:
Aug 23 10:42:05 k-HP-EliteBook-8460p apachectl[7951]: (98)Address already in
use: AH00072: make_sock: could not bind to address [::]:80
Aug 23 10:42:05 k-HP-EliteBook-8460p apachectl[7951]:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
If you've come here because you have this issue in bionic/18.04 and there's no
fix yet, then you can download these two packages:
https://packages.ubuntu.com/xenial/amd64/oping/download
https://packages.ubuntu.com/xenial/amd64/liboping0/download
And install them manually with dpkg -i
oping will
Public bug reported:
Installation of `nvidia-396` after `sudo add-apt-repository ppa
:graphics-drivers/ppa` on Ubuntu 18.04 fails due to
```
> sudo apt-get install -f nvidia-driver-396
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libselinux (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/1769301
Title:
** Summary changed:
- linux-kvm: -proposed tracker
+ linux-kvm: 4.4.0-1033.39 -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)
> When host call fails (even with timeout), it returns "1" claiming
"dns_has_local()=true".
0 = true, 1 = false (you implied the opposite)
What may add confusion here is the grep -vq check is like an extra check
to make sure host didn't return 0 (success = we found .local) but then
say 'not
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: texlive-extra (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/1788162
** Summary changed:
- linux-aws: -proposed tracker
+ linux-aws: 4.4.0-1067.77 -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)
** Package changed: ubuntu => util-linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788321
Title:
swapon failed: invalid argument
To manage notifications about this bug go to:
@mpontillo would you mind testing with the libvirt that's in the release
pocket of Bionic?
https://launchpad.net/ubuntu/+source/libvirt/4.0.0-1ubuntu8
That would help tell us if libvirt has had an SRU that changed this
behavior in the short time that Bionic has been released.
--
You received
Mark this as fix-released for kernel testing, the test works as expected
on both generic / kvm kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788338
Title:
DEBUG_WX is expected to be unset
** Changed in: libavg (Ubuntu)
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/1785054
Title:
FTBFS with ffmpeg 4 in cosmic
To manage notifications about this bug
I've asked a question on stackexchange.com, but still no answer. There is a
detailed description and some logs.
https://unix.stackexchange.com/questions/458853/useradd-groupadd-fails-failure-while-writing-changes-to-etc-passwd-and-etc-gr
--
You received this bug notification because you are a
Since the original reporter confirms the bug was fixed for a while prior
to version 3.0.3, it would be best to open a new bug and mention there
what version the regression occurred in.
To open that new bug, please just run:
ubuntu-bug vlc
--
You received this bug notification because you are
*** This bug is a duplicate of bug 1762219 ***
https://bugs.launchpad.net/bugs/1762219
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1762219, so is being marked as such.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1788798
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
Hello,
This is a duplicate of bug #1783957 !
Yes, I confirm this is a duplicate that above bug, because nobody is
taking care of my problem of the above bug !!! Sadly ! And I will
(normally, with decency, not abusing of anything) report this on more
forums and more bug
** Summary changed:
- linux-raspi2: -proposed tracker
+ linux-raspi2: 4.4.0-1096.104 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
Public bug reported:
Attempted to switch to nvidia drivers after using nouvaeu.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libnvidia-compute-390 (not installed)
Uname: Linux 4.18.4-041804-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
Date: Fri Aug 24 00:10:37
Tested, confirmed wrapped in a libvirt upstream patch and submitted at
https://www.redhat.com/archives/libvir-list/2018-August/msg01532.html
Lets give the people a few days to read and ack as well then we can push
it to cosmic.
It came to my mind that due to HWE-Kernels we eventually also want
After some discussion with Kamal,
Although this MANDATORY_FILE_LOCKING is considered to be a "very common
feature", we decided not to enable it since its on its way to being
removed altogether (unless some customer were to ask for it, then I'd
say switch it on for sure).
Thanks
** Changed in:
** Summary changed:
- linux-snapdragon: -proposed tracker
+ linux-snapdragon: 4.4.0-1100.105 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788787
Title:
package libnvidia-compute-390 (not installed) failed to
install/upgrade: trying to overwrite
Public bug reported:
Tested on Lubuntu 18.04 and Lubuntu 18.10:
Install compton-conf in Lubuntu 18.04. It is present by default in Lubuntu
18.10.
The entry in Menu > Accessories is "compton". Clicking on it does
nothing.
The corresponding .desktop file in /usr/share/applications is
This bug was fixed in the package dphys-swapfile - 20100506-5
---
dphys-swapfile (20100506-5) unstable; urgency=high
* Add patch to fix the setup subcommand exiting prematurely with more
recent dc versions. (Closes: #906767, LP: #1788681) Also update
Hello Hans, Hello Christian.
Thank you so very much for your answers.
They really helped, you solved it.
Yes I am having a minimal server installation.
And yes, as i looked into
/etc/apt/sources.list
an entry like
deb http://archive.ubuntu.com/ubuntu bionic universe
was missing.
Just
On classic systems snapd will honor the system proxy settings via
http_proxy (and friends). However it does not (yet) respect the internal
settings. The following PR changes this:
https://github.com/snapcore/snapd/pull/5699
--
You received this bug notification because you are a member of Ubuntu
FWIW, I also found the default to be a questionable choice, as well as
the justification for it - ie the tools mentioned aren't really
equivalent to this one - they're tools for transferring files, not for
monitoring network bandwidth.
However, I did a quick search for 'bandwidth monitoring
I have a theory some instances of this bug could be caused by the non-
deterministic nature of 'get_dirty_pixel' in the mutter source code.
You don't need to know what that means, but if you have the knowledge to
test patches then please try this one:
(That page is two patches actually. You need both.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181666
Title:
gnome-shell randomly blocks mouse clicks from working in app windows
To manage
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783957
Title:
Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no
login screen in a normal
VLC media player 3.0.3 Vetinari
It freezes on fullscreen. I'm new to ubuntu so i don't really understand the
threads. Can someone enlighten me. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I will start a new bug report, as nobody cares with this bug, I see.
Opensource community fixing bugs more rapidly than commercial software
companies ? I'll think again about that one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784223
Title:
Learning how to build a new system using the UEFI stuff. I expect many
installs before success.
To manage notifications about this bug
- auto-internal backup: https://bugzilla.gnome.org/show_bug.cgi?id=716151
- Jpg-raw images: https://gitlab.gnome.org/GNOME/shotwell/issues/21
** Bug watch added: GNOME Bug Tracker #716151
https://bugzilla.gnome.org/show_bug.cgi?id=716151
--
You received this bug notification because you are
** Changed in: kernel-sru-workflow/snap-release-to-stable
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/1788769
Title:
linux-aws: 4.4.0-1067.77 -proposed tracker
To
I had the same problem with sound and brightness hot keys after
upgrading to Ubuntu 18.04 on a Lenovo P50 using Unity.
Park Ju Hyung (arter97) solution #11 worked for me but with a slight
modification:
ExecStartPre=/bin/sleep 1
Otherwise the hotkeys worked but the fonts began to fade making the
** Changed in: ubuntu-kernel-tests
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/1788338
Title:
DEBUG_WX is expected to be unset for X-KVM kernel
To manage
Thanks Jens for the upstream pointers
** Changed in: shotwell (Ubuntu)
Status: New => Triaged
** Changed in: shotwell (Ubuntu)
Importance: Undecided => Critical
** Changed in: shotwell (Ubuntu)
Importance: Critical => Wishlist
** Also affects: shotwell via
This change results in not being able to log in to the live session
again with sddm, should you log out or restart X.
sddm does not support passwordless login it seems:
https://github.com/sddm/sddm/issues/751
** Bug watch added: github.com/sddm/sddm/issues #751
--- Comment From heinz-werner_se...@de.ibm.com 2018-08-24 03:32 EDT---
IBM bugzilla status -> closed, Fix Released with Cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786460
Title:
Thanks for getting back on this so fast.
I followed the proposed steps:
1. `ubuntu-bug _usr_lib_xorg_Xorg.1000.crash` reported the bug, but
closed silently. I did not get a new bug ID. Where can I find it?
2. On that page I can find crashes from 2017, but none from after the
upgrade to Ubuntu
I followed the linked howto sans the ipv6 pieces as I had no ipv6 target range
anywhere to be used.
I can connect just fine with that.
Before I do that it would be easier for you to check if dropping the ipv6 lines
from the server conf make it work.
If it does - then we know it only affects the
Public bug reported:
Series: Cosmic
sddm: 0.18.0-1ubuntu2
casper: 1.395
Since casper change: https://launchpad.net/ubuntu/+source/casper/1.395
"Set empty live user password on all flavours, this was previously gdm
specific."
sddm login to the live session is not possible. e.g. should the live
Hello Jonathan, or anyone else affected,
Accepted console-setup into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/console-
setup/1.178ubuntu2.7 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Public bug reported:
When I suspend my laptop, it often happens that the bluetooth stops
working. From gnome settings it is shown like if I had no bluetooth
device at all.
$ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i
'blue|firm'
03:00.0 Network controller [0280]:
Restarting the computer is the only way I found so far to make the
bluetooth work again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788807
Title:
Bluetooth device not detected after resume from
Kai-Heng, the bug seems to be gone on my system with your newest kernel
in #63 and I don't experience any regression so far. Thanks for your
work!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Upstream says:
"Resolving as fixed with the Xwayland Present implementation in 1.20"
So fixed in cosmic.
** Changed in: xorg-server (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
BertN45,
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. You reported this bug some
time ago and there have been many changes in Ubuntu since that time.
Your
*First linux bug report*
I am also affected by this issue Bionic: 4.15.0-33 on a Dell Aurora R6
Processor is i7-7700K Kabylake getting the issue with the PCI bus
connected to Intel Corporation Wireless 3165 card.
I see someone said a fix is in place, but cannot find where the fix has
been
Chris,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Do you still see a problem related to the one that you reported? Please
let us know if you
Giovanni,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Do you still see a problem related to the one that you reported? Please
let us know if
Per git bisect, the fix for this should be:
commit 6c971c09f38704513c426ba6515f22fb3d6c87d5
Author: Y.C. Chen
Date: Thu Jan 26 09:45:40 2017 +0800
drm/ast: Fixed system hanged if disable P2A
The original ast driver will access some BMC configuration through P2A
bridge
that
Public bug reported:
Booting Trusty with kernel 3.13.0-156-generic on a fairly new Intel box
results in stuck CPU warnings:
[ 33.551942] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/0:1:1119]
[ 33.558560] Modules linked in: hid_generic ast(+) crct10dif_pclmul
syscopyarea crc32_pclmul
Public bug reported:
apropos memory usage recommends memusage(1) and memusagestat(1) but
command-not-found cannot find these tools, recommending instead
gmemusage (which seems to require X and is unrelated).
I've heard that in Fedora the memusage script is in a libc-utils
package, but I seem to
Vitali,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
I have tested "YouTube" and "Dailymotion" using Ubuntu 18.04 and Firefox
61 and the sound
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1788817
and then change the status of the bug to 'Confirmed'.
If, due to the
** Changed in: kernel-sru-workflow/snap-release-to-candidate
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/1787162
Title:
linux-gcp: 4.15.0-1018.19~16.04.2
Was this issue resolved in 18.04 with light-locker 1.8.0?
** Changed in: light-locker (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/1646152
Title:
Back to
Ciao nulla ho dato a terminale quello che mi hai detto ma non ha
funzionato inoltre il pc non si spegne resta schermo nero led acceso,può
dipendere dallo stesso problema ?grazie
Il Giovedì 23 Agosto 2018 14:55, Joseph Salisbury
ha scritto:
You may need to run the following from a
(I'm sorry, I have troubles adding comment in launchpad- receiving timeout).
Thanks for response. I have tried it now, looks like the problem is
resolved already, icon disappears. (But I'm using Ubuntu 18.04
already)
Kind regards,
Vitali Kuzmin
On Fri, Aug 24, 2018 at 12:41 PM Paul White
I followed this instructions
(https://wiki.ubuntu.com/Kernel/KernelBisection#Reverse_commit_bisecting_upstream_kernel_versions)
to make a reverse commit bisect
Output of the last git bisect:
$ git bisect good
3549130ef7f6ec732a7770ea0ac36231be85a089 is the first bad commit
commit
Please subscribe yourself to those upstream bugs, this is out of
Ubuntu's scope
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788679
Title:
Features request
To manage notifications about this bug
Still seeing this (haven't updated, neither using apt nor update-manager
because this bug annoys me).
Digged for when this was introduced in update-manager and found the
package was updated in June:
$ zgrep update-manager /var/log/apt/hi*2* -B3 -A1
/var/log/apt/history.log.2.gz:Start-Date:
** Summary changed:
- Bluetooth not working on Dell XPS 15
+ Bluetooth not working on Dell XPS 15 (Qualcomm Atheros QCA6174)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782893
Title:
Bluetooth
somehow this bug was filed against linux, changed it to cheese (the
webcam software) and added missing logfiles, marked as confirmed.
** Package changed: linux (Ubuntu) => cheese (Ubuntu)
** Changed in: cheese (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to install a particular package. Please execute the following
command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try
I cannot authorize this computer to my Launchpad account, as this is a
work computer.
Tell me which logs do you need, and I will gladly provide them.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778020
Title:
devices not authorized at lightdm on initial boot
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (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/1774188
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (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/1774188
Title:
Launchpad has imported 33 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=105811.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (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/1774188
Title:
Settings is gnome-control-center. Did you install any gnome session?
** Changed in: unity (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/1788724
Title:
Two
Public bug reported:
After a fresh boot computer suspends fine, however further attempts to
suspend result in failure with the above mentioned error message. When
that happens, shutdown doesn't work either; shutdown process gets stuck
at some point and I must forcibly turn off or reset the
1 - 100 of 581 matches
Mail list logo
