Was able to 'solve' the issue through
sudo apt-get purge linux-image-6.5.0-35-generic
reboot # into the 6.5.0-28-generic kernel
sudo apt update;sudo apt upgrade
reboot # into the 6.5.0-35-generic kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
diff /boot/config-6.5.0-35-generic /boot/config-6.5.0-28-generic
3c3
< # Linux/x86 6.5.0-35-generic Kernel Configuration
---
> # Linux/x86 6.5.0-28-generic Kernel Configuration
51c51
< CONFIG_VERSION_SIGNATURE="Ubuntu 6.5.0-35.35~22.04.1-generic 6.5.13"
---
> CONFIG_VERSION_SIGNATURE="Ubuntu
Tried as well in (initramfs) to load the kernel module for lvm and lvm
vgchange -ay but this does nothing in (initramfs) making the system also
not recoverable when starting with the 6.5.0-35-generic kernel
** Attachment added: "showing the last error messages before it drops into
initramfs"
Public bug reported:
Product: Ubuntu 22.04
Component: Kernel 6.5.0-35-generic
Summary: The kernel 6.5.0-35-generic in Ubuntu 22.04 fails to load the
LVM module, causing the root file system to not be found and the system
to boot into (initramfs).
Steps to Reproduce:
Install Ubuntu 22.04 with
This bug happend to me as I had modified my.cnf file instead of puting
the modifications in the mysql.conf.d folder.
a good reminder to always use the .d directories.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Remote machine 100km further away
Computer is updating
End user thinks computer is slow and pulls the power plug from the computer
Turns out computer was updating the kernel
Starts machine
Grub can't find any kernels anymore and drops into Grub CLI
The process of finding the
Here is the machine info from Landscape:
Distribution: Ubuntu 18.04.5 LTS (bionic)
Hardware:
Processor: Intel(R) Celeron(R) CPU N3150 @ 1.60GHz
Memory: 8 GiB RAM
Storage:Model: SanDisk SDSSDX24
Size: 240 GB
Network:Model: Wireless 3160
MAC: f4:06:69:x:x:x
IP:
As recommended by the Gnome-shell developers a bug upstream with Mutter is
opened.
https://gitlab.gnome.org/GNOME/mutter/-/issues/1356
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1356
https://gitlab.gnome.org/GNOME/mutter/-/issues/1356
--
You received this bug notification
Also I'm happy to use a workaround. I'm just a bit disappointed that devilspie
no longer works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888098
Title:
Ubuntu 20.04 gnome-shell places windows
Thank you for your further input Daniel.
The issue is that the stable version of ChromisPOS that I'm using the
source code was destroyed by a commit error.
I'm working together with the developer providing resources to get the
unstable version production ready but that is taking more time than I
Reported this Upstream under
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3011
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3011
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3011
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is interesting. When running gnome-shell in Wayland the window
placement seems to be correct. I've been testing it a bit.
Unfortunately Wayland doesn't allow for remote desktop access so I can't
help my customers when something goes wrong.
--
You received this bug notification because you
Wish me luck, fingers crossed. I'm going to create the issue on Gnome's
bug tracker now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888098
Title:
Ubuntu 20.04 gnome-shell places windows on
@Daniel van Vugt
Thanks for your understanding and advice.
Do you have any recommendations for an alternative window manager that is:
- Officially Supported by Canonical under the support contract
- Touchscreen Friendly
- Secure
- Has a sidebar on the left (the product I sell is designed around
And the cashier side
** Attachment added: "Cashier side of the setup"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394700/+files/Bug1888098_opposingScreensCashier.jpeg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
So you can see what the system looks like when installed
** Attachment added: "Opposing Screens Customer"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394699/+files/Bug1888098_opposingScreensCashier.jpeg
--
You received this bug notification because you
And before anyone starts anything about freeloading.
I donate several thousand euros per year and a lot of my time to open
source projects.
So, let's not go there.
Once again thank you.
I hope that it's much clearer now what is not working as expected in
Ubuntu 20.04's iteration of Gnome
And here is proof that there are no extensions enabled
** Attachment added: "No Extensions enabled"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394697/+files/Bug1888098_ProofAllExtensionsDisabled.jpeg
--
You received this bug notification because you are
Some more fun, the onscreen keyboard follows the misplaced dialog box to
the non-touchable monitor.
** Attachment added: "Screen Keyboard opens on non touchable area"
Here is an extra treat so you can see why block Caribou is very
necessary and the gnome onscreen keyboard implementation makes the
system completely unusable.
** Attachment added: "Extra treat why the block caribou extension was on."
Here is a photo so you can see that the Center New Window option does
nothing. At least it stopped doing the Easter Egg of putting things
halfway between two monitors that's a plus. :D
** Attachment added: "Photo Center new window doesn't do anything"
Thanks for have a new look at this
Oh and I forgot to mention this is with the option
Center New Windows turned ON in Gnome Tweak Tool
Which should theoretically do the same as the DCONF edit line, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Here is a photo so it's easier to understand what the issue is.
** Attachment added: "Photo of the issue faced"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394688/+files/2020-07-21_Bug%20-1888098_GnomeWindowPlacementBug.png
--
You received this bug
Removing the extensions has the same effect.
Block Caribou 36 is necessary as the Point of Sale system (Open source)
already has all the buttons and keyboard that are necessary for the use
of the Point of Sale system. Yet it contains text entry fields which pop
up the on-screen keyboard. There
Public bug reported:
Ubuntu 20.04 LTS
gnome-shell:
Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2
What I expected to happen:
When clicking a button on the primary screen to open a new window in any
application, that window should always open on the same monitor.
What happened instead:
Gnome-shell
Public bug reported:
Ubuntu 20.04 LTS
gnome-tweaks 3.34.0-2ubuntu1
AOC USB monitor
Bus 002 Device 002: ID 17e9:ff10 DisplayLink I1659FWUX
What I expected to happen:
When the USB3.0 Displaylink monitor is plugged in and gnome-tweaks installed
the display remains on and attached as a monitor
There is a workaround via
xinput map-to-output "Weida Hi-Tech CoolTouch® System" eDP-1
There needs to be some kind of detection to do this automatically and
create a systemD systemctl file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here is the xinput list-props while the second screen (AOC) is disconnected
Here the touch works as expected
xinput list-props 11
Device 'Weida Hi-Tech CoolTouch® System':
Device Enabled (169): 1
Coordinate Transformation Matrix (171): 0.50, 0.00, 0.50,
0.00,
There is a regression of this bug in Ubuntu 20.04 using the default Gnome
desktop
Setup is a Shuttle POS P511
using a Weida CoolTouch controller with driver integrated into the Linux kernel
Second screen is a AOC USB-3.1 Display Link monitor without display
capabilities only (no touch).
When
Can confirm that these steps BEFORE REBOOTING lead to a working 18.04
system after the 16.04 upgrade fails.
Maybe these steps could be added to the upgrade script
In psudocode:
if [ error due to systemd1.service ] then;
sudo mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service
Thanks, after loosing 4 terabytes of data due to buggy BTRFS, I moved
away from the file system back to ext4. I still have the machine on a
shelf for the day BTRFS becomes stable or gains recovery tools, so I can
recover and access the data again.
If you want to test this specific case then
Isn't
bluetoothctl
the current alternative to hidd?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/281580
Title:
[Intrepid] New Bluetooth Wizard fails to pair with devices:
reintroduce hidd
To
Done
https://github.com/storaged-project/udisks/issues/723
** Bug watch added: github.com/storaged-project/udisks/issues #723
https://github.com/storaged-project/udisks/issues/723
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The Source code file location where this happens I'm pretty sure is
here:
/src/disks/gduwindow.c
/*
*/
static void
eject_cb (UDisksDrive *drive,
GAsyncResult *res,
gpointer
Public bug reported:
Use case: As a user of hot swap-able SATA disks using a Harddrive Riser
over eSATA. I need a safe, easy and convenient way to remove the hot
swap-able SATA disk without rebooting and without having to go to the
command line.
When attempting to eject an harddisk or a solid
Translation of the Error message to English:
Removal of the medium has failed
Error ejecting /dev/sdi: Command-line `eject"/dev/sdi"' exited with a non-zero
status 1:
eject: could not eject, last error:
Incorrect ioctl() for device
(udisks-error-quark, 0)
So you can see in the error message
So I took over the screen and see that there is a user prompt to
upgrade.
I chose the regular updates which included an update for the unattended
upgrade package.
I'll try to cancel and restart the Landscape process with the new
unattended-upgrade package.
ii unattended-upgrades
Now 14 days into the upgrade. There has been no timeout of the process and it's
still chugging along doing absolutely nothing at all.
(see screenshot)
** Attachment added: "14 days in still no upgrade or timeout"
Still running now 72 hours later with no progress.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853056
Title:
LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no
progress
To
Public bug reported:
LANDSCAPE the licensed version is having troubles upgrading a Disco to
Eoan machine. It's been running for 24 hours with no progress.
Steps to reproduce
* Click on Computers
* Choose the computer to release upgrade
* Click on Packages
* Among the selected computers, 1 can be
Here is the htop output of the machine 24 hours after clicking the
upgrade button in Landscape.
** Attachment added: "HTOP output of the machine"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+attachment/5306325/+files/2019-11-18htopUnattendedUpgrade24hours.png
--
root 1068 0.0 0.5 122408 22240 ?Ssl nov17 0:00
/usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown
--wait-for-signal
root 1125 0.2 0.7 47792 29684 ?Snov17 4:40
/usr/bin/python3 /usr/bin/landscape-client --daemon --pid-file
systemctl status landscape-client.service
\u25cf landscape-client.service - LSB: Landscape client daemons
Loaded: loaded (/etc/init.d/landscape-client; generated)
Active: active (running) since Sun 2019-11-17 20:05:13 CET; 1 day 2h ago
Docs: man:systemd-sysv-generator(8)
Tasks: 8
systemctl status unattended-upgrades.service
\u25cf unattended-upgrades.service - Unattended Upgrades Shutdown
Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled;
vendor preset: enabled)
Active: active (running) since Sun 2019-11-17 20:05:12 CET; 1 day 2h ago
Screenshot showing the lack of progress. Current time of the screenshot
is 22:00 GMT+1
** Attachment added: "24 hours no progress in the upgrade from Disco to Eoan"
I saved one 14.04.5 machine for this purpose.
Will I be able to enabled -proposed for 14.04.5 even though it's now out of
support?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Public bug reported:
What Happened:
When upgrading from 18.10 -> 19.04 about 10 minutes into the upgrade a dialog
box shows up to remove old packages at this point the HDMI output and ssh
servers are disabled so the only way to continue the upgrade is to physically
go to the machine and plug
Public bug reported:
/usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service
Printer is Epson TM-T88V Thermal Roll Receipt printer
indicator-printers-service
Description:Ubuntu 16.04.5 LTS
Release:16.04
indicator-printers:
Geïnstalleerd:
When is the fix going to be released? 18.04.1LTS takes still around 10
seconds to complete after
sudo systemctl start nameofser{TAB}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471723
Title:
This is not fixed at all. Same issues still in kernel 4.15.0-39-generic
see the attached screenshot
** Attachment added: "Screenshot proof of mouse lag and tearing on Ubuntu
18.04.1 LTS"
This issue is also happening in Ubuntu 16.04LTS with backports enabled.
So I think there is something foobar with systemd-resolved and not
resolvconf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So physically at the machine it was only possible to log into the
command prompt. There is no graphical interface available.
To top it off
Network manager was stopped! Not very good for network-manager to be
stopped right after an upgrade.
sudo service network-manager restart
started the
Ok so this is still FUBAR but then on a higher level.
The upgrade failed miserably see the attached file.
I was able to ssh into the machine after the upgrade.
ran dpkg --reconfigure -a as suggested see below
then I tried to reboot. which was a big mistake.
when I try to reconnect to the
One quick little rant.
Landscape is supposed to be Enterprise Grade software. I should be able
to upgrade the releases of an entire farm of machines. This has been
broken since the first time I tried this feature with Landscape.
--
You received this bug notification because you are a member of
I'm going to upgrade a system from 14.04.5 to 16.04.x tomorrow at
10:00AM CEST so I'll let you know the results.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Landscape: Upgrade
Still persists on Ubuntu 18.04. Gnome-shell will not let you right-click
in a java application. Other desktop environments like Unity and
Openbox(LXDE) don't have this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Another thing to note. The stutter (every 5 seconds a freeze frame) is
consistently reproduce-able on Gnome on Ubuntu 18.04 but when you switch
to Unity there is no stutter the video at all. So suspect that Gnome
could also be playing a part in this issue.
** Summary changed:
- video lag
+ video
I have still have two machines that need upgrading from 14.04 -> 16.04 ->
18.04. I want to replace them and test the upgrade in the lab.
The upgrade from 16.04->18.04 also fails. I'll report it in a new ticket.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The workaround to comment out the accessibility.properties does not work
on Ubuntu 18.04.1 using the Unity desktop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788250
Title:
AWT applications fail
Switching to the Official Oracle Java 8 Package was the workaround that worked
for me.
sudo add-apt-repository ppa:webupd8team/java
sudo apt update
sudo apt install oracle-java8-installer
This bug caused downtime. Hopefully it will be given high priority to
fix.
--
You received this bug
Public bug reported:
On Ubuntu 18.04LTS starting and stopping the computer is extremely slow.
SystemD defaults to a start time timeout of 90seconds and a stop time timeout
of 90seconds
in the file
/etc/systemd/system.conf
This is great for huge databased raid systems in some cloud datacenter
I can confirm that Martin Vysny's solution/workaround works in Ubuntu
18.04.1LTS.
(this was not the case in Ubuntu Alpha when I reported this bug)
Please note that you have to reboot (or log-off and logon again) for the
system-monitor to show up in the gnome-tweaks extensions page.
Time to say
Well gnome-shell crashed again and won't let me in again.
whoopsie 35M aug 19 20:51 _opt_minergate_minergate.1000.crash
I've attached a new previous boot
** Attachment added: "new previous boot"
Wrong crash file, oops (blush)
I uploaded the gnome-shell one.
whoopsie 114M aug 19 20:52 _usr_bin_gnome-shell.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787277
Title:
gdm3 freezes
*** This bug is a duplicate of bug 1188569 ***
https://bugs.launchpad.net/bugs/1188569
@Khurshid Alam
Unity is still supported as a community project.
gnome-shell does not work in production for my business as it doesn't
respond correctly to a touchscreen and I can't just stop my entire
So here is the upstream answer:
Window decorations are client-side on wayland, that means they are just another
part of the application window the same way as the products you are viewing. We
cannot tell what parts of the window are decorations, or whether there are in
fact any decorations at
Upstream moved the bug to gtk-pixbuf as they knew of some problems with
ico's in gdk-pixbuf
https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/86
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787294
*** This bug is a duplicate of bug 1188569 ***
https://bugs.launchpad.net/bugs/1188569
The point of this bug is that it happens after an Upgrade.
Something in the Upgrade process is breaking this behavior.
Asking one to do a fresh install is not a reasonable solution.
** Summary changed:
- WindowsXP on a 386 boots faster than Ubuntu 18.04.1
+ Extremely long boot times on Ubuntu 18.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787285
Title:
Extremely long
Reported upstream to the Gnome-shell devs
https://gitlab.gnome.org/GNOME/gnome-shell/issues/493
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787288
Title:
gnome-shell window title bar wastes
BTW> Workaround to the buttons on the right (which only makes sense for right
to left languages ) was to install Gnome-tweak tool.
In Left to Right languages having the buttons on the left means less
mouse travel on high res screens to click the button. This was just good
well thought out and
Here is the Upstream Bug report
https://gitlab.gnome.org/GNOME/gtk/issues/1279
side note: When will Launchpad be updated with rich images and header
templates like the gitlab bug tracker?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I only have the default Ubuntu gnome-shell extensions installed as installing
extensions from some gnome website still seems to me to be an extreme IT
Security risk.
I installed the gnome-tweak tool and lightdm the problem hasn't occurred
anymore unless I try to log in with Wayland.
Wayland
The name of the crash file is
_usr_bin_gnome-shell.1000.crash
I uploaded it with ubuntu-bug
How do I see the bug number it created?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787277
Title:
Here is a copy of journalctl -b-1 > Previous_Boot.log
** Attachment added: "Previous Boot.log"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1787277/+attachment/5176514/+files/previous_boot.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Example of search query that Nautilus refuses to sort.
** Attachment added: "Example of where nautilus is not sorting"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1698351/+attachment/5176511/+files/Selectie_012.png
--
You received this bug notification because you are a member
Here is a PNG of the icon so you can see what it looks like if you are
also on 18.04 with this bug.
I used icotool -x pos.ico
to extract the icons from the .ico file as PNGs
** Attachment added: "PNG version of the icon"
And interestingly enough. Nautilus also displays the preview of the file
as noise.
** Attachment added: "Nautilus also shows the icon as noise."
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+attachment/5176038/+files/Schermafdruk%20van%202018-08-16%2000-36-31.png
--
Public bug reported:
Steps to reproduce
Create an .ico file (for using the same icon between multiple platforms)
create a desktop file linking to the ico file.
here is an example of the one that doesn't work
[Desktop Entry]
Type=Application
Version=0.9.4
Name=ChromisPos
Comment=Chromis Point of
And here is the actual .ico file
** Attachment added: "the pos.ico file referred to by the desktop file"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+attachment/5176037/+files/pos.ico
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Here is a screenshot of the icon in gnome-hell
** Attachment added: "Corrupted Icon"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+attachment/5176036/+files/Schermafdruk%20van%202018-08-16%2000-33-47.png
--
You received this bug notification because you are a member of
Public bug reported:
Steps to reproduce
upgrade from 16.04 to 18.04
Start your desktop with conky
Conky output is corrupted.
see screenshot.
Log out of gnome-hell
Log into Unity
Conky output looks normal.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: conky 1.10.8-1
ProcVersionSignature:
See the screenshot
50px have been wasted here!
On my 1280x1024 production screens for my business 50px is an extra line of
text. Two if I use a smaller font.
I noticed that the Opera browser has figured out a way around this and
hides the unnecessary title bar when maximized. Maybe we can learn
See here in this screenshot. The 50px are used for the Application which
is much more important than gnome-shell.
** Attachment added: "Opera browser gets rid of the title bar when maximized."
Public bug reported:
Steps to reproduce
Start Ubuntu
Login to Unity
Choose logoff
Choose Ubuntu (which should have the label Gnome-hell)
Note this is the only way to get Gnome-hell to start, starting it
directly just shows a black screen and dumps you back to the greeter.
(already created a bug
Public bug reported:
Steps to reproduce
Upgrade from 16.04.5 to Ubuntu 18.04.1
Reboot the computer
The computer takes several minutes to reboot
The computer hangs on a purple screen not even showing the Ubuntu progress logo
Eventually the login screen shows up.
The hardware is
16-core processor
Public bug reported:
Steps to reproduce
Upgrade a Ubuntu 16.04.5 machine to 18.04.1
Install LightDM (gdm3 doesn't allow me to log into my system)
Install Unity (gnome3 won't start after one use)
Try to open a terminal to do anything.
CTRL+ALT+T
Nothing happens.
What should have happend
A
Public bug reported:
Steps to reproduce
Switch to LightDM
Switch to Unity
(gnome wouldn't let me log in so I was looking for the log file)
Open Nautilus
in the search bar type ".log" (without the quotes)
All the log files in your home directory are shown
Click on Name column
nothing happens
click
Public bug reported:
== Release ==
Description:Ubuntu 18.04 LTS
Release:18.04
Ubuntu Gnome desktop
gdm login manager
== Package version ==
vino:
Geïnstalleerd: 3.22.0-3ubuntu1
Kandidaat: 3.22.0-3ubuntu1
Versietabel:
*** 3.22.0-3ubuntu1 500
500
This is still broken in Bionic with landscape-client
The proposed patch does not work.
landscape-client:
Geïnstalleerd: 18.01-0ubuntu3.1
Kandidaat: 18.01-0ubuntu3.1
Versietabel:
*** 18.01-0ubuntu3.1 500
500 http://nl.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Public bug reported:
== release ==
Description:Ubuntu 18.04 LTS
Release:18.04
== package ==
landscape-client:
Geïnstalleerd: 18.01-0ubuntu3.1
Kandidaat: 18.01-0ubuntu3.1
Versietabel:
*** 18.01-0ubuntu3.1 500
500 http://nl.archive.ubuntu.com/ubuntu
Jun 9 18:36:29 machine sshd[10309]: Failed password for root from $EVILIP port
60394 ssh2
Jun 9 18:38:25 machine sshd[10335]: Server listening on 0.0.0.0 port 22.
Jun 9 18:38:25 machine sshd[10335]: Server listening on :: port 22.
Jun 9 18:38:39 machine sshd[10339]: pam_unix(sshd:auth):
Here is Swap usage over 3 days.
** Attachment added: "Swap usage over 3 days"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1776059/+attachment/5151421/+files/Swap_3-day.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Heres a 3-day graph from landscape showing that memory never reaches more that
57 used.
The gap of course being the downtime caused by this bug.
~$ free -h
totalusedfree shared buff/cache available
Mem: 3,8G959M2,0G 28M
Here are the requested log files including the Landscape error
** Attachment added: "kern.log and kern.log.1"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1776059/+attachment/5151369/+files/KernelLogs.tar.gz
--
You received this bug notification because you are a member
Public bug reported:
Every week on Sunday morning one of my Ubuntu 16.04 machines goes into a
non-usable state.
The log file shows the last entry in the log is
landscape-broke[1164]: segfault at 0 ip 0049469d sp
7ffe06803db0 error 4 in python2.7[40+2de000]
All logging stops
Didn't help after all. Plymouth is still using 100% CPU on reboot.
Now trying all the suggestions in
https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1536771
Disabled plymouth in Grub and dpkg-reconfigured it.
--
You received this bug notification because you are
I found the conflict with the eGalax Touch Daemon driver.
I moved the driver startup from /etc/init.d/eGtouch.sh
to userspace as I don't need the touchscreen at login.
The strange thing is I have 17 machines with this configuration and only
one is exhibiting this behaviour with plymouthd
--
I've attached an apport report of the runaway process
** Attachment added: "apport.plymouth.b8ut5mm8.apport"
https://bugs.launchpad.net/lightdm/+bug/1192051/+attachment/5103196/+files/apport.plymouth.b8ut5mm8.apport
--
You received this bug notification because you are a member of Ubuntu
There is a regression of this bug in 16.04.4LTS
Linux computer 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
Codename: xenial
PID USER PR NIVIRTRES
1 - 100 of 229 matches
Mail list logo
