Spoke too soon: the simple workaround is "snap remove gnome-calculator;
snap install gnome-calculator".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768340
Title:
fscrypt does not work for home
Trent Lloyd, did you manage to work around the problem with broken
snaps? Asking because it looks like there's an update for the gnome-
calculator snap that has broken the calculator on my system. Nothing
happens when I run it, and if I run "snap refresh" from the command
line, I get the following
Having used this configuration (with upstream fscrypt) for a week, I'm
finding that some logins are successful while others are not. So there's
still some underlying intermittent issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I built fscrypt from upstream (v0.2.3-8-g3e32282) and this issue no
longer manifests. So whatever bug I'm running into has been fixed
upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768340
Public bug reported:
I am trying to use fscrypt in place of ecryptfs to encrypt my home
directory, and to automatically unlock/lock it on login and logout. I am
using a fresh installation of Ubuntu 18.04 done on 05/01/18. The
hardware is a Dell Precision 5520 laptop. The version of the fscrypt
After restarting my Ubuntu VM, notifications appear to be working
properly. Well, at least I get a notification bubble, and a blue message
envelope, though I'm not seeing the change in the dock's tiny triangle
(item #2 from the list in the bug description).
I noticed that I had a
Will someone be backporting this into raring? #1174936 and #1174740 are
possible duplicates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1177285
Title:
gnome-control-center crashes on
Public bug reported:
The on message receipt notification behavior in empathy is semi-broken.
Just how broken depends on whether I have an open chat window with the
sender.
If the chat window is open:
1. I get a little notification bubble in the top-right corner containing the
name of the sender
I can confirm that Eugene's script yields the same results in my VM as
well:
...
62: ./eugene_script.sh: line 11: 10940 Terminated tail -f
/etc/hosts /dev/null
63: ./eugene_script.sh: line 11: 10943 Terminated tail -f
/etc/hosts /dev/null
64: tail: inotify cannot be
Thanks, Eugene. I had begun putting together a repro case with
pyinotify, but a shell + tail certainly takes the cake.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
Title:
inotify fd leak
Public bug reported:
I'm running Ubuntu 12.04 in a VM. After a recent kernel upgrade, I'm
finding that I can reliably put the system in a position where the
inotify_init() syscall returns -EMFILE, but /proc/*/fd shows fewer
anon_inode:inotify entries than
/proc/sys/fs/inotify/max_user_instances.
** Attachment added: version.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1101666/+attachment/3488366/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
Title:
I should add that when I reboot the system, the problem goes away until
I run my pyinotify unit tests again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
Title:
inotify fd leak
To manage
apport information
** Tags added: apport-collected precise running-unity
** Description changed:
I'm running Ubuntu 12.04 in a VM. After a recent kernel upgrade, I'm
finding that I can reliably put the system in a position where the
inotify_init() syscall returns -EMFILE, but /proc/*/fd
apport information
** Attachment added: AplayDevices.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488369/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
apport information
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488368/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488370/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488371/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488372/+files/Card0.Codecs.codec97.0.ac97.0.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488373/+files/Card0.Codecs.codec97.0.ac97.0.0.regs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488374/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488375/+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/1101666
Title:
apport information
** Attachment added: PciMultimedia.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488376/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488377/+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/1101666
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488378/+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: ProcModules.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488379/+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/1101666
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488380/+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/1101666
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488381/+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/1101666
Title:
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488382/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101666
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1101666/+attachment/3488383/+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/1101666
I enabled -proposed, installed vmmouse with version 1:12.9.0-0ubuntu0.1,
and using xev, verified that there are no motion events when pressing
mouse buttons. Thanks guys!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Johann: can we get an updated xserver-xorg-input-vmmouse package with
that commit reverted? What's the process we need to follow?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996821
Title:
vmmouse
There's a fix for the kernel panic in some of the drm-intel-next
branches (commit 31acbcc408f412d1ba73765b846c38642be553c3).
Note that in my experience DisplayPort is still pretty much broken on
the Natty kernel even with this fix applied.
--
You received this bug notification because you are a
I think this is the same as bug 754146.
There's a fix for the kernel panic in some of the drm-intel-next
branches (look for commit 31acbcc408f412d1ba73765b846c38642be553c3).
Note that in my experience DisplayPort is still pretty much broken on
the Natty kernel even with this fix applied.
--
Public bug reported:
I am running Maverick on a Thinkpad T410s laptop, and my workflow
consists of connecting the laptop to an external Dell 30 monitor with a
DisplayPort cable, disabling the laptop's display, and using the
external monitor exclusively.
On Maverick, this usually works correctly,
Note that this forum post appears to describe the exact same problem I have,
albeit on different hardware:
http://ubuntuforums.org/showthread.php?p=10636426
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: kernel.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/754146/+attachment/1997519/+files/kernel.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/754146
Title:
The kernel log contains two instances of the same oops. I think this
corresponds to when I unplugged the DisplayPort cable.
Apr 7 15:07:55 adar-dev kernel: [ 267.333834] BUG: unable to handle kernel
NULL pointer dereference at 0230
Apr 7 15:07:55 adar-dev kernel: [ 267.336276]
This is a really annoying bug for IRC-using Empathy users. Should it be
filed upstream? Or is this Ubuntu-specific?
--
Typing an input line longer
https://bugs.launchpad.net/bugs/392251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I forgot to mention: I'm running Ubuntu Lucid 10.04 with telepathy-idle
0.1.6-1.
--
Typing an input line longer
https://bugs.launchpad.net/bugs/392251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: GNOME Bug Tracker #587441
https://bugzilla.gnome.org/show_bug.cgi?id=587441
** Also affects: telepathy-idle via
https://bugzilla.gnome.org/show_bug.cgi?id=587441
Importance: Unknown
Status: Unknown
--
Typing an input line longer
Public bug reported:
Binary package hint: autofs5
I have an automount setup containing a large number of NIS-provided
maps, all derived from an NIS-provided master map (yp:auto.master). When
I stop automount using stop autofs, I noticed that some mounts have
been unmounted while a
I forgot to mention that this is with autofs5 in Lucid Lynx, package
version version 5.0.4-3.1ubuntu5.
--
when stopped, automount orphans some mounts
https://bugs.launchpad.net/bugs/578536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've gone ahead and filed an upstream bug.
** Bug watch added: GNOME Bug Tracker #617971
https://bugzilla.gnome.org/show_bug.cgi?id=617971
** Also affects: empathy via
https://bugzilla.gnome.org/show_bug.cgi?id=617971
Importance: Unknown
Status: Unknown
--
empathy tries to
Core dumps aren't going to work because I think our core dumping code is
busted (see the definition of the Panic_Panic if you're curious).
Travis or Martin: could one of you reproduce this crash within gdb and
use symbols to get a more meaningful backtrace? I'm not sure if Ubuntu's
vmware-guestd
Looks like a crash in retrieving information from libdnet, used by the
guestInfo subsystem in guestd.
Could you reproduce the bug and upload the dumped core as well as the
guestd executable containing symbols? You may need to play with 'ulimit'
to allow a core dump to be generated.
--
Works for me, thanks (using a Workstation 6.5 host).
I've found a few other issues, but I'll file separate bug reports for
them.
--
open-vm-source doesn't build
https://bugs.launchpad.net/bugs/278711
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: open-vm-toolbox
There's a small bug in the vmware-user.desktop file supplied with the
open-vm-toolbox package such that the application doesn't automatically
start when a new X11 session is started. The details can be found in the
upstream bug
Public bug reported:
Binary package hint: open-vm-source
The vsock module depends on the vmci module, and in recent kernels
(including those of Intrepid and Jaunty) such dependencies are validated
at build-time by the modpost utility. If one module is built without
seeing the Modpost.symvers of
** Attachment added: modversions.ubuntu.patch
http://launchpadlibrarian.net/19950928/modversions.ubuntu.patch
--
vsock module does not load
https://bugs.launchpad.net/bugs/302230
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Why are all of those packages required for compilation? Isn't open-vm-
source the source package for the kernel modules only? None of the -dev
packages you've mentioned are needed for compiling the open-vm-tools
kernel modules.
--
open-vm-source should recommend installation of packages needed
The new upstream open-vm-tools release (2008.11.18) now provides
dkms.conf which should allow for easy dkms integration. Could someone
more familiar with dkms give this a shot?
--
should build kernel modules with dkms
https://bugs.launchpad.net/bugs/277556
You received this bug notification
I think this bug has been fixed, but as far as I know, Intrepid's open-
vm-source package is still busted because of bug #278711.
--
module-assistant fails to install open-vm-source
https://bugs.launchpad.net/bugs/193606
You received this bug notification because you are a member of Ubuntu
Bugs,
Any sponsors out there listening? Dan requested sponsorship for his bug
fix 10 days ago and it doesn't look like there's been any action towards
getting the package fixed since. This bug renders open-vm-source
unusable on Intrepid, so it would be really nice to see it fixed.
In an effort to make
There's a clean patch for this problem available in the upstream open-vm-tools
bug tracker:
http://sourceforge.net/tracker/index.php?func=detailaid=2071170group_id=204462atid=989708
Or a direct link to the patch:
55 matches
Mail list logo
