I had this repeating on my system even with Maverick. The system is one
upgraded from Lucid. Would it be possible that the gwibber is still
using the wrong database? Disabling gwibber did help. Also, I think this
is a recent problem that has not appeared during the time using Lucid.
--
Gwibber
Axel: I tested the head of that repository. The output I am getting
seems a little bit concerning.
What I did:
$ sudo apt-get install mercurial libfile-slurp-perl libtext-template-perl
$ hg fetch http://noone.org/hg/xen-tools/
$ cd xen-tools
$ sudo make install
$ sudo xen-create-image --hostname
I take that back. It was obviously something wrong with verbosity. If
the /etc/xen directory is missing, there is no clear output.
--
xen-tools is not available in lucid
https://bugs.launchpad.net/bugs/538917
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** This bug is no longer a duplicate of bug 146859
No dri (and therefore no compiz) for virtual screen greater than 2048x2048
--
[GM45] Compiz does not start when resolution is more than 2048
https://bugs.launchpad.net/bugs/372741
You received this bug notification because you are a member of
I reopened a bug #372741 for GM45 which I marked as duplicate before.
--
No dri (and therefore no compiz) for virtual screen greater than 2048x2048
https://bugs.launchpad.net/bugs/146859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This works for me with the patch 103 re-enabled in mesa. However it
appears from bug #146859 and bug #359392 that this patch has side
effects for some other chips.
I have re-enabled the patch 103 in the latest package from proposed in
my PPA: https://launchpad.net/~ferrix/+archive/ppa
** Package
*** This bug is a duplicate of bug 146298 ***
https://bugs.launchpad.net/bugs/146298
I know exactly what you are saying but the case is that we have in our
hands a fix that does work on several configurations and on others it
does not. So in this bug I am suggesting that, if easily done, we
*** This bug is a duplicate of bug 370777 ***
https://bugs.launchpad.net/bugs/370777
Confirmed. Fixed the problem for me.
--
Virtual Screen Size ignored in Xubuntu
https://bugs.launchpad.net/bugs/372598
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I am having this problem (again). I had it fixed some time ago by a
combination of packages I do not remember but an official update broke
it.
* The screen becomes cropped from the 2048th pixel.
* It is impossible to cross the limit with mouse unless it is crossed first by
a window.
Currently
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Compiz does not start when the resolution is above 2048 in either
direction. This behavior has changed in a recent patch where the area
above 2048 would not be drawn correctly (and there is a fix for that
too).
Affected version:
I was able to repeat this earlier but currently with xserver-xorg-video-
intel 2:2.6.3-0ubuntu9.2.
This has never occured to me when using xrandr from command line.
--
[GM45, 945] Unable to mirror to external monitor
https://bugs.launchpad.net/bugs/368518
You received this bug notification
Does moving a window across the border enable the mouse to enter the area?
Are you using compiz?
--
[gm45] [jaunty] intel xrandr dual head auto config only configures part of one
screen on Dell Lattitude E4300
https://bugs.launchpad.net/bugs/358315
You received this bug notification because you
Obviously the change that fixed this for me has been rolled back. I can
confirm that it did not cause a hang on GM45 and I suggest that the
patch would be restored conditionally for chips having no problem with
it.
--
No dri (and therefore no compiz) for virtual screen greater than 2048x2048
** Changed in: mesa (Ubuntu Jaunty)
Status: Fix Released = Confirmed
--
No dri (and therefore no compiz) for virtual screen greater than 2048x2048
https://bugs.launchpad.net/bugs/146859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 146859 ***
https://bugs.launchpad.net/bugs/146859
** This bug has been marked a duplicate of bug 146859
No dri (and therefore no compiz) for virtual screen greater than 2048x2048
--
[GM45] Compiz does not start when resolution is more than 2048
@aporter: I don't know where the rumors and hunches come from. It is
true that I run out of memory before achieving 4096x4096 resolution but
that results in a decent error message.
I have made the rolled back feature available in my PPA:
https://launchpad.net/~ferrix/+archive/ppa
The patch is
Public bug reported:
When I receive mail where the sender is of the form Lastname,
Firstname and the last name contains Finnish umlaut letters ä and ö,
the sender is parsed into simply Lastname.
Example:
Järvinen, Jukka j...@j.com is shown as:
Message window: Järvinen and Jukka j...@j.com
** Package changed: evolution (Ubuntu) = thunderbird (Ubuntu)
--
Thunderbird splits email addresses with non-ascii characters and a comma in
From: field
https://bugs.launchpad.net/bugs/369150
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I filed the bug into upstream as well:
https://bugzilla.mozilla.org/show_bug.cgi?id=490689
It appears that I was wrong about the case sensitivity. Reproducing this
requires only an escaped letter, a comma and no quotes.
** Bug watch added: Mozilla Bugzilla #490689
This happens also to me also.
(Reading database ... 141359 files and directories currently installed.)
Preparing to replace base-files 5ubuntu3 (using
.../base-files_5ubuntu4_amd64.deb) ...
Unpacking replacement base-files ...
dpkg: error processing
Solved it actually. When something is mounted on /mnt unpacking fails. I
am not sure if the mount needs to be irresponsive at the time (I had a
disconnected samba mount).
This error isn't obvious and clearly it shouldn't matter if something is
mounted on an existing directory while we are trying
This is what I got when I updated my Hardy.
Setting up mono-gac (1.2.6+dfsg-6ubuntu3) ...
* Installing 1 assembly from libgmime2.2-cil into Mono
* Installing 4 assemblies from libmono-addins0.2-cil into Mono
* Installing 2 assemblies from libmono-addins-gui0.2-cil into Mono
* Installing 1
This still happens.
Here's a snippet from my crypttab.
--- 8 ---
sdd2_crypt /dev/disk/by-uuid/bd3d4b37-5b8d-4ad6-a21c-c52115c77f88 none luks
--- 8 ---
With kernel revision 8, I don't get an error but with revision 16 the
initramfs reports that the specified file is not found.
Here's the lspci output for a reference. This setup works perfectly with
TwinView configured. Compiz or something prevents nvidia-settings from
working, but that has been the case for previous versions as well.
** Attachment added: lspci output for the record.
Didn't work a bit. I had to fall back to the previous versions. I
attached the xorg log file.
My graphics adapter is a Gigabyte GeForce 8600GT on an ASUS P5K-V
motherboard.
** Attachment added: This is the log generated by any configuration
http://launchpadlibrarian.net/11158307/Xorg.0.log
My lshw for more information.
** Attachment added: lshw output
http://launchpadlibrarian.net/11158378/lshw.txt
--
[hardy] Enabling xinerama crashes X
https://bugs.launchpad.net/bugs/179822
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Public bug reported:
I updated to Hardy and my dual head configuration that worked perfectly
on Gutsy started crashing. An automatically set up configuration worked
okay when I removed xorg.conf and by merging the configurations I found
that activating Xinerama was the cause. TwinView works like
I updated to version 1.0.15rc3. I packaged using the 1.0.14-1ubuntu2
patch and it worked as is. I haven't checked on any other cards but it
works as a first aid for D630. The packages for amd64 and
2.6.22-12-generic kernel can be found in the URL below.
Public bug reported:
Binary package hint: acpi-support
In Feisty (and everything previous as far as I know) I had a problem
with my Dell Latitude D610. The LCD doesn't come up after I open the
lid. A double switch makes things only worse. According to some
reference I cannot remember there is a
Public bug reported:
Binary package hint: acpi-support
In Feisty (and everything previous as far as I know) I had a problem
with my Dell Latitude D610. The LCD doesn't come up after I open the
lid. A double switch makes things only worse. According to some
reference I cannot remember there is a
Has anyone actually implemented a driver so far? I won my camera from
Microsoft and the best use I can guess is using it in Linux.
--
Microsoft LifeCam VX-6000 High Definition Webcam doesn't work at all.
https://bugs.launchpad.net/bugs/56171
You received this bug notification because you are a
31 matches
Mail list logo
