[Bug 1012277] Re: Closing laptop lid should not blank external monitor

2012-06-21 Thread fsando
I'm experiencing this on a dell xps m1330 laptop with intel integrated
graphics.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1012277

Title:
  Closing laptop lid should not blank external monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1012277/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740218] Re: gnome-applet clock time freezes

2011-04-11 Thread fsando
I have found a way to reliably recreate this bug (or the same result)


Every time I start the editor geany (ppa:geany-dev/ppa) gnome-panel applets 
immediately stop updating. They come to life again if I resize the panel. 

I guess that geany does something that other processes do - whatever
that is.

I made an strace  but I don't know what I would be looking for.

lsb_release -rd
Description:Ubuntu 10.04.2 LTS
Release:10.04

apt-cache policy packagename gnome-panel
gnome-panel:
  Installed: 1:2.30.2-0ubuntu0.2
  Candidate: 1:2.30.2-0ubuntu0.2

uname -mrsv
Linux 2.6.32-30-generic #59-Ubuntu SMP Tue Mar 1 21:30:46 UTC 2011 x86_64

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/740218

Title:
  gnome-applet clock time freezes

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740218] Re: gnome-applet clock time freezes

2011-04-11 Thread fsando
Adding to previous comment:

The issues with geany and gnome-panel first appeared after removal of
mono-runtime (removes tomboy and f-spot), removal of evolution (I have
no agenda, mono-apps and evolution removed because I never use them)

After last post I reinstalled ubuntu-desktop (draws all mono, evolution
etc.), the issue geany persisted. I then completely removed geany and
all plugins. Then reinstalled geany and plugins now the issue has gone.
I can start geany without gnome-panel crashing.

So at one point in time gnome-panel crashed, later - with the same
applications - it doesn't crash. I made an strace with and without crash
which I can post if anyone is interested - don't know if they show
anything useful. I looke at them with a diff viewer and there are only a
few actual differences.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/740218

Title:
  gnome-applet clock time freezes

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 748423] [NEW] drives in tree view appear in seemingly random order with no option to reorder

2011-04-02 Thread fsando
Public bug reported:

Binary package hint: nautilus

System: Ubuntu 10.04  LTS 
Linux serv10 2.6.32-30-generic #59-Ubuntu SMP Tue Mar 1 21:30:46 UTC 2011 
x86_64 GNU/Linux
GNOME nautilus 2.30.1

To reproduce:
Open nautilus, set side pane to Tree

Actual behavior: When side pane is set to Tree drives appear in
apparently random order with no option to change it.

Expected behavior: drives should appear in alphabetical order.


In contrast to this, when drives are opened files in tree view do appear in 
alphabetical order. 
Also in the Places menu drives appear in alphabetical order.

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/748423

Title:
  drives in tree view appear in seemingly random order with no option to
  reorder

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 124440] Re: gnome needs a way to manipulate scroll speed

2011-01-25 Thread fsando
I don't need this often but when I need it I'm seriously surprised that
it's not there.

Is the reason it's missing that xorg makes it too complicated to
implement? If that's the case we must hope really hard for Unity.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/124440

Title:
  gnome needs a way to manipulate scroll speed

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 552157] Re: gnome-search-tool in 9.10 discards configuration when started with --path=

2010-03-31 Thread fsando
Ok, found a solution - don't know if this is a workaround or the
preferred way:

Change the look_in_folder property before calling gnome-search-tool
#
#!/bin/bash
gconftool-2 -s --type=string /apps/gnome-search-tool/look_in_folder 
$NAUTILUS_SCRIPT_CURRENT_URI
gnome-search-tool
#

-- 
gnome-search-tool in 9.10 discards configuration when started with --path=
https://bugs.launchpad.net/bugs/552157
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-utils in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 552157] [NEW] gnome-search-tool in 9.10 discards configuration when started with --path=

2010-03-30 Thread fsando
Public bug reported:

Binary package hint: gnome-utils

gnome-search-tool changed behavior from earlier versions:
discards configuration when started with --path=

Earlier behavior restored by copying earlier version from 8.10 to 9.10

Example with nautilus-scripts
.gnome2/nautilus-scripts/search.here.sh:

In ubuntu 8.10
#
#!/bin/bash
cd $NAUTILUS_SCRIPT_CURRENT_URI
exec gnome-search-tool

#
When starting this script by right clicking it starts in the current directory 
AND remembers all settings

in 9.10 (1)
#
#!/bin/bash
gnome-search-tool --path=$NAUTILUS_CURRENT_URI

#
When right clicking and running this script
Expected behavior:
Start in current folder AND remember all settings
Actual behavior
Starting in current folder BUT all settings forgotten

in 9.10 (2)
#
#!/bin/bash
gnome-search-tool

#
When right clicking and running this script
Expected behavior
Don't know what to expect
Actual behavior
Starts in /home/user AND all settings remembered

