I was ready to update with the fact that Kernel 5.9 and 5.10 have seemed
largely stable when the first full release of 5.10, which I had been
running for a while without problems, managed to lock up. For the first
time it has provided an error message that may be useful though. I am
attaching a
I thought I'd better give another update given it has been a while and
I've not returned with the information requested. I've not found the
switch point to provide the bisect output asked for, but I can add some
additional info that may be of help.
Any 5.8 series kernel I have tried from rc1
Thought I'd better give an update on progress from my end. The above
task is proving more of a challenge than hoped (not helped by time out
on customer sites using different hardware).
The stock 5.8 series kernel (linux-image-5.8.0-53-generic) is
reasonably, but not completely, stable. I can
In case it helps narrow down where to look for the issue, I have dropped
back to the stock 5.8 kernel from the linux-image-5.8.0-53-generic
package in 21.04. With the 5.11 (from the standard repositories) and the
5.12 and 5.13rc2 (from mainline) I couldn't manage a day without a lock
up. Usually
No luck with 5.13rc2. I'm attaching another prevboot in case it is of
help.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928600/+attachment/5498738/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498713/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928600
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498712/+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/1928600
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498711/+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/1928600
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498710/+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/1928600
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498709/+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/1928600
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498708/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498707/+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/1928600
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498705/+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/1928600
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498706/+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: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498704/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928600
Title:
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498703/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928600
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498702/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928600
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498698/+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: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498696/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498700/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928600
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498701/+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/1928600
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498699/+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/1928600
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1928600/+attachment/5498697/+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/1928600
Title:
apport information
** Tags added: apport-collected
** Description changed:
With this hardware configuration this issue has been a problem only when
suspending or resuming from suspend under 20.04. Having decided to
upgrade through 20.10 to 21.04 to see if things improve enough to help
Another capture following the lock up immediately after the last.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928600/+attachment/5498495/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This grab wasn't as per the instructions, but was taken as soon as I saw
the request out of personal interest. I'm including it in case it is of
use. It did lead me to the following interesting links, but I've not had
time to see if there is anything useful to try that I haven't already
done yet:
This one was taken as per instructions on the next lock up. Having taken
it, when I was about to attach to this bug report the screen went again.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928600/+attachment/5498494/+files/prevboot.txt
--
You
Tried the 5.12.4-051204 image from the reference link and still get the
lock up - 3 since installing about 4 hours ago (first from suspend and
then twice in attempts to reboot and get working again - in each case
moments after logging in).
Currently running the 5.8.0-53 kernel from the 21.04
lspci output attached. Kernel wise, I'll take a look, but will note that
this has followed me through kernel updates at least with 5.4.x 5.8.x
and 5.11.x kernels from the stock Ubuntu repositories in case that is of
any help. If it is kernel related 5.11.x is significantly worse than the
5.4.x and
** Attachment added: "Lock immediately after logging in following suspend with
X.Org"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928600/+attachment/5498065/+files/lock03.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "Lock when attempting to log in with Wayland"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928600/+attachment/5498064/+files/lock02.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
With this hardware configuration this issue has been a problem only when
suspending or resuming from suspend under 20.04. Having decided to
upgrade through 20.10 to 21.04 to see if things improve enough to help
me identify which package to report a bug against things have
*** This bug is a duplicate of bug 1839380 ***
https://bugs.launchpad.net/bugs/1839380
Public bug reported:
If there is a file or directory of the same name as one being restored
Nautilus will lock up until you force it to quit.
This can be a failed restore which has copied the file but not
** Attachment added: "Screenshot of window with details expanded, prior to
moving to top of screen"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1871080/+attachment/5347687/+files/Screenshot%20from%202020-04-06%2011-23-16.png
--
You received this bug notification
** Attachment added: "Screenshot of window at start where you can see the
buttons"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1871080/+attachment/5347688/+files/Screenshot%20from%202020-04-06%2011-22-30.png
--
You received this bug notification because you are a
Public bug reported:
This has the same symptoms as bug #1072460. I have raised a new bug
report for two reasons, firstly a fix has been released for that bug
report and secondly it is for an upgrade from 12.04 to 12.10 (as
referenced in the description) so the bug is several years old.
The basic
** Attachment added: "Screenshot of window viewing details"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1871080/+attachment/5347686/+files/Screenshot%20from%202020-04-06%2011-23-38.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I've now tested the Microsoft mouse on my desktop computer and the
scroll wheel works find after a suspend / resume, so this looks to be a
clash with the hardware in the laptop - a Lenovo G510.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Updating to 19.10 hasn't fixed the problem, but I have just replaced my
mouse and found the issue is no longer there with the new one. The
original was a Microsoft Wireless Mobile Mouse 1000 (045e:0745 Microsoft
Corp. Nano Transceiver v1.0 for Bluetooth) and the new one is a Logitech
M220
I did not have this problem prior to upgrading to 19.04. The upgrade
process was an upgrade from 18.04 to 18.10 with an immediate upgrade to
19.04 (after a clean reboot), so there was no usage of 18.10 as a
desktop environment to compare with. The 18.04 install was kept up to
date.
I have tested
Public bug reported:
After a resuming from a suspend the mouse scroll wheel is almost, but
not quite, non functional. If you scroll quickly for a while you do get
a slight movement of the scroll bar to show that there is some level of
communication, but nothing remotely usable.
The fix is to use
Public bug reported:
With the default Ubuntu install you cannot snap Files to the side of the
screen on a 1366x768 screen. An application won't snap if it cannot be
resized to half the screen size, and the minimum width of Files is
clearly slightly larger than this.
Adjusting the minimum width
Public bug reported:
The dock sometimes appears on the lock screen, and it is possible to
start a program from the lock screen without logging in when this
happens, although it is not possible to interact with it once it has
started.
I haven't reported it as a security vulnerability because it
I'm getting this several times a day now, so if there is an update I
should notice quite quickly whether it has had an impact. In case there
is a common link I also have other bugs against the mate-dock-applet:
Bug #1715234 - Dock doesn't scroll
Bug #1715236 - Icons never stop flashing
Bug
Public bug reported:
When starting Firefox from the default icon that comes with the dock
applet used by Mutiny a second icon is created for the running
application. The original icon continues to flash. If you click on the
original icon it opens a new Firefox window, whereas the new icon brings
Public bug reported:
With some applications (so far I've seen it with Firefox, Caja and
Telegram [from the flexiondotorg PPA]), the associated icon on the dock
never stops flashing once the application has loaded, and even continues
after it has been closed.
I have noted in the case of Firefox,
Public bug reported:
When adding applications to the dock as used in the Mutiny panel layout
the dock spreads beyond the edge of the screen. Rather than scrolling
through the applications, or bunching them (as per Unity) they simply
spread out until they are longer than the screen height
Public bug reported:
I haven't been able to find any specification of the file name for a
.desktop file, so am working on the basis that anything can be used
before the .desktop extension. When installing the telegram-desktop
package from the 17.10 beta on Ubuntu MATE it creates a .desktop file
On further investigation it would appear the fix is to rename the
.desktop file from:
telegramdesktop.desktop
to:
telegram-desktop.desktop
this seems to fit with the standard used by other applications listed in
/usr/share/applications/ and would get things working with minimal
effort.
--
A bit more info following investigation. When using MenuLibre to
investigate the menu applications Telegram is listed. It is also listed
when using the MATE Menu Editor (mozo). It doesn't, however show in the
menus - Brisk Menu, Main Menu (The Main MATE Menu) or MATE Menu
(Advanced MATE Menu).
Public bug reported:
I haven't been able to test this in the standard Ubuntu release desktop
(the new Gnome variety), but there is no entry in any of the available
menu tools in Ubuntu MATE 17.10 (latest beta). It also doesn't show as a
running application in any of the panels or Mutiny Dock (on
Not sure how much help it will be, but I keep getting redirected to this
bug as already having been reported and each time I've been quietly
minding my own business doing something completely unrelated to the dock
- this time reading a web page in Firefox. I presume it is doing
something in the
A quick extra bit of info; you can clear the problem by logging out and
back in again, no need for a full reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676901
Title:
Multicoloured borders
Public bug reported:
This only seems to happen after the computer has suspended and resumed,
but then remains until a full reboot has been performed. I have this on
two computers, although they do have identical hardware specs (bar
memory and different make graphics cards with the same GPU).
To fix this you need to uninstall the steam-launcher package:
sudo apt remove steam-launcher
remove repo.steampowered.com from your sources and then install the
steam package from multiverse:
sudo apt install steam
Once you've done this, run Steam and let it sort out its
install/update/etc.,
I spotted that BIOS update yesterday, somewhat annoyed that I missed it
as I've been waiting for one since I got the laptop (problems with
suspend and resume that seem to be related). I thought I would get
update notifications from Lenovo the same as I do from HP, but there you
go. I have now
Public bug reported:
Every time I use LibreOffice and try to resize the window (which starts
as full screen) Xorg produces a segfault and returns me to the login
screen. This is easy to reproduce and is not document dependent - it
happens with a blank document in any of the LibreOffice
I hope it will be pushed upstream, I'm not in a position to do anything
about that though. I've looked for a way to modify the bug to indicate
that there are security implications to it, but haven't found anything
yet. It would be a shame if you can only state that on logging the bug.
--
You
I hope it will be pushed upstream, I'm not in a position to do anything
about that though. I've looked for a way to modify the bug to indicate
that there are security implications to it, but haven't found anything
yet. It would be a shame if you can only state that on logging the bug.
--
You
I've done some investigation into this and I'm not sure that the
description is quite accurate, at least not for my situation anyway.
Having just built a new server and ssh'd into it on a non-standard port
with no problem I've done a bit of playing and found that the problem
seems to present
I've done some investigation into this and I'm not sure that the
description is quite accurate, at least not for my situation anyway.
Having just built a new server and ssh'd into it on a non-standard port
with no problem I've done a bit of playing and found that the problem
seems to present
Public bug reported:
The following packages have unmet dependencies:
libreoffice-base: Depends: libreoffice-core (= 1:3.5.4-0ubuntu1.1) but
1:3.5.7-0ubuntu4 is to be installed
Depends: libreoffice-base-core (= 1:3.5.4-0ubuntu1.1) but
1:3.5.7-0ubuntu4 is to be installed
This problem has just got worse for me. There was a brief period where
the dual screen setup was completely broken (i.e. I only got a single
screen with the same setup), but before I got the chance to investigate
an update fixed things (sorry!). I now have better control of the
screens in the AMD
Stephen Birch: Yes that is the same problem, I have just uploaded my
screencast to Youtube - http://www.youtube.com/watch?v=M8TsiS88YDc - my
screens are set the opposite way to yours (i.e. not default I had to
swap them in the xorg.conf file)
Gerry Boland: I can't see it being intended
Public bug reported:
When running a dual screen setup with the launcher set to autohide the
cursor jumps across to the left side of the screen as soon as the mouse
moves it from the right monitor to the left one. If you move slowly it
will sometimes stay in place, and if you disable the autohide
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986835
Title:
Cursor jumps to left side of screen when moving from right to left
monitors
To manage notifications about this bug go to:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922574
Title:
unity-panel-ser segfaults when volume control accessed
To manage notifications about this bug go to:
Public bug reported:
The following two lines are from two instances of this, which is 100%
repeatable simply by moving the mouse over the volume icon in the unity
panel.
Jan 27 13:01:55 orca kernel: [ 2771.859725] unity-panel-ser[3348]: segfault at
10 ip 002b2ee6 sp bf8f7690 error 4 in
I should have added that this started immediately after
libgtk-3-bin:i386 (3.2.0-0ubuntu3, 3.2.0-0ubuntu4) was updated when I
installed it on Start-Date: 2012-01-24 15:06:16, so there is clearly a
change in this package that is triggering the fault.
--
You received this bug notification because
I've done a clean install which automatically used the STA driver and
had this problem. I then disabled it and tried the firmware-b43-lpphy-
installer package only to have the same problem. If I disable wireless
completely, either using the BIOS or the switch on the front everything
works fine. I
Is there a fix for 10.04 LTS, which only runs 2:3.4.7~dfsg-1ubuntu3.4? I
don't often reboot my server, but invariably forget to check that nmbd
is running when I do!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
Is there a fix for 10.04 LTS, which only runs 2:3.4.7~dfsg-1ubuntu3.4? I
don't often reboot my server, but invariably forget to check that nmbd
is running when I do!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Take a look at bug #663670
(https://bugs.launchpad.net/ubuntu/+source/papyon/+bug/663670). There's
a good chance it is the same issue. Do you get a message along the lines
of Cannot Connect with No Reason Specified?
Basically try finding the file:
RequestMultipleSecurityTokens.py
which is in
To combine those last two comments, instead of using:
rm -rf /var/lib/ureadahead
I went for:
mv /var/lib/ureadahead /.ureadahead
which took an existing debugfs directory with it. That was the only
content of the directory at the time. Other than that it all seems to be
working fine, although
I'm suffering the same problems on my HP Mini 2133. Sound would drop out
after a suspend and resume sometimes on 9.10, but I've only noticed the
logged errors since upgrading to 10.04. The original install was UNR
9.04.
--
hda-intel spurious response messages and intermittent GDM startup with
I have a very similar problem to this in that the low battery is
reported immediately the power is disconnected. Thankfully in my case
the machine doesn't go as far as powering down. The machine is an HP
Mini 2133 netbook that was installed with 9.04 UNR and has been upgraded
through 9.10 through
Finally managed to get at the hardware again to test 9.04 against it and
works fine (as far as the ITE controller card is concerned anyway), so
although I can't speak for the 8.04 or 8.10 releases, 9.04 has fixed the
problem. I've also tested this with the same model controller card on
different
Apologies for not updating on this, although there isn't really anything
to update on it, I was waiting for some additional input and sadly the
machine ended up running Windows (although the partial Ubuntu install is
still present). Sorry Martin for not replying to your comment sooner,
Public bug reported:
Binary package hint: debian-installer
To reproduce this you will need to install Gutsy onto a HD that is
connected off a controller with an ITE8212 chipset. In this case the
controller is on a PCI card not on the motherboard, I have no way of
telling whether this is related
79 matches
Mail list logo
