Hi all,
After having debugged an issue of not being able to configure TouchPads,
it became apparent that some bitrot is at fault here:
gsynaptics
still lies around in our repos and happens to build.. but, that does not
make it any usable.
The daemon is configured to only fire up in a gnome session, where this
used to be 'preferred long ago', but nowadays, this functionality is
provided by GNOME intrnally, and it interacts directly with syndaemon
(from xf86-input-synaptics). GNOME still has code detecting the presence
of gsynaptics and would move itself out of the way, but then of course
anything the user does in gnome-control-center is useless; the user
would have to (and need to know to) configure all the settings in
gsynaptics.. which is an ugly tool and provides no additional
functionality (in my view).
so, if nobody comes up with a very compelling argument as to why
gsynaptics should not be removed from Factory (and this, openSUSE 13.2),
I will file for a delete request soon.
Cheers,
Dominique
--
Dimstar / Dominique Leuenberger <dimstar(a)opensuse.org>
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
The screen saver always wants either a mouse click+move or keyboard
input to show the desktop again. Is there a way to get normal behaviour?
At least in 11.4 it was possible to either just move the mouse or press
CTRL or SHIFT or such keys to show the screen contents again.
In control center I found no setting which would allow that again.
Olaf
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Il 30/09/2013 11:14, Marco Calistri ha scritto:
> Il 29/09/2013 16:50, John Andersen ha scritto:
>> On 9/29/2013 9:34 AM, Marco Calistri wrote:
>>> Dear openSuSers,
>>>
>>>
>>> The oddity of this issue is verging the incredible!:
>>>
>>> I have a Nokia Lumia 710 smart-phone, running WP-7.8 and I tried to send
>>> a picture from it to my laptop which is running openSUSE 12.3 64 bits,
>>> both from being logged in KDE or Gnome DE, but never the picture is sent
>>> to the computer.
>>>
>>> I have of course enabled the file sharing and reviewed all the
>>> configuration of Blue-tooth, but nothing to do: openSUSE refuses to
>>> accept and download the picture from the smart-phone.
>>
>> On KDE, it seems that pairing is a bit different, at least on 12.3.
>> It doesn't care about pins.
>> You click the taskbar tray Icon for bluetooth and select configure
>> Then in the configure window you scan for devices (add a device).
>> This should find your device and show its MAC in hex characters as well as its name.
>>
>> If you select Trusted, then opensuse+KDE will accept connections from that device
>> (whether or not it your Computer is set as visible), and upon sending a file it
>> will pup up a window to accept the file or not. (You can always set this as the default
>> action for files from that device from that same pop up window).
>>
>> (I don't have a windows phone to test with, so I tested with A Surface Pro tablet.)
>>
>> Each time I try to send a file from the device to opensuse/kde I see an authenticate
>> box on the surface pro. But you have to uncheck that, because KDE is using the
>> concept of a trusted device and the authentication option does not show
>> an actionable dialog on KDE.
>>
>>
>
> Hi John,
>
> The fact is that using BlueTooth in openSUSE 12.3 I cannot send from
> external device to the system, I can do the contrary: from system to
> device, though not always!
>
> But I can do it by sending from external device to an Ubuntu virtual
> machine running in same openSUSE 12.3, that is the oddity: it seems
> something is wrong in openSUSE.
>
> Cheers,
>
Same problem persist with openSUSE 13.1 64bits Gnome Desktop.
Send over BlueTooth from external device to O.S. fails!
A bit disappointed so far :-|
Cheers,
--
Marco Calistri (amdturion)
opensuse 12.3 (Dartmouth) 64 bit - Kernel 3.7.10-1.16-desktop Gnome 3.8.3
Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
After the latest round of updates [including the GNOME 3.8 repo] the
application dia is broken.
Core was generated by `dia'.
Program terminated with signal 11, Segmentation fault.
#0 ddisplay_update_handler (ddisp=0x2ee2bf0) at display.c:566
566 g_return_val_if_fail ( renderer->clip_region_clear != NULL
(gdb) bt
#0 ddisplay_update_handler (ddisp=0x2ee2bf0) at display.c:566
#1 0x00007f89f2497bf5 in g_main_dispatch (context=0x25b1b20) at
gmain.c:3054
#2 g_main_context_dispatch (context=context@entry=0x25b1b20) at
gmain.c:3630
#3 0x00007f89f2497f38 in g_main_context_iterate (context=0x25b1b20,
block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>)
at gmain.c:3701
#4 0x00007f89f24983aa in g_main_loop_run (loop=0x2611820) at
gmain.c:3895
#5 0x00007f89f3984727 in IA__gtk_main () at gtkmain.c:1257
#6 0x000000000041e405 in main (argc=<optimized out>, argv=<optimized
out>) at main.c:35
--
Adam Tauno Williams <mailto:awilliam@whitemice.org> GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Il 27/10/2013 23:49, John Andersen ha scritto:
> On 10/27/2013 05:23 PM, Marco Calistri wrote:
>> As I wrote I can send perfectly over Bluetooth toward the same Linux box
>> where 12.3 is running as main O.S. but using different guest O.S.
>> running as virtual-machines.
>
> Somebody has to own the bluetooth.
> Its going to be the host os or the guest os.
>
> If it works sending files to the host os via bluetooth on Opensuse 12.3
> then Opensuse is doing its job and there is no problem.
>
> If that doesn't work on a guest os you have a problem with how your
> VM software handles shared devices. Its a question for what ever list
> deals with that Virtual Machine software.
>
I resolved Bluetooth problem by reverting previous Gnome-3.8 Stable to
default.
I upgraded Gnome-3.6 to 3.8 some times ago but couldn't suppose that it
could broke Bluetooth.
Now I roll-backed Gnome to default openSUSE 12.3 version and Bluetooth
works perfectly send/receive!
Later I will check if also power-management now works as I expect with
my laptop.
This served me as lesson: to avoid upgrading things before the final
official release be ready but also sometimes is good to experiment new
things.
Cheers,
--
Marco Calistri (amdturion)
opensuse 12.3 (Dartmouth) 64 bit - Kernel 3.7.10-1.16-default
Gnome 3.6.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge
Mobile
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
I upgraded my workstation [nVidia x86_64] and primary laptop [Intel-GPU
x86_64] openSUSE 12.3 boxes to GNOME 3.8 as described @
<http://dominique.leuenberger.net/blog/2013/04/gnome-3-8-for-opensuse-12-3-g…>
Upgrade was smooth, and both are working. On the laptop [Intel-GPU] I
had to also perform the Mesa upgrade, otherwise it was hopelessly
donkers (as expected from the post).
zypper ar obs://home:dimstar:Mesa/standard Mesa
zypper dup --from Mesa
Only problem I have now is that GVFS WebDAV seems quite broken. I can
view a folder in Nautilus, but attempting to right-click open some file
results in an error. GVFS appears to be dropping the initial part of
the path so "/dav/Projects/MyProject/Documents/myfile.txt" results in a
request for "/Projects/MyProject/Documents/myfile.txt".
--
Adam Tauno Williams <mailto:awilliam@whitemice.org> GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
I'm not sure if this is a "GNOME" issue, it appears to be a Gtk issue,
so I don't know if that counts.
I'm seeing widget packing problems when using Wireshark, in dialogs some
widgets are not expanding to fill the available area.
Widget not packing correctly in the Follow TCP dialog
<https://bugzilla.novell.com/show_bug.cgi?id=819148>
I found a very similar but relating to the packet detail dialog.
<https://bugzilla.novell.com/show_bug.cgi?id=813180>
--
Adam Tauno Williams <mailto:awilliam@whitemice.org> GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org