Hi,
Now sometimes it works,
but sometimes conduit close unexpectly when choosing destination folder.
The destination folder is 1st "mounted" via nautilus (I browse an
ssh://hostname/path/to/folder)
In conduit,
I set up a file to folder synch.
I configure the file, and choose juste one file,
the
can't reproduce anymore
Le dimanche 19 octobre 2008 à 08:57 +, Daniel T Chen a écrit :
> Is this symptom still reproducible in 8.10 beta or later?
>
> ** Changed in: gnome-compiz-manager (Ubuntu)
>Status: New => Incomplete
>
--
Cdlt,
Bruno
--
[gutsy] compiz-tray-icon must be laun
can't reproduce anymore.
Le jeudi 16 octobre 2008 à 20:48 +, Daniel T Chen a écrit :
> Is this symptom still reproducible in 8.10 beta or later?
>
> ** Changed in: compizconfig-settings-manager (Ubuntu)
>Status: New => Incomplete
>
--
Cdlt,
Bruno
--
ccsm crashed with AttributeEr
Hi,
I was unable to reproduce this crash with latest updates...
And even the first time, it was really a random crash which has occur
just one time.
Hard to reproduce, so it may be corrected with latest updates, or
not ...
Le jeudi 10 avril 2008 à 13:17 +, Basilio Kublik a écrit :
> Hi the
workaround for auto compiz launch:
i've had to suppress the .config files, it seems there is (was may be
with last updates) a bug with his gnome integration and configuration
process.
the pbl with OAFIID is another bug (gnome?), which seem to be related
with the 3D desktop icon launch pbl.
--
[
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/9041998/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/9041999/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/9042000/ProcStatus.txt
--
gnome-com
Public bug reported:
Binary package hint: compiz
the folowing steps must be done to activate 3D Desktop:
1st launch of compiz-tray-icon : nothing appear
2nd launch of compiz-tray-icon: both windows appears
from here, i can select show icon in tray, but nothing appears
3rd launch of compiz-tray
** Summary changed:
- gnome-compiz-preference must be launched 3 times to activate 3D destkop
+ [gutsy] compiz-tray-icon must be launched 3 times to activate 3D destkop
** Description changed:
Binary package hint: compiz
the folowing steps must be done to activate 3D Desktop:
1st lau
this is gnome-compiz-manager
$ dpkg -L gnome-compiz-manager
/usr/bin/gnome-compiz-preferences
/usr/bin/compiz-tray-icon
$ gnome-compiz-preferences
(gnome-compiz-preferences:8174): libgnomevfs-CRITICAL **:
gnome_vfs_get_uri_from_local_path: assertion `g_path_is_absolute
(local_full_path)' failed
Le mercredi 29 août 2007 à 21:10 +, Travis Watkins a écrit :
> You should not use this tool.
>
> ** Changed in: gnome-compiz-manager (Ubuntu)
> Sourcepackagename: compiz => gnome-compiz-manager
Moreover, ccsm is unable to do anything : all the setting are absolutely
useless/ignored and the 3
the 3D desktop can be sucessfully launch with :
$ /usr/bin/compiz --replace gconf
how the 3D desktop plan to be activated on gutsy ?
*creating a new compiz gdm session ?
*adding the compiz --replace to the existing gnome session ?
As a side effects of this current bug, if I logout/logon,
all t
Another test without using the compiz-tray-icon or compiz-preferences :
1) BOOT
2) GDM Login in gnome session
3D *NOT* OK: logfile .xsession-errors_Fresh_reboot_no3Dfunctional
(processes compiz and compiz.real are launched)
6165 ?S 0:00 /bin/sh /usr/bin/compiz --sm-client-id
defa
Just mousing over 4 times make it crash
--
gnome-panel crashed with SIGSEGV
https://bugs.launchpad.net/bugs/207693
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
Same issue on my side,
more than 48H to sync few meg
same kind of error log
** Attachment added: "syncdaemon.log"
http://launchpadlibrarian.net/49222447/syncdaemon.log
--
Extremely unreliable file syncing, Traceback (failure with no frames):
https://bugs.launchpad.net/bugs/584727
You receive
** Attachment added: "syncdaemon-exceptions.log.2010-05-27_12-42-30"
http://launchpadlibrarian.net/49222514/syncdaemon-exceptions.log.2010-05-27_12-42-30
--
Extremely unreliable file syncing, Traceback (failure with no frames):
https://bugs.launchpad.net/bugs/584727
You received this bug not
** Attachment added: "syncdaemon.log.2010-05-27_12-42-30"
http://launchpadlibrarian.net/49222569/syncdaemon.log.2010-05-27_12-42-30
--
Extremely unreliable file syncing, Traceback (failure with no frames):
https://bugs.launchpad.net/bugs/584727
You received this bug notification because you a
duplicate of Bug #993579
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995397
Title:
lightdm nvidia run in lowgraphic mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
quicker than your reboot:
ctrl alt f1,
logon in terminal
$ sudo /etc/init.d/lightdm restart
here is my sysinfo
** Attachment added: "BM_Sysinfo.txt"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/993579/+attachment/3141640/+files/BM_Sysinfo.txt
--
You received this bug notificatio
same probleme here,
It seems like a running condition between lightdm and nvidia drivers.
sometimes it starts perfectly (less than 10s boot sequence)
sometimes I arrive in the "running in low graphics mode" windows.
workaround: switch to terminal, and just launch a
$ sudo /etc/init.d/lightdm res
Public bug reported:
Seems to be a race condition between ligthdm and nvidia driver.
Sometimes boot is ok,
Sometimes lightdm pop the "running in low graphic mode" session.
none of the options works
but workaround is to switch to terminal, and restart lightdm
for the old style: $ sudo /etc/init.d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995397
Title:
lightdm nvidia run in lowgraphic mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug
manual solution with dconf have done it
manually add all (core_number,'#FF') fix also this crash on my side... but
have to do it for all 12 cores (intel i7 3930)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Crash after connecting 2nd monitor (LCD), 1st one is internal LCD (dell
latitude D620)
seems to work a little, very slowly, high cpu from compiz, and crash
after a while
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Hello,
same for me, seems not fully solved, may be this is a graphic driver
issue.
correction seems to fix the crash (no more crash for the moment), but
graphic is extreemly slow (can see half screen refreshing, each screen
change take 2s for image updating).
compiz process stay at full cpu.
no
Public bug reported:
Binary package hint: compiz
compiz process stay at full cpu.
may be related to bug #761864
no issue at all with only internal lcd (chip intel 945GM intregrated)
came back to normal behaviour once external display is disconnected.
Once 2nd screen connected, the sluggy refresh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/766941
Title:
compiz at 100% cpu when a 2nd monitor is connected
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
yes even total reboot
submit bug report data on bug 766941
the fix seems to have stop the crash, but the problem seems more complex, still
high cpu and very sluggy reshresh (1 to 2s for each frame)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Description changed:
Binary package hint: compiz
compiz process stay at full cpu.
- may be related to bug #761864
+ may be related to bug #761834
no issue at all with only internal lcd (chip intel 945GM intregrated)
came back to normal behaviour once external display is disconnect
Le mercredi 20 avril 2011 à 09:59 +, Sebastien Bacher a écrit :
> thank you for your bug report, does it happen in a classic GNOME
> session?
Hello,
I've just try it and yes same issue on classic gnome session.
manage to crash compiz on this one, send bug data off this classic gnome
session tr
Same issue on my side.
ubuntu 10.10, upgraded from 10.04
in 10.04 no pbl with simple-scan.
no issue with xsane.
seems to be a gtk issue
** Attachment added: "simple-scan-rapport-anomalie.txt"
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/641575/+attachment/1677428/+files/simple-
libcanberra-gtk-module was missing
$ sudo apt-get install libcanberra-gtk-module
has solve this issue.
--
Simple Scan crash just after scanning or during save
https://bugs.launchpad.net/bugs/641575
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
it has solve the issue for basic scan, and save as, but it stills bug if
you try to rotate the image.
** Attachment added: "simple-scan-rapport-anomalie2.txt"
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/641575/+attachment/1677508/+files/simple-scan-rapport-anomalie2.txt
--
Si
crash log on rotation
** Attachment added: "simple-scan-rapport-anomalie4.txt"
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/641575/+attachment/1677633/+files/simple-scan-rapport-anomalie4.txt
--
Simple Scan crash just after scanning or during save
https://bugs.launchpad.net/bug
33 matches
Mail list logo
