Thanks Nate, I've been busy the past few days so I didn't have time to
look into it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100096
Title:
open-vm-dkms 2012.10.14-874563-0ubuntu1: open-vm-too
The package from Nate fixes most compilation errors, except for the
following:
/var/lib/dkms/open-vm-tools/2012.12.26/build/vmhgfs/inode.c: In function
‘HgfsTruncatePages’:
/var/lib/dkms/open-vm-tools/2012.12.26/build/vmhgfs/inode.c:888:4: error:
implicit declaration of function ‘vmtruncate’
[-
I'm seeing the same compilation errors with a fresh and up to date
installation of RR x64.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100096
Title:
open-vm-dkms 2012.10.14-874563-0ubuntu1: open-
I can confirm that the attached patch allows the program to start. The
changes to the configuration file do not apply on a 64-bit machine and
are not necessary to allow the program to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Right clicking by tapping with 2 fingers already works in natty. Click
and drag works with the left button by double tapping, but not by
clicking and dragging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Roman,
1. It does not fix click and drag. There may be a patch at
https://build.opensuse.org/package/files?package=xorg-x11-driver-input&project=X11%3AXOrg&rev=17f381a34750c8d6634d00015d210d0c
that fixes it, but I don't have time the coming days to look at it.
2. I don't know which patch you mea
Hi Paul,
You should get the source files for the version of the synaptics driver
that is in Maverick (1.2.2). You can do this by running 'apt-get source
xserver-xorg-input-synaptics'. The newer version is not compatible with
your kernel.
I attached a patch for version 1.2.2 (on the right side of
My attached patch was added to the right of the screen, it was _not_ the
link I posted. The patch can be found here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/582809/+attachment/1906642/+files/clickpad-1.3.99%2Bgit20110116
.0e27ce3a-0ubuntu7.patch
To use it, do the following:
- get the
Here is a patch based on the patch by Takashi Iwai
(https://build.opensuse.org/package/view_file?file=xf86-input-synaptics-
add-clickpad-support.diff&package=xorg-x11-driver-
input&project=X11%3AXOrg&srcmd5=17f381a34750c8d6634d00015d210d0c).
It is updated to the version of xserver-xorg-input-synap
Just tested it with latest kernel (the build of 21 April), and the
problem still exists there.
** Tags removed: needs-upstream-testing
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bu
apport information
** Attachment added: "WifiSyslog.txt"
http://launchpadlibrarian.net/45015198/WifiSyslog.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
apport information
** Attachment added: "UdevLog.txt"
http://launchpadlibrarian.net/45015180/UdevLog.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: "ProcModules.txt"
http://launchpadlibrarian.net/45015176/ProcModules.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
apport information
** Attachment added: "ProcInterrupts.txt"
http://launchpadlibrarian.net/45015171/ProcInterrupts.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "PciMultimedia.txt"
http://launchpadlibrarian.net/45015167/PciMultimedia.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
apport information
** Attachment added: "Lspci.txt"
http://launchpadlibrarian.net/45015165/Lspci.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
apport information
** Attachment added: "UdevDb.txt"
http://launchpadlibrarian.net/45015177/UdevDb.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
apport information
** Attachment added: "ProcCpuinfo.txt"
http://launchpadlibrarian.net/45015169/ProcCpuinfo.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
apport information
** Attachment added: "Card0.Codecs.codec.1.txt"
http://launchpadlibrarian.net/45015161/Card0.Codecs.codec.1.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bug
apport information
** Attachment added: "IwConfig.txt"
http://launchpadlibrarian.net/45015164/IwConfig.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
apport information
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/45015163/CurrentDmesg.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
http://launchpadlibrarian.net/45015136/Card0.Codecs.codec.0.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bug
apport information
** Attachment added: "Card0.Amixer.values.txt"
http://launchpadlibrarian.net/45015126/Card0.Amixer.values.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/45015125/BootDmesg.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/45015122/ArecordDevices.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/45015120/AplayDevices.txt
--
[Karmic] volume ignored when starting up muted
https://bugs.launchpad.net/bugs/455618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
apport information
** Tags added: apport-collected
** Description changed:
I'm using the Fujitsu Siemens Amilo PI 1536 notebook.
When it boots while the volume is set to 0, it will ignore this and set the
volume to full (this is really irritating).
If the volume is set halfway or full, it
These new versions fix it for me. I don't see any new problems after a
quick restart and hibernate test round.
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification becaus
I can reproduce this by simply touching the file '/forcefsck' and
rebooting.
Killing either 'plymouth quit' or 'plymouth --mode=boot --attach-to-
session' shows gdm again, all though kill 'plymouth --mode=boot
--attach-to-session' spams the terminal with the following message:
'mountall: Plymouth
I also had this issue. When killing plymouth, gdm starts normally
though.
--
Graphical bootstrap hangs on fsck
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/33965792/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/33965793/AplayDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/33965794/ArecordDevices.t
Public bug reported:
I'm using the Fujitsu Siemens Amilo PI 1536 notebook.
When it boots while the volume is set to 0, it will ignore this and set the
volume to full (this is really irritating).
If the volume is set halfway or full, it will adhere to it.
This worked on every Ubuntu up till Karmi
32 matches
Mail list logo