Copied gnome-search-tool from 8.10 to 9.10 and expected behavior returned
Copied files:
/usr/bin/gnome-search-tool
/usr/lib//libgnome-desktop-2.so.7.2.4
/usr/lib/libgnome-desktop-2.so.7 (symlink)

** Affects: gnome-utils (Ubuntu)
 Importance: Undecided
 Status: New

-- 
gnome-search-tool in 9.10 discards configuration when started with --path=
https://bugs.launchpad.net/bugs/552157
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-utils in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 93847] Re: Excessive CPU usage by Gnome System Monitor

2010-02-26 Thread fsando
I don't know if this is a clue but it looked very strange:

Some time ago I noticed that every time I checked processes with gnome
system monitor ntop would use a lot of cpu (50-100%). When I killed ntop
system monitor would be killed too! It happened consistently. Eventually
I removed ntop in synaptics. After that system monitor would use 80-90%
cpu and it took several seconds to resize its window. I then reinstalled
ntop and now it runs normal 5-20% cpu, I can kill ntop without side
effect.

Still ntop is apparently started automatically by system monitor
(apparenatly also other *top utilities like atop)

-- 
Excessive CPU usage by Gnome System Monitor 
https://bugs.launchpad.net/bugs/93847
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 173421] Re: In evince (pdf viewer) typing in the search box, whenever typing 'a' open file dialog opens ie. not possible to have 'a' in any search term

2007-12-09 Thread fsando
Thanks a lot for your answer, it solved the problem
I just spend 40 minutes figuring out what it meant, and from the Gnome help:

To change an application shortcut key, open the menu, and with the
mouse pointer on the menu item you wish to change, press the new
combination of keys. To remove a shortcut key, press Backspace or
Delete

I must accidentally have changed the accelerator key, didn't know this
was possible, just changed it back - no bug in Evince :)

-- 
In evince (pdf viewer) typing in the search box, whenever typing 'a' open file 
dialog opens ie. not possible to have 'a' in any search term
https://bugs.launchpad.net/bugs/173421
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 173421] Re: In evince (pdf viewer) typing in the search box, whenever typing 'a' open file dialog opens ie. not possible to have 'a' in any search term

2007-12-02 Thread fsando

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/10690944/Dependencies.txt

** Attachment added: ProcMaps.txt
   http://launchpadlibrarian.net/10690945/ProcMaps.txt

** Attachment added: ProcStatus.txt
   http://launchpadlibrarian.net/10690946/ProcStatus.txt

-- 
In evince (pdf viewer) typing in the search box, whenever typing 'a' open file 
dialog opens ie. not possible to have 'a' in any search term
https://bugs.launchpad.net/bugs/173421
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for evince in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 173421] In evince (pdf viewer) typing in the search box, whenever typing 'a' open file dialog opens ie. not possible to have 'a' in any search term

2007-12-02 Thread fsando
Public bug reported:

Binary package hint: evince

From evince's Help  About:
Evince Document Viewer 2.20.1
Document Viewer.
Using poppler 0.6 (cairo)

My system:
Ubuntu 7.10 on a laptop

When I type in the 'find' box whenever I type an 'a' the 'Open File'
dialog opens which means that it is impossible to search for any term
containing an 'a'.

ProblemType: Bug
Architecture: i386
Date: Sun Dec  2 11:45:33 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/evince
NonfreeKernelModules: fglrx
Package: evince 2.20.1-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/bin/evince
ProcCwd: /home/finn
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
SourcePackage: evince
Uname: Linux finnubuntu 2.6.22-14-rt #1 SMP PREEMPT RT Mon Oct 15 01:05:51 GMT 
2007 i686 GNU/Linux

** Affects: evince (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug

-- 
In evince (pdf viewer) typing in the search box, whenever typing 'a' open file 
dialog opens ie. not possible to have 'a' in any search term
https://bugs.launchpad.net/bugs/173421
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for evince in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 139748] Re: poor handling of eSATA drives

2007-10-20 Thread fsando
I have similar (but worse) experience:
I use feisty on a laptop, I have a Samsung Sata2 drive formatted as ext3 in an 
external usb/esata box. When connected via usb there are no problems. When 
connected as esata via Delock Express Card the following happens:
When hotplugging it is not detected at all ('lshal -m' shows nothing related to 
un-/plugging).
When I cold start with the drive connected I see in '/var/log/dmesg' a lot of 
lines referring to 'ata1' and 'sda1'  they all seem to indicate that the boot 
process tries to get access to the drive but fails. My internal drive which is 
normally mounted as sda is now mounted as sdb. 
Will posting my dmesg with and without connected drive help? If so I can do 
that.

-- 
poor handling of eSATA drives
https://bugs.launchpad.net/bugs/139748
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gnome-volume-manager in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs