By default, Nautilus displays the weekday for more recently modified
files. This can be confusing, and I have to look at the calendar to
compare dates. Is there a way to change this, so Nautilus displays the
calendar date for all files? I'm using oS Leap 15.1 and GNOME 3.26.
Thanks,
Jon Cosby
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Hi,
with the Firefox 73 builds I've enabled the cairo-gtk3-wayland target.
So wayland support should be enabled in Firefox if
* Gtk >= 3.22
* GDK_BACKEND is set OR MOZ_ENABLE_WAYLAND is set
Now I'm wondering how this could be integrated better into Tumbleweed
and was wondering what logic I could put into the firefox start wrapper.
Is there a reliable (and lightweight) way to get the information if we
are running under wayland which could be used?
Thanks,
Wolfgang
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Hello good people,
I am pretty new to the collab plugin and found something I did not fully
understand. I am putting the mail here since I saw the collab plugin was
heavily used by the GNOME project :-) Please let me know if this should go to
the packaging list.
As seen below, the version of GNOME:Next/libsigc++2 was given as 2.10.1,
however the real version of the package is already 2.10.2. Is it expected?
$ osc collab todo --project GNOME:Next | grep -e sig -e 'Package'
Package | Parent Project | GNOME:Next | Upstream
libsigc++2 | 2.10.1 | 2.10.1 | 2.10.2
libsigc++3 | 2.99.12 | 2.99.12 | 2.99.13
$ osc ls GNOME:Next/libsigc++2
_link
baselibs.conf
libsigc++-2.10.2.tar.xz
libsigc++-std-c11.patch
libsigc++2.changes
libsigc++2.spec
# -> GNOME:Factory libsigc++2 (latest)
baselibs.conf
libsigc++-2.10.2.tar.xz
libsigc++-std-c11.patch
libsigc++2.changes
libsigc++2.spec
Thank you!
Best wishes,
Yifan
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
What's happened to the GNOME screensaver in 3.26? It's a separate
package in Tumbleweed, and I can't find it for Leap 15.1. I can't lock
my computer without it. The command gnome-screensaver-command is not
found.
Jon Cosby
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Greetings,
I have a user for whom I installed openSUSE Leap 15 this week.
He has reported that when his Acer tower unit wakes up from sleep, there is no wi-fi. Sadly, he switches off and back on.
I saw the wireless card, it’s a PCI.
I think that this cannot be an ongoing solution. I tried to Google....
Anybody knows of something that a layman can do to get back in business?
Interesting?
*Also posted in FB.*
Best wishes
Sent from my iPhone
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Hi,
I have created a package [1] for piper [2], a GTK+ application to configure
gaming mice. As I would like to contribute it to Factory I am now looking for
a devel project I could maintain it in. Sadly, the project structure of the
Gnome projects is not too obvious to me. Shall I submit it to Gnome:Apps, or
would another project be a better fit for such an application?
Kind Regards,
Matthias
[1]: https://build.opensuse.org/package/show/home:theMarix:Staging/piper
[2]: https://github.com/libratbag/piper
--
Dr. Matthias Bach
www.marix.org
„Der einzige Weg, die Grenzen des Möglichen zu finden, ist ein klein wenig
über diese hinaus in das Unmögliche vorzustoßen.“ - Arthur C. Clarke
Hi,
I just now get the first time a BIOS upgrade request on my Lenovo Thinkpad
through Gnome Software on TW.
Where is this coming from? Is it save to apply it from Gnome Software? Typically
I boot into Windows to use Lenovo's tooling for that purpose but if it works
also reliably that way fine for me.
I am just _really_ surprised that and how this is integrated into TW talking
about hardware detection and finding the right upgrades from a vendor.
Are there any details somewhere describing that feature?
Thanks,
Wolfgang
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Hi,
First of all, kudos and thanks to the openSUSE GNOME team for already
getting us GNOME 3.28 on TW, so closely following its upstream release.
You folks rock!
I was wondering if the mechanism for switching to gnome-wayland session
at the gdm login screen has changed. I don't see separate entries for
GNOME [Wayland] and GNOME Xorg, like it used to show on gdm 3.26, when
I click on the gear menu after selecting the user. It only shows two
entries: GNOME and Icewm, although I have gnome-session-wayland
installed. When I log in to the GNOME, it logs me into an Xorg session.
Thanks in advance for any help.
Cheerio!
--
Atri Bhattacharya
Sat 17 Mar 00:24:49 CET 2018
Sent from openSUSE Tumbleweed on my laptop.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
This is a Tumbleweed system that has been (mostly) zypper dup-ed
for a bit more than two years.
rpm -qa gnome* | grep -v 3.26 | sort gives the following, and I
wonder to what extent I can/should simply remove these packages?
gnome-icon-theme-3.12.0-4.2.noarch
gnome-icon-theme-extras-3.12.0-3.3.noarch
gnome-icon-theme-symbolic-3.12.0-3.3.noarch
gnome-keyring-3.20.1-3.4.x86_64
gnome-keyring-pam-3.20.1-3.4.x86_64
gnome-mahjongg-3.22.0-1.3.x86_64
gnome-menus-3.13.3-2.4.x86_64
gnome-menus-branding-openSUSE-42.1-1.4.noarch
gnome-nettool-3.8.1-8.6.x86_64
gnome-power-manager-3.25.90-1.1.x86_64
gnome-shell-search-provider-seahorse-3.20.0-2.8.x86_64
gnome-themes-accessibility-3.22.3-1.3.noarch
gnome-themes-accessibility-gtk2-3.22.3-1.3.noarch
gnome-user-share-3.18.3-1.3.x86_64
gnome-vfs2-2.24.4-29.2.x86_64
gnome-video-effects-0.4.3-1.2.noarch
And, more importantly, should we get them removed via zypper dup?
Gerald
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Once an USB storage device with several partitions gets connected to the system, something automatically mounts each filesystem on a partition in read-write mode. Filesystems on LVM volumes are recognized, but not automatically mounted. LUKS partitions are entirely ignored.
To avoid datacorruption during a crash, one can unmount these partitions easily in the Nautilus UI. But once the screen is locked, and later unlocked, something mounts the filesystems again.
To me it is not clear at all what the benefit of that action would be.
The question is: what must be done to avoid these automounts during screen unlock?
Olaf
