Same boat here. Ubuntu 14.04 64bit. FIle 3.10.1.
Was in the middle of copying files from a cd to the server (via SMB),
used Alt+Tab to switch to a Remmina RDP session. Kind of switched back
and forth too quickly and then had to Alt+Tab again till I got my RDP
session to the forefront. When I went
Me too. :-) Yup, just updated my laptop that's running 14.10. Software
Updater is on the side, I can right click on it and tell it to install
the updates. It even asks for the password, then installs the updates.
But doesn't show a window.
Running it manually works fine.
** Tags added: ui
--
.
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: E2E [ESS ES1978 (Maestro 2E)], device 0: ESS Maestro [ESS Maestro]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: clickwir 1768
Running Kubuntu 14.10 and only have adb 1.0.31. Can't update my Nexus 4
to 5.0.1 because it requires at least adb 1.0.32.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to android-tools in Ubuntu.
Had the same hang. Client is Ubuntu 15.10 and server is 14.04, both up
to date as of today. Fix was to change client MTU from 9000 to 1500.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
*** This bug is a duplicate of bug 1531184 ***
https://bugs.launchpad.net/bugs/1531184
Running 16.04.1 and this fix doesn't seem to make a difference.
Feb 5 10:55:56 ubuntu systemd[1]: dnsmasq.service: Start-post operation timed
out. Stopping.
Feb 5 10:55:56 ubuntu dnsmasq[31933]:
Was going through the regular GUI upgrade process from 16.04, message
kept coming up dozens of times. After clicking CLOSE on about the 20th
one, I just held ENTER until they went away. Upgrade continued, gave a
message at the end that something didn't install right and my system
might be
Would like to have the ability to cleanly remove iscsi related processes
from systems that don't need it.
Sitting there, it's not hard on resources, but I'm trying to shave off
anything I can.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
esg and syslog info as it happened. Attaching those captures.
clickwir@mach:~$ uname -a
Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
clickwir@mach:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Descript
Happened again after just a few minutes of watching. Tried not watching
YouTube for a while and it was fine for about 20 mins.
dmesg
[ 2441.656816] clocksource: timekeeping watchdog on CPU2: Marking clocksource
'tsc' as unstable because the skew is too large:
[ 2441.656819]
econds. Then it stopped and nothing responded.
It did this a few times over the course of an hour. Had to power off
the PC to get a reboot. Last time it did this I ssh'd from another PC
to get dmesg and syslog info as it happened. Attaching those captures.
clickwir@mach:~$ uname -a
Linu
PC to get a reboot. Last time it did this I ssh'd from another PC
to get dmesg and syslog info as it happened. Attaching those captures.
clickwir@mach:~$ uname -a
Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
clickwir@mach:~$ l
this a few times over the course of an hour. Had to power off the
PC to get a reboot. Last time it did this I ssh'd from another PC to get
dmesg and syslog info as it happened. Attaching those captures.
clickwir@mach:~$ uname -a
Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 x86_64
.
clickwir@mach:~$ uname -a
Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
clickwir@mach:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename: artful
Just did a fresh install of 20.04 as a Proxmox VM and see this "invalid
argument" in the start up messages and syslog. Trying to start it
manually also fails. Tried recreating it, also failed.
root@changeme:/# fallocate -l 2G /swap.img
root@changeme:/# chmod 600 /swap.img
root@changeme:/# ls
Fixed my problem.
While looking through /var/log/syslog, I noticed this line around the
same time swap mount failed.
BTRFS warning (device sda3): swapfile must not be copy-on-write
Then a few lines later...
systemd[1]: swap.img.swap: Failed with result 'exit-code'.
systemd[1]: Failed to
FWIW, I still see this on a fresh Ubuntu 20.04 install. My NFS server is
also Ubuntu 20.04.
Linux server01 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
[1129462.984558] audit: type=1400 audit(1592950067.469:72821):
apparmor="DENIED"
17 matches
Mail list logo
