Hello Eduardo:
I was wondering if anyone had version 5.2.18-dfsg-2 installed and didn't do
updates ever since, but this is a rare case.
that version is the base in cosmic, so if anybody has it installed is not on
xenial anymore...
please don't make confusion between 5.0.18 and 5.2.18 :)
If you
Moreover problem appear not only in 18.04 but also in 18.10 version.
Rolling back gnome-shell and gnome-shell-common packages fix this
problem, so i added gnome-shell to affected packages.
according to this launchpad - https://launchpad.net/ubuntu/+source/gnome-shell
for Ubuntu 18.04:
-
This bug was fixed in the package metacam - 1.2-11
---
metacam (1.2-11) unstable; urgency=medium
[ Joao Eriberto Mota Filho ]
* Using new DH level format. Consequently:
- debian/compat: removed.
- debian/control: changed from 'debhelper' to 'debhelper-compat' in
1366x768 (16:9) the scale is not changed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812190
Title:
distorted and disappearing icons on the toolbar at the top
To manage notifications about this
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812266
Title:
Keyboard layout indicator does not indicate current
Everyone please follow the steps in comment #2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812527
Title:
gnome-shell crashes when switching from workspace that is running
Android emulator
Almost all actions lead to the described problem, including running a video
capture program.
https://youtu.be/0QCqQPNGHhs
** Attachment added: "journalctl.zip"
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1812190/+attachment/5230926/+files/journalctl.zip
--
You received this bug
Same issue here [https://answers.launchpad.net/ubuntu/+question/677918].
Please see my answer, hope it helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812527
Title:
gnome-shell crashes when
Here is a correction to my previous post (the post immediately above
this one). '[W]hat do you have in my specifically': I meant 'have in
mind'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791427
I did not tried reboot=pci, will try now. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
systemd: Failed to send signal
To manage notifications about this bug go to:
Public bug reported:
### What I expected to happen
`service fwknop-server stop` should stop the service
### What happened instead
Nothing, the service is still running
### Details
The default [init.d
script](https://github.com/mrash/fwknop/blob/master/extras/fwknop.init.debian)
looks for the
> do you see any output when typing journalctl -b 0 -k?
Yes, but what do you have in my specifically? Anyway, at present I am
not running the patched kernel, because (1) as I explained, it broke my
networking, (2) deblacklisting the touchpad module seemed to cause my
touchpad problems (even when
The solution was manually partitioning the disk and choosing the
installation location of grub to an efi partition. I guess ubuntu was
trying to install the grub to a wrong partition, such as /dev/sda.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Finally I have fixed the problem by compiling and installing latest git
xf86-video-intel driver. Now everything works fine. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797604
Title:
I am also seeing this problem, which seemed to manifest itself after a
recent update. By experimenting, I've determined that there seems to be
a segfault in libmutter-2.so.0.0.0 each time the workspace changes (when
the Android emulator is running).
Please see the attached excerpt from my syslog.
It has miraculously fixed itself... I had installed the synaptic
drivers, rebooted and no joy the first time round. After rebooting just
now, the device is being picked up.
➜ ~ cat /proc/bus/input/devices
I: Bus=0019 Vendor= Product=0003 Version=
N: Name="Sleep Button"
P:
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => 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/1728238
Title:
update-initramfs not adding i915 GuC firmware for Kaby
** Changed in: linux (Ubuntu)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu Bionic)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu)
Status: In Progress => Confirmed
** Changed in: linux (Ubuntu Bionic)
Although you have provided some logs that are not in recovery mode,
those logs span multiple days so are not helpful in pinpointing the
immediate problem.
When sending logs in future please ensure they don't mention "recovery
nomodeset", AND that the earliest and oldest dates in the log file are
I suspect the mistake is that you are not manually un-selecting recovery
mode, so it is always rebooting in the same mode as last time, so is
always in recovery mode.
Either that or the non-recovery mode boots are failing to record a log
at all. But I suspect it's more likely you're stuck in
This change was made by a bot.
** Changed in: linux (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/1812609
Title:
Linux kernel bug, HP laptop touch pad
hi, more feedback from me: i am now running this kernel since sa morning
without any issue with at least 20 suspend/resumes. Just in case, i
appended my journalctl log (but without the debug kernelparameter).
@ALinuxUser: do you see any output when typing journalctl -b 0 -k?
** Attachment added:
** Changed in: 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/188051
Title:
[needs-packaging] Cytoscape
To manage notifications about this bug go to:
** 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/1812610
Title:
package phpmyadmin 4:4.6.6-5 failed to install/upgrade: installed
phpmyadmin package pre-removal
Public bug reported:
#2006 - MySQL server has gone away;
mysqli_real_connect(): Unexpected server respose while doing
caching_sha2 auth: 109;
mysqli_real_connect(): MySQL server has gone away;
mysqli_real_connect(): (HY000/2006): MySQL server has gone away;
i have mysql-server installed but
Public bug reported:
I can't use my touchpad. Followed this page
(https://wiki.ubuntu.com/DebuggingTouchpadDetection) and came to the
conclusion that this is a Linux kernel bug.
➜ ~ cat /proc/bus/input/devices
I: Bus=0019 Vendor= Product=0003 Version=
N: Name="Sleep Button"
P:
Hey Daniel,
I'm honestly not sure what I'm doing wrong. Here's precisely what I'm
doing. Tell me where I'm messing up:
First, I booted into recovery mode by hitting Esc on bootup, and selecting
boot into recovery mode. The computer then boots, and reaches a point at
which it I have multiple
Looking at the dmesg | grep wlp2s0 can also put some light on this.
Apparently, TX Power Saver causes connection loss for networks with PEAP
authentication.
WiFi works fine on home networks (WPA2/WEP)
Drops at college/work. (PEAP)
This was my last output.
[570105.023727] wlp2s0: Limiting TX
Public bug reported:
I am reporting this as a new bug, because I did not do anything custom
in the installation wizard.
I only chose pre-defined options in the form of radio buttons and check boxes.
A summary of my choices through the wizard:
- I chose the English
- I chose an English keyboard
[Expired for coreutils (Ubuntu) because there has been no activity for
60 days.]
** Changed in: coreutils (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for One Hundred Papercuts because there has been no activity
for 60 days.]
** Changed in: hundredpapercuts
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]
** Changed in: thunderbird (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for thunar (Ubuntu) because there has been no activity for 60
days.]
** Changed in: thunar (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/1769870
[Expired for pcmanfm-qt (Ubuntu) because there has been no activity for
60 days.]
** Changed in: pcmanfm-qt (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for smbc (Ubuntu) because there has been no activity for 60
days.]
** Changed in: smbc (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/1672885
[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm3 (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/1804251
[Expired for libreoffice (Ubuntu) because there has been no activity for
60 days.]
** Changed in: libreoffice (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for gnome-software (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: gnome-software (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for apt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: apt (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/1804343
** 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/1812606
Title:
package libcom-err2:amd64 1.44.4-2ubuntu0.1 failed to install/upgrade:
package libcom-err2:amd64
[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/1803915
Title:
nose
[Expired for xscreensaver (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: xscreensaver (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for initramfs-tools (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: initramfs-tools (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for thunar (Ubuntu) because there has been no activity for 60
days.]
** Changed in: thunar (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/1796089
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for lubuntu-meta (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: lubuntu-meta (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Selwyn, thank you for reporting this and helping make Ubuntu better.
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? Please keep in mind the following:
1) The one to test is in
Public bug reported:
Linux update was the culprit
ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: libcom-err2:amd64 1.44.4-2ubuntu0.1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
AptdaemonVersion:
Tudor Holton:
Given you've tested the latest mainline kernel, latest BIOS, and assuming all
the previous test results are the same when not using any non-default kernel
parameters as noted in your Bug Description:
i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013"
it appears one is to wait while
** Tags removed: kernel-bug-exists-upstream-4.2-rc4 needs-upstream-testing
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-5.0-rc2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
"incorrect resolution" is because you have booted into recovery mode,
which disables proper resolutions via the "nomodeset" kernel parameter.
Please reboot and as soon as the purple screen appears tap "Esc". Now
select a normal kernel to boot that is not recovery mode.
If the problem still
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: 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/1652570
Title:
Bug while
** Package changed: xorg (Ubuntu) => systemd-shim (Ubuntu)
** Summary changed:
- update error
+ installed systemd-shim package post-removal script subprocess returned error
exit status 2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Having troubles with interfaces, HD shows problems and my usb ports are
not connecting. Please advise. I did a complete reinstall in december
2018.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu
Please try uninstalling these extensions and then tell us if the bug
still occurs after they are gone:
'mediapla...@patapon.info'
'system-moni...@paradoxxx.zero.gmail.com'
'desktop-icons@csoriano'
'gsconn...@andyholmes.github.io'
'tracker-search@cewee'
If the bug then no longer occurs, please
Does this bug affect just the internal speakers? Do headphones work?
** Changed in: pulseaudio (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/1372096
Title:
** Summary changed:
- Internal speakers not working after crash reboot
+ [ALC662 rev3] Internal speakers not working after crash reboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812567
Title:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
It looks like you've made some changes to power management that might
have caused this bug.
Please try using powertop (or whatever you use already) and ensure your
mouse or bluetooth adapter is never set to sleep.
** Summary changed:
- When I use my Bluetooth A2DP headset (Philips SHB7102)
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1769383, so it is being marked as such. Please
Please:
1. Boot normally and reproduce the freeze again.
2. Reboot again into recovery mode and then run:
journalctl -b-1 > prev_boot.txt
and send us the resulting file 'prev_boot.txt'.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
** Changed in: ubuntustudio-controls (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/1809024
Title:
CPU Governor setting does not persist after reboot
To
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1812446
When reporting bugs in the future please use apport by using 'ubuntu-
The Intel J3455 processor has been around for 2 years so I think Ubuntu
supports it already.
What is the problem that you are seeing?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1769383, so it is being marked as such. Please
When you say "the grey background" of the login screen, that makes me
curious. Why is it grey? It should be purple.
If it's grey because of changes you made then please try Ubuntu without
changing the system in such a way that the login screen is grey. Does
the bug still happen if you install
Thanks.
Since we need each bug to be about a single issue, let's make this one
about just the keyboard not responding. If you have other performance
problems then please log a new bugs for those.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Summary changed:
-
Also, what shell are you using?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811808
Title:
Tearing and/or flickering when using Intel graphics
To manage notifications about this bug go to:
Thanks.
Next I would like to confirm if this is really a pure Intel bug. Just
for testing, can you please try uninstalling the Nvidia driver, reboot
and then log into "Ubuntu on Wayland"?
Does using a Wayland session avoid the bug?
Please also run 'xrandr' in the Wayland session and send us the
** No longer affects: xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812367
Title:
xdotool does not work well if launched by a shortcut
To manage notifications about this bug go to:
Thanks for the pointer. A bug was just reported to
https://gitlab.gnome.org/GNOME/gnome-control-center/issues as
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/351
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Please try again. The log in comment #7 is from recovery mode :(
I think you forgot step 2 in comment #2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811599
Title:
When booting, the computer
This sounds like an application freeze which then leads to a shell (but
not the X server) freeze.
Please run this command to send us more information about the system:
apport-collect 1805782
** Changed in: wine (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807276
Title:
Cannot swipe up from bottom of screen to get Onscreen Keyboard in
Since "the mouse cursor is still moving but nothing else on the GUI is
working any more", that means the X server has not "crashed".
** Summary changed:
- X server crashes after alleged application crash
+ Some wine apps stop responding
** Package changed: xorg-server (Ubuntu) => wine (Ubuntu)
** Changed in: gdm3 (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805699
Title:
System goes to sleep with external monitor and lid closed after login
To
Since removing lkp_Ubuntu_4_15_0_38_41_generic_45 solved the problem
this bug should probably be reassigned to whatever component installed
that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803830
Doug, hardware model numbers don't matter here. Only software version
numbers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805444
Title:
[nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu
Vincent, you are commenting on the wrong bug. Please open a new one
instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798790
Title:
Ubuntu login screen never appears when using the Nvidia
** No longer affects: gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795703
Title:
Ubuntu Dock gets replaced with a standard GNOME one after a while
To manage notifications
What are the approximate power usage numbers you see in watts? (Gnome
Shell vs Unity)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795342
Title:
Higher power consumption when running gnome-shell
** Summary changed:
- gnome-shell filling up syslog with thousands of entries with stack traces
ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
+ gnome-shell filling up syslog with thousands/millions of entries with stack
traces ending in osdWindow.js (lines 206/207 in
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Summary changed:
- Dialog renders at the center of combined monitor space with a multi-monitor
setup
+ Dialogs render at the center of combined monitor space with a multi-monitor
setup
** Tags added: multimonitor
--
You
** Description changed:
+ https://gitlab.freedesktop.org/libinput/libinput/issues/176
+
+ ---
+
I made a fresh install of Ubuntu 18.04 on a thinkPad t450s and t480s. The
trackpoint reacts, especially if i want to move it only a small distance, very
jumpy and erratic.
It is very difficult
Same issue. Ubuntu 18.04 64 bit. Using radeon drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991638
Title:
Crashes when gui is invoked
To manage notifications about this bug go to:
Raul,
Can you please try a much newer (or older) kernel and tell us if that
improves the situation?
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
** Summary changed:
- Touch Screen stop working on 18.04 beta1
+ NextWindows 1900 HID Touchscreen stopped working in 18.04 (recognized as
Sorry, but did I understand that a temporary solution is to downgrade
libmenu-cache to version 1.0.2-2?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782984
Title:
PCManFM crashes frequently on
Going further, for those who are running arch containers in proxmox who
reach here after googling via getting a message similar to this:
[ 2204.273155] audit: type=1400 audit(1548030556.960:100):
apparmor="DENIED" operation="mount" info="failed flags match" error=-13
profile="lxc-101_" name="/"
As I suspected, the error:
Bluetooth: hci0: last event is not cmd complete (0x0f)
is itself not a bug. The only bug is that the error was displayed when
it shouldn't be. So if you have any actual Bluetooth bugs then they
should probably be logged elsewhere. That is according to
** Changed in: hwe-next
Status: In Progress => 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/1807334
Title:
Add support for ALC3277 codec on new Dell edge gateways
To manage
Can someone experiencing this bug please report it to the PulseAudio
developers?
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/new
and then tell us the new bug ID.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no
screens found") from dix_main
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It's probably possible, but is not a priority. And probably difficult to
justify any enhancement request like this being backported to a stable
release. If anyone would like to try then go ahead:
https://wiki.ubuntu.com/StableReleaseUpdates
--
You received this bug notification because you are
I didn't. Someone else did 9 years ago in comment #19.
Also, the original bug was logged against Ubuntu 9.10 which reached end
of life in 2011.
The most recent report of this bug I can see is 17.10, which also
reached end of life in 2018.
If you have any ongoing problems then please open a new
Thanks TJ.
I've submitted the patch to upstream:
https://www.spinics.net/lists/platform-driver-x86/msg17872.html.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811815
Title:
Lenovo ideapad
*** This bug is a duplicate of bug 1793640 ***
https://bugs.launchpad.net/bugs/1793640
Also gutsy and hardy are well past end of life:
https://wiki.ubuntu.com/Releases
So we are now tracking the issue in bug 1793640 instead.
--
You received this bug notification because you are a member
1 - 100 of 287 matches
Mail list logo
