Anyone who has an rsync that supports the xxh128 hash using the xxhash
0.7 library did something very bad in their build. An rsync compiled
with that library only supports xxh64 & xxh32. Thus, this described
mismatch never occurs in a stock rsync (the 128-bit hash was unstable in
xxhash 0.7, and
To be clear, if you have xxhash 0.7 and "rsync -V" reports xxh128 in the
checksum list, fix the rsync build by getting rid of any patch that
enabled that unsupported hash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That said, of course, 0.8.0 is the better choice for the most possible
features (if it is available).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934992
Title:
rsync 3.2.x in Groovy depends on
You misread my comments. It's only the 128-bit hash that depends on
0.8.0. The 0.7 version works fine with rsync, giving it the 64-bit and
32-bit hashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
).
I now use a chromebook with a crouton chroot to get the first acceptable
3d-accelerated linux I've ever used (and I've used both nvidia and amd over
the years).
..wayne..
On Thu, Jan 9, 2014 at 11:51 AM, Christopher M. Penalver
christopher.m.penal...@gmail.com wrote:
Wayne Davison, this bug
It can easily work on both sides. e.g.:
nocache rsync -aiv --rsync-path='nocache rsync' /src/ host:/dest/
The --rsync-path option tells the remote side it should also use nocache
wrapper.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
It can easily work on both sides. e.g.:
nocache rsync -aiv --rsync-path='nocache rsync' /src/ host:/dest/
The --rsync-path option tells the remote side it should also use nocache
wrapper.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Sadly, this feature makes middle clicking (on things like browser links,
etc.) very flaky -- clicks go ignored quite often. I used gpointing-
device-settings to turn the feature off, but a reboot had it go enabled
once again, and I had to toggle the gpointing-device-settings checkbox
back on and
Public bug reported:
The change in bug #554984 (enabling trackpoint scrolling by default) has
made middle-clicking very flaky in oneiric. I am using the latest
updates of oneiric in a new install. My computer is a Lenovo T510, but
since the issue is caused by a new setting in
Public bug reported:
I'm using the Unity 2D login option on my Lenovo T510 which is
configured in the bios to use just the discrete NVidia graphics:
01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M]
(rev a2)
If I configure an external monitor (using nvidia-settings) and
There needs to be a way to just turn the screensaver off. It is so
annoying to have the screen go black just trying to watch a video. (Or
to have to jiggle the mouse every 10 minutes.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For those experiencing this bug, here's an easier work-around when
coming out of suspend:
Press Alt-F2 and type compiz --replace and press Enter. That will get
rid of the corruption and let you continue using your programs.
--
You received this bug notification because you are a member of
Looks like the unity bug regarding this issue has a fix committed:
https://bugs.launchpad.net/unity/+bug/676166
FYI, I always use compiz --replace as my fix after resume.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Starting up the various libreoffice utilities using the lo* script names
(e.g. lowriter, localc, etc.) outputs a warning about the deprecated
single-dash option used in the helper script. These script should be
changed to add an extra dash.
For instance:
$ lowriter
Warning:
I revisited this issue recently, and discovered that I have to use the
nvidia-settings program to get dual screen going with the proprietary
display driver, since xrandr doesn't work. So, once I discovered that,
I simply configured my 2nd display as a Separate X Screen (in the
Configure popup)
Public bug reported:
I have my computer configured to use Intel graphics at present, due to
how buggy dual monitors are with the nvidia graphics:
00:02.0 VGA compatible controller: Intel Corporation Core Processor
Integrated Graphics Controller (rev 02)
I have a 2560x1600 monitor positioned to
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753611
Title:
WARNING: at /build/buildd/linux-2.6.38/net/sched/sch_generic.c:256
dev_watchdog+0x213/0x220()
--
ubuntu-bugs mailing list
What session are you using when you login? The Classic Desktop one w/o
No Effect? Or the Ubuntu Desktop one? Also, verify that your
xorg.conf still mentions the nvidia driver. I have no problem getting
effects going, I just can't get multiple monitors going.
--
You received this bug
I have a T510, and the nvidia driver loads fine for me (I'm testing the
latest Natty). I do have the Display changed in the BIOS to tell the
system that I have the nvidia graphics (Discrete) rather than Optimus.
Maybe your BIOS is set to Optimus?
However, once I have the nvidia driver going, the
Public bug reported:
Binary package hint: gdm
In the gdm selector for choosing the session type, there is the text
Ubuntu Classic Session (no effect) which would be better written as
Ubuntu Classic Session (no effects) or Ubuntu Classic Session
(effects disabled). The phrase no effect denotes
Fuy: what happens if you logout and back in after adding the second
monitor?
For me, I had setup my 2nd monitor in a classic session, with my
1920x1200 external monitor to the left of my laptop's 1400x1050 monitor
(aligned at the top). I then logged into a unity session, and saw the
unity
** Attachment added: External (larger) monitor on the right of laptop
(smaller) screen.
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/661450/+attachment/1887806/+files/ext-right.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I haven't seen this in ages, so the newer Ubuntu releases apparently
have this fixed.
--
corrupts the terminal
https://bugs.launchpad.net/bugs/88987
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Jaunty has glipper 1.0, which is based on their python rewrite of the C
source. I just looked at their python code, and it has logic in it to
avoid forcing a text value when there is a binary object on the
clipboard (which is what my C patch did that they incorporated into the
C version).
My changes made it into the CVS version of glipper (with a couple
strange omissions that I need to ask them about). But that does mean
that the maintainers of glipper approve of the method used in the patch.
--
Glipper makes copy/pasting of images in OpenOffice impossible
I have created a patch for glipper 0.95.1 that fixes this problem as
several others that I discovered. If anyone is interested, you can grab
it here:
http://opencoder.net/glipper-fixes.patch
It mentions all the fixes at the start of the patch. (I also reported
this to the glipper project on
For those wanting to build the package, this command will install the
build-dependencies:
apt-get build-dep glipper
I added a change to the debian/changelog to the patch to make it
easier to build a new .deb package from the source (and the patch now
requires the -p1 option, not -p0). For
This bug is caused by some incorrect logic when the checkClipboard()
function calls the processContent() function (both in src/main.c). If
the call to gtk_clipboard_wait_for_text() returned a NULL (because the
clipboard item could not be changed into plain text), the NULL gets
passed to
This is happening to me too. Very freaky to have the whole screen
switch into kanji, or corrupt in weird ways.
** Changed in: aptitude (Ubuntu)
Status: Unconfirmed = Confirmed
--
corrupts the terminal
https://bugs.launchpad.net/bugs/88987
You received this bug notification because you
29 matches
Mail list logo
