Public bug reported:
Binary package hint: ubuntuone-client
Ubuntu One crashed on pressing connect upon starting pc. Got error
report saying that ubuntu one crashed and alert to report it.
ProblemType: Bug
.home.mewt..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
** Attachment added: .home.mewt..cache.ubuntuone.log.oauth.login.log.txt
http://launchpadlibrarian.net/41815099/.home.mewt..cache.ubuntuone.log.oauth.login.log.txt
** Attachment added:
.home.mewt..cache.ubuntuone.log.syncdaemon.exceptions.log.txt
** Attachment added: lspcivvnn.log
http://launchpadlibrarian.net/35652118/lspcivvnn.log
--
inverted colours when using X Window System (X11/XShm/Xv)
https://bugs.launchpad.net/bugs/481371
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: dmesg.log
http://launchpadlibrarian.net/35652125/dmesg.log
--
inverted colours when using X Window System (X11/XShm/Xv)
https://bugs.launchpad.net/bugs/481371
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/35652245/Xorg.0.log
--
inverted colours when using X Window System (X11/XShm/Xv)
https://bugs.launchpad.net/bugs/481371
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I never edited this myself since everything worked out of the box...but
im attaching jsut for the sake of having it here
** Attachment added: xorg.conf
http://launchpadlibrarian.net/35652398/xorg.conf
--
inverted colours when using X Window System (X11/XShm/Xv)
Public bug reported:
Hi,
After the upgrade from 9.04 to 9.10, colours in movies playing in totem
or vlc or anything else are appearing as inverted when using X Window
System (X11/XShm/Xv) as output plugin. If I change the output plugin
from gstreamer-properties to X Window System (No Xv),
Public bug reported:
Binary package hint: compiz
Just upgraded to Gutsy and have since been experiencing system lockups.
Machine had to be turned off in 3 separate instances.
Symptons: Usually occurs during high cpu load. Several applications were
open including gcolor2, firefox3b5, eclipse
Public bug reported:
Binary package hint: compiz
After the latest update, Compiz is crashing very frequently.
I have attached the bug report generated by compiz itself to help solve
this problem
** Affects: compiz (Ubuntu)
Importance: Undecided
Status: New
--
compiz crashes
** Attachment added: crash report
http://launchpadlibrarian.net/907/compiz-crash
--
compiz crashes after update
https://bugs.launchpad.net/bugs/150743
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
fixed with above instructions...thanks
--
black tooltips
https://bugs.launchpad.net/bugs/141254
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
editing file fixes it great..thanks :D
--
cannot install new version of update-notifier: gconf schema problem
https://bugs.launchpad.net/bugs/150680
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I will try to delete my folder once i get home and see if that fixes
it..
--
F-spot fails to load - Can't get a connection to the dbus..trying again
https://bugs.launchpad.net/bugs/140006
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
deleting the f-spot folder fixed it for me 2...must be something gone
wrong during upgrade as i had never used f-spot before and only ran it
first time after my upgrade to gutsy
--
F-spot fails to load - Can't get a connection to the dbus..trying again
https://bugs.launchpad.net/bugs/140006
You
yes of course:
[EMAIL PROTECTED]:~$ sudo service dbus start
[sudo] password for mewt:
* system message bus already started; not starting.
[EMAIL PROTECTED]:~$
restarting dbus also didnt help the problem..Im currently upgrading some
packages again (1 of which is f-spot) will report
Updated to latest version of f-spot
[EMAIL PROTECTED]:~$ sudo apt-cache show f-spot | grep -i version
[sudo] password for mewt:
Version: 0.4.0-0ubuntu2
problem still persisting
--
F-spot fails to load - Can't get a connection to the dbus..trying again
https://bugs.launchpad.net/bugs/140006
Im still getting this bug...Network manager says that no network cards
are found..I have to right click and disable networking and then re-
enable it before it takes an ip address from my local dhcp server
--
network-manager doesnt connect me at startup anymore
Public bug reported:
Binary package hint: f-spot
On trying to load F-spot (first time use, never used it before) It fails
to load. when ran from a terminal the following was printed out:
[EMAIL PROTECTED]:~$ f-spot
Initializing Mono.Addins
Starting new FSpot server
/home/mewt/.gtkrc-2.0:1
for nothing
Mewt
** Affects: linux-restricted-modules-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
nvidia-glx-new installs 386 kernel
https://bugs.launchpad.net/bugs/137758
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
might have been i had it uninstalled..but then again i think such a prob
should be fixed by having the appropriate linux-restricted modules
installed, not get a new one according to the kernel getting installed
--
nvidia-glx-new installs 386 kernel
https://bugs.launchpad.net/bugs/137758
You
doing a manual install of the nvidia driver is the only way which allows
me to enter gui right now...and i still need to reinstall the driver
after every restart
--
nvidia kernel module has version mismatch with nvidia xorg module
https://bugs.launchpad.net/bugs/107646
You received this bug
HI,
I was using nvidia-glx-new, I only reverted to the manual installation
as I needed to use the graphical interface...anyhow..your hint about
/etc/default/linux-restricted-modules-common made me check that file and
i added nv as one of the modules to not be loaded at startup and i
Sure here comes:
Xorg.0.log
** Attachment added: Xorg.0.log
http://librarian.launchpad.net/7378962/Xorg.0.log
--
nvidia kernel module has version mismatch with nvidia xorg module
https://bugs.launchpad.net/bugs/107646
You received this bug notification because you are a member of Ubuntu
** Attachment added: xorg.conf
http://librarian.launchpad.net/7378969/xorg.conf
--
nvidia kernel module has version mismatch with nvidia xorg module
https://bugs.launchpad.net/bugs/107646
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Attachment added: dmesg.txt
http://librarian.launchpad.net/7378972/dmesg.txt
--
nvidia kernel module has version mismatch with nvidia xorg module
https://bugs.launchpad.net/bugs/107646
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
[EMAIL PROTECTED]:~$ dpkg -l nvidia-\* | grep ii
ii nvidia-glx-new 1.0.9755+2.6.20.5-15.20 NVIDIA binary XFree86
4.x/X.Org 'new' driver
ii nvidia-glx-new-dev 1.0.9755+2.6.20.5-15.20 NVIDIA binary XFree86
4.x/X.Org 'legacy' dri
ii nvidia-kernel-common
I wonder why when i do lspci | grep -i nv, the card is detected as a
6600gs :S when it's an 6800 :S
--
nvidia kernel module has version mismatch with nvidia xorg module
https://bugs.launchpad.net/bugs/107646
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
] wrote:
mewt:
You've been conned into buying a fake! :P
OK seriously, that can happen due to simple mislabeling. It could be the
database of device IDs is incorrect or the card itself simply has the
wrong identity set in its BIOS. I think it's the former because the
binary nvidia driver seems
** Attachment added: linux-restricted-modules-common
http://librarian.launchpad.net/7379425/linux-restricted-modules-common
--
nvidia kernel module has version mismatch with nvidia xorg module
https://bugs.launchpad.net/bugs/107646
You received this bug notification because you are a member
Public bug reported:
I have just upgraded to feisty and I am having some problems with X. on
first installation of both of nvidia-glx, nvidia-glx-new and the manual
drivers from nvidia.com x works well...however on reboot x fails to
start giving the error that there is an API mismatch between the
30 matches
Mail list logo
