$ journalctl -g 'Linux version'
Apr 27 17:57:21 ub3jj kernel: Linux version 5.15.0-27-generic (buildd@ubuntu)
(gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
#28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 (Ubuntu 5.15.0-27.28-generic
5.15.30)
-- Boot
** Attachment added: "previous (successful) boot logs for comparison"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971095/+attachment/5585653/+files/journalctl_b_-1_g_mpt2sas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
mpt2sas card driver failed to start properly after normal poweroff + restart.
Logs attached.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-27-generic 5.15.0-27.28
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux
Public bug reported:
rhythmbox 3.4.2 loop music without no gui.
OS Ubuntu 18.04 LTS.
5.4.0-109-generic #123~18.04.1-Ubuntu SMP Fri Apr 8 09:48:52 UTC 2022 x86_64
x86_64 x86_64 GNU/Linux
rhytmbox version is 3.4.4
When you click playlist. Play song. Close the program in window x button. (From
As a workaround for this use case may want to try
sudo systemctl stop NetworkManager.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898814
Title:
Under netplan with "renderer: networkd",
Patch to /usr/share/plasma/look-and-
feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml
** Patch added: "Fix lock screen password input with keyboard only"
I also have this same problem with Ubuntu 20.04.4 and plasma-workspace
5.18.8-0ubuntu0.1.
I think this is caused by the following upstream bug:
https://bugs.kde.org/show_bug.cgi?id=439604
That bug is closed without a fix though, because 5.18 is unmaintained. However,
there's another upstream
Same issue in home desktop computer. Wifi not turn on. I have to restart
wifi-dongle and computer.
Ubuntu 18.04 LTS. I dont find any options in turned to off. Settings are same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Added a patch at
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366
** Description changed:
- Submitting a patch soon.
+
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366
- Without fix:
- $ set|fgrep PS1|head -1
+ Expected:
+
+
** Patch added: "0001-Properly-escape-PS1-for-xterm-title.patch"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1960366/+attachment/5559792/+files/0001-Properly-escape-PS1-for-xterm-title.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Submitting a patch soon.
Without fix:
$ set|fgrep PS1|head -1
PS1='\[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
With quotation fix applied:
$ set|fgrep PS1|head -1
** Description changed:
Regression to be analyzed further later.
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5)
- Most relevant part of boot logs:
+ Most relevant part of boot logs (more in attachment):
Turning off secondary and tertiary monitors for the duration of the
initial boot appears to work around this issue. Suspend-to-ram works
with all monitors powered (same hardware configuration as in #1926400).
** Attachment added: "journalctl -b -1 -k | egrep -v 'audit|dbus-daemon'"
Public bug reported:
Regression to be analyzed further later.
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5)
Most relevant part of boot logs:
Nov 30 13:08:00 ub3ff kernel: microcode: microcode updated early to
Similar symptoms to https://gitlab.freedesktop.org/drm/amd/-/issues/1406
and repeats in some form most of the time when unlocking screen after
screen blanking.
After suspend somewhat more random behaviour (works more often than
after blanking).
** Bug watch added:
** Attachment added: "Possibly related to
https://gitlab.freedesktop.org/drm/amd/-/issues/1406;
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+attachment/5493225/+files/dmesg.20210429.log
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+attachment/5492985/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+attachment/5492984/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
HWE kernel appears to get more amdgpu MST related WARNINGs and Oopses than
non-HWE, mostly after resume from blanking or suspend.
Kernel logs for most recent one attached.
- $ journalctl -b -1 -k | egrep -v 'audit|dbus-daemon' > /tmp/oops20210428.txt
- $ fgrep RIP
Public bug reported:
HWE kernel appears to get more amdgpu MST related WARNINGs and Oopses than
non-HWE, mostly after resume from blanking or suspend.
Kernel logs for most recent one attached.
$ journalctl -b -1 -k | egrep -v 'audit|dbus-daemon' > /tmp/oops20210428.txt
$ fgrep RIP
Few months ago I gave up and stopped using my TB18. Easier to connect
few cables once a day than fight with this. I'm much happier now. TB18
serves as an expensive laptop stand for me (elevates laptop 5 cm from
table).
--
You received this bug notification because you are a member of Ubuntu
Now that the new SOF firmware is included in the linux-firmware package
(see bug #1900809) the audio stack has been much more stable for me.
Unfortunately there has been still one audio stack crash after the
firmware upgrade, but it probably was another issue, since the dmesg
didn't contain
This update would also fix at least bug #1881505.
Basically, my audio on Lenovo T14 was working very unreliably and jammed
with a DSP panic quite often with the 1.4.2 version, but seems to work
just fine with 1.6.
It would be great to get this update included soon, since it's very
inconvenient
It seems that the 1.6 version of the SOF firmware fixes the issue for
me. Haven't got any of those DSP panic messages anymore after the update
and before the update they occurred almost every day.
Is there anything I can do to help in making this fix to be included to
linux-firmware package?
If this is indeed the same issue as in
https://github.com/thesofproject/sof/issues/2828, then the problem
should be fixed by upgrading the SOF firmware to 1.6 version.
I'll give it a try by installing directly from
https://github.com/thesofproject/sof-bin/tree/stable-v1.6
I will let you know if
I have the same problem with Lenovo T14 (Gen 1), which seems to have a
similar sound device:
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:02c8] (prog-if 80)
Subsystem: Lenovo Device [17aa:22b1]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Actually
https://git.launchpad.net/ubuntu/+source/apport/commit/apport/ui.py?h=ubuntu/quantal=5080c104ebb3a02c4f16a3f6646449db8c72b545
lists a fix (--hanging) for this being available since quantal.
** Tags removed: focal
** Changed in: apport (Ubuntu)
Status: Confirmed => Fix Released
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
Exact reproduction conditions of bug #1891636 and bug #1891745 unknown.
At least OOPS ID 6647d368-df04-11ea-af91-fa163ee63de6 uploaded to
errors.ubuntu.com now, marking these two as duplicates for now.
**
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
Exact reproduction conditions of bug #1891636 and bug #1891745 unknown.
At least OOPS ID 6647d368-df04-11ea-af91-fa163ee63de6 uploaded to
errors.ubuntu.com now, marking these two as duplicates for now.
**
Also https://errors.ubuntu.com/user/$(sudo cat /var/lib/whoopsie
/whoopsie-id) claims "No errors have been reported from this system",
which is consistent with no ".uploaded" files appearing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891636
Title:
After recent updates Xorg crashes whenever entering Display Settings
To manage notifications about
No longer reproducible by visiting display settings after bug #1891745
crash. Possibly a duplicate of bug #1861609.
** Description changed:
- AssertionMessage Xort: ../../../../../../include/privates.h:121:
+ AssertionMessage Xorg: ../../../../../../include/privates.h:121:
dixGetPrivateAddr:
** Description changed:
[Impact]
1. When trying to send a report manually, you can not
- 2. When next possibly unrelated crash of same process happens, .crash
gets overwritten even if .crash.upload exists (= upload not yet
completed?)
- 3. When trying to copy-paste the stacktrace as text,
** Description changed:
[Impact]
1. When trying to send a report manually, you can not
- 2. When trying to copy-paste the stacktrace as text, you can not
+ 2. When next possibly unrelated crash of same process happens, .crash
gets overwritten even if .crash.upload exists (= upload not yet
Public bug reported:
This instance happened after lockscreen, as such may be suspend-resume
related. On the other hand at least 0 and 10 parts on backtrace appear
similar to bug #1891636
While this appears to be a recent regression, DpkgLog.txt doesn't
contain xorg references. Could it be
Public bug reported:
AssertionMessage Xort: ../../../../../../include/privates.h:121:
dixGetPrivateAddr: Assertion `key-initialized' failed.
Also affected by apport bug #1891634 making filling more information
here somewhat tedious.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
Public bug reported:
[Impact]
1. When trying to send a report manually, you can not
2. When trying to copy-paste the stacktrace as text, you can not
[Test Case]
Start Ubuntu
Open terminal
$ ubuntu-bug /var/crash/.crash does not appear to send anything to
errors.ubuntu.com, when NetworkManager
On Ubuntu 20.04 stable,
the Clipit interface does not work on Xorg either. The hotekeys do not work,
the preferences do not open and the program does not shut down properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No such feature seen yet on Focal version of ubuntu-bug either.
** Tags added: focal
** Changed in: apport (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Not reproducible on fresh install on same hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871916
Title:
Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu
To manage
** Patch added: "this patch let me dpkg --configure --pending successfully"
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1872020/+attachment/5351085/+files/grubpostinst.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
(auto)upgrade failed, not analyzed further for now.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: shim-signed 1.40+15+1533136590.3beb971-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
Public bug reported:
Installed (upgraded 16->18->20 beta) ubuntu appears to utilize incorrect
x.org drivers for RX 5500 XT. Those drivers appear to be missing
features like multi-monitor support. On the other hand live-usb of 20.04
beta did manage to utilize all 3 connected monitors (before
install python-six package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853107
Title:
Crash in starting
To manage notifications about this bug go to:
Public bug reported:
Program crash when starting.
Using Ubuntu 18.04 LTS, 5.0.0-36-generic
log is Traceback (most recent call last):
File "/usr/bin/wammu", line 47, in
import Wammu.Locales
File "/usr/lib/python2.7/dist-packages/Wammu/Locales.py", line 31, in
import six
ImportError:
Public bug reported:
im trying to install the most recent ubuntu on an kingston 120gb ssd
drive
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion:
xenial version working fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769132
Title:
ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font
To manage notifications about this bug
Fix not fix the problem in LTS version. I have installed 2.8.1-2ubuntu2
version and i have same problems. (Ubuntu 18.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769132
Title:
ubuntu18.04's
*** This bug is a duplicate of bug 1486316 ***
https://bugs.launchpad.net/bugs/1486316
** This bug has been marked a duplicate of bug 1486316
lpc_ich: Resource conflict(s) found affecting gpio_ich
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1486316
Title:
lpc_ich: Resource conflict(s) found affecting gpio_ich
To manage notifications about this bug go to:
I updated BIOS by saving exe file to usb stick and used bios update option from
BIOS boot menu.
For TB18DC firmware upgrade, I installed Windows 10. Actually firmware upgrade
did not go too smoothly (it upgraded successfully some subsystems, but not all,
failed with MTS1, MTS2).
Here are some
And now the rest of issues seem to have been gone away when I also
updated my TB18DC to the latest firmware (1.0.8).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766076
Title:
USB over
It seems that this problem with TB18DC has gone away for me after
updating my Dell Precision 7530 bios to the latest 1.6.0 version.
There's still another USB problem with dock but symptoms are different
than earlier: for example usb mouse stops working after some time, but
still after that is
Updated kernel to 4.19.15-041915-generic (ukuu), and still this
reproduces.
Right after boot it works fine, then after one working day I disconnect
thunderbolt
and suspend the machine. Then next morning it reproduces within first hour.
With the current setup I don't have any usb devices
Okay, after yet another occurrence of the issue:
lspci -vv
00:00.0 Host bridge: Intel Corporation Device 3ec4 (rev 07)
Subsystem: Dell Device 0831
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz-
No, for me lspci works fine after this issue:
00:00.0 Host bridge: Intel Corporation Device 3ec4 (rev 07)
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Device 3e9b
00:04.0 Signal processing controller: Intel
This is now happening to me about every 10-20 minutes or so. Very
frustrating.
With TB18DC I'm using
- onboard sound port
- onboard ethernet port
- mouse dongle
- fingerprint reader
- 1 large external monitor with DP
After reboot this tends to happen after longer period of time (several
I have the same issue with Dell TB18DC tb dock and Dell Precision 7530
laptop. Using ukuu mainline kernel 4.19.4-041904-generic. I think latest
system bios update 1.4.2 (https://www.dell.com/support/home/us/en/04
/product-support/product/precision-15-7530-laptop/drivers) made this
problem appear a
Public bug reported:
Steps:
1. Open Ubuntu Software
2. Search for "Dropbox"
3. Install it
4. Launch it
5. Click back button < in the top left corner.
Expecting it navigates back to search or main view, but nothing happens.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubuntu-software
Now I have Ubuntu 18.10 installed.
Workaround is to use a working grub2 (for example booting up with Ubuntu
18.04 installation media) and move to grub command line. There I created
a new menuentry for loading Ubuntu 18.10 installer from another USB
stick.
Even though Ubuntu 18.04 installation USB stick works fine, I see same
kind of mmx64.efi error flashing quickly. However it does not halt there
unlike in Ubuntu 18.10 installation media.
The error I see when booting up with Ubuntu 18.04 installation media:
Failed to open \EFI\BOOT\mmx64.efi -
However, using the same usb-creator-gtk (version 0.3.5) in Ubuntu 18.04,
I created an installation USB stick from Ubuntu 18.04. That works
without any problem in MSI laptop. There is no /EFI/BOOT/mmx64.efi file
either in that USB stick, but it works anyway.
The result is that I am not able to
I was about to install Ubuntu 18.10 into laptop (MSI GT62VR 7RE
Dominator Pro) using USB installation media. It was able to boot up and
start installation until the installation halted with a black screen.
After I rebooted I got the same error about missing mmx64.efi.
Windows 10 boots up fine
I can reproduce the bug in Ubuntu 18.04.1 by re-configuring keyboard-
configuration package (version 1.178ubuntu2.7) with DISPLAY being
unset/empty, e.g.:
tuomas@matta:~ 0 $ sudo DISPLAY= DEBIAN_FRONTEND=noninteractive \
dpkg-reconfigure keyboard-configuration
*** This bug is a duplicate of bug 520546 ***
https://bugs.launchpad.net/bugs/520546
** This bug has been marked a duplicate of bug 520546
Alt-f2 switches to virtual terminal 2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think this is a duplicate of #520546.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783859
Title:
Alt-Key handling changed after update
To manage notifications about this bug go to:
Thank you for your work. I will test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661629
Title:
upgrade of kernel fails with mkinitramfs: failed to determine device
for /
To manage
@#9, Supposedly rasdaemon could handle MCEs on bionic+. Have not yet
witnessed it working though, even on hardware that had dozen
reports/year shown with mcelog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same happened also me. Updating system and intel-microcode is installed in AMD
machine.
Updating intel laptop and also AMD-microcode is installed in intel-laptop. Is
there no amendment here? What processor is used.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
im updating latest intel-microcode (sudo apt-get update && sudo apt-get
upgrade -y) and it is also automatically install also amd-microcode in
my laptop. Why? my laptop not use amd-microcode. it is use only intel.
Why it install it when updating my laptop. Is this a bug or what?
--
You received
I have similar big problem with kernel and latest nvidia drivers but i
do not secure boot in my machine. When Ubuntu install new kernel and
boot. nvidia drivers not loaded in kernel. And system crashing.
Error! Could not locate dkms.conf file.
File: does not exist.
using nvidia 390 drivers.
1. appears to depend on snapshot, given cloud images handle the LUNs fine as
additional disks
2. debug symbols part may need more effort than I can spend on this
Also appears to require the following PEBCAK configuration snippet, but
that alone was not enough to reproduce the crash with stock
** Attachment added: "i440fx vm definition (same result with q35 too)"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1773004/+attachment/5143449/+files/ovmf_v02c.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Attempting to boot old 14.04 LTS snapshot in a VM with LUN passthrough
results in segfaults.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: qemu-system-x86 1:2.11+dfsg-1ubuntu7.2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic
Public bug reported:
apt dist-upgrade failed
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libgtk2.0-0 2.24.31-2ubuntu1 [modified:
usr/share/doc/libgtk2.0-0/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
As this bug most likely won't ever get fixed (since Unity7 development
was scrapped), it might be useful to document the known workarounds
here, starting with:
1: Start any window manager with working shade support, for example as follows:
$ nohup openbox --replace >/dev/null &
# Warning: If you
Public bug reported:
It would be nice to have the latest upstream branch in the next Ubuntu
LTS.
** Affects: sssd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I have lubuntu on dvd from www.lubuntu.net i can run it from dvd but i
cannot install it for some reason.. i also cannot format my hdd which
contain win 8.01 and its completely stuck..
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubiquity 17.04.9
upgrading packages and get this error. sudo apt upgrade -f I did it and
the upgrade seemed to go ok.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676423
Title:
package cups-daemon
** Description changed:
I get again blurring text and my windows screen again. When using
updated 379.39 driver in Ubuntu 16.04 LTS.
Driver quality is really bad in recent times. I have suffered with this
problem for a very long time. At times, it disappears for some reason,
but
Public bug reported:
I get again blurring text and my windows screen again. When using
updated 379.39 driver in Ubuntu 16.04 LTS.
Driver quality is really bad in recent times. I have suffered with this
problem for a very long time. At times, it disappears for some reason,
but always come back.
in 379.26 version working with no problems. But it not found a ppa.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675784
Title:
Blurr text and images in screen when using 379.39 driver
To manage
Sorry 375.26
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675784
Title:
Blurr text and images in screen when using 379.39 driver
To manage notifications about this bug go to:
I think this was written in error, unfortunately. It now appears to me
that the cause of the problem described here was actually not due to
Ubuntu touch as I have been able to reproduce it on an android device
with the same headset. So it is likely a hardware issue related to the
headset in
Olivier, I no longer have a device to test this on. However, I am fairly
sure that this problem did occur in other "web apps" using the same
"browser base" (oxide?). But if it is related to the keyboard, and
autopunctuation, one would suspect it to be system wide.
Also, I remember that it seemed
Semi-worksforme @ OTA-15, as in symptoms disappeared for now.
But we shall see whether actual bug(s) were addressed as well after
after 10 weeks assuming no OTA-16 before that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with
root on ZFS I get this error:
Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
In my main computer 64-bit Ubuntu 16.04 LTS, it is working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547297
Title:
No auto login in Ubuntu GNOME Xenial
To manage notifications about this bug
I have a problem. Im using auto-login in my laptop. When im editing
Users and Groups and selecting auto-login off in my user account. It not
working. When reboot the computer. My account auto-login to desktop.
Using Ubuntu MATE 16.04 32-bit. I have full upgraded system.
--
You received this bug
Confirming identical symptoms (symantec sites) to the ones mentioned in
chromium issue linked above. Please consider removing misleading "self-
signed" -part from bug title.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Listening to music using a2dp compatible bt headphones, the audio is
bad. Let me explain. If I plug in a pare of headphones with a 3.5 mm
stereo plug and compare it to the bluetooth audio, I cannot tell the
difference in most devices. I know that a2dp is done with lossy
isn't there some risk of being culpable of "deceptive marketing" or
other such legal issues with things like this? Would think that in such
cases the priority should be "critical"...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Placing calls with priximity sensor
+ Placing calls with proximity sensor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646341
Title:
Placing calls with proximity sensor
To
It just occurred again. I would say that it happens at least once a day.
This time I accidentally typed two white spaces which were then
automatically change to a "full stop sign". I proceeded to erase the
unintentional sign and it did remove it but it also joined the two last
words. I then tried
Public bug reported:
Often (but not always) when text is enterrd into a field this false
concatenation occurs. For example, one types something like "Once upon a
timr." and then realizes the typo and begins to erase. At this time the
text field often then concatenates the last word so that in
Public bug reported:
This might be something easy to implement, butthat would help users
much. Change the app so that when user is browsing through contacts and
selects one, if then at that moment proximity sensor realizes that user
has put phone against head, place call. Currently user needs to
Fix this this problem is also committed to the 1.13 branch of upstream git.
https://git.fedorahosted.org/cgit/sssd.git/commit/?id=afec2ab750a453c592397f6775ec091e894d89b9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When SSSD is run on a server that hosts an AD domain controller powered
by Samba4, all authentication attempts will fail if SSSD is configured
to use the said AD DC as backend and access_provider = ad is specified
in the SSSD configuration. No problems with authentication
Unfortunately the 1.4.3-5ubuntu1 does not fix this bug for me. I'm using
Ubuntu 16.10 on a Dell XPS 13 9343 machine with Haswell i7-5500U CPU and
still getting this same error spammed in syslog every 4 seconds even
after updating the thermald package from wily-proposed.
--
You received this bug
Public bug reported:
Help
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: dictionaries-common 1.20.5
ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CasperVersion: 1.340.2
1 - 100 of 985 matches
Mail list logo
