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
I had a working tumbleweed with KDM and KDE. Tried also to login to a
Gnome session from KDM which returned only the KDM login menu back again.
Therefore I decided to make a new, plain 12.3 installation from scratch
with only the Gnome desktop installed. Gnome 3.6 login worked ok from
the GDM menu after that.
Then ran 'zypper dup' which upgraded 12.3 to the latest level. Gnome 3.6
login still worked ok after that.
Disabled the 12.3 repositories and added the following five for
tumbleweed distro upgrade:
1. openSUSE Current OSS
http://download.opensuse.org/distribution/openSUSE-current/repo/oss/
2. openSUSE_Current_non-OSS
http://download.opensuse.org/distribution/openSUSE-current/repo/non-oss/
3. openSUSE Current updates
http://download.opensuse.org/update/openSUSE-current/
4. openSUSE-Current-non-oss-current
http://download.opensuse.org/update/openSUSE-non-oss-current/
5. Tumbleweed
http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/
Then ran 'zypper dup' which upgraded 306 packages to tumbleweed,
possibly from Gnome 3.6 to 3.8 included.
After this upgrade, neither normal mode nor Advanced (recovery) mode
boot up to the GDM login menu, but stop with a black console after the
last message "Reached target Graphical Interface" or after "Started LSB
x Display Manager".
Similar experiences and possibly solutions?
Thanks,
Terje J. Hanssen
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Hi,
I was looking at
https://build.opensuse.org/project/subprojects?project=GNOME and
realized we have many many subprojects, with many of them being really
old.
I've started marking as DISCONTINUED (in the description) some of these
projects:
- GNOME:STABLE:2.x
- GNOME:STABLE:{3.0,3.2,3.4}
- GNOME:Backports:2.x
- GNOME:Community (superseded with GNOME:Apps, really)
At the same time, I'm removing all maintainers and only leaving the
gnome-maintainers group (to avoid people changing packages in these
projects, but still have a group who can jump in if really needed) and
disabling build on Factory when it was still there.
I'm planning to do the same for the following projects which have not
been active in a long time, so please shout fast (within a week) if you
don't want this:
- GNOME:Apps:F-Spot
- GNOME:Apps:F-Spot:Unstable
- GNOME:Apps:Tasque
- GNOME:Apps:Tomboy
- GNOME:Apps:Tomboy:Unstable
- GNOME:Ayatana:11.4
- GNOME:Ayatana:deprecated
- GNOME:Evolution and GNOME:Evolution:*
- GNOME:GNOME1
Note that I'm not removing any package, nor dropping any repository. So
all of this should be revertable.
Thanks,
Vincent
--
Les gens heureux ne sont pas pressés.
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Hi,
I've just applied the latest 12.3 updates and now all my input fields in
gtk2 applications are "flat". Is that intentional? This looks quite
strange to me and everything but nice.
(I'm not running under Gnome but WindowMaker so no Gnome settings are
applied but only gtk2 default behaviour.)
I guess
gtk2-metatheme-adwaita-3.6.2-3.4.1
gtk2-theming-engine-adwaita-3.6.2-3.4.1
is responsible for that?
* Fr Apr 12 2013 jmcd(a)suse.com
- Fix GtkEntry text background override; (bgo#685712);
(bnc#815078).
+ Added allow-gtkentry-background-override.patch
+ xchat input and topic boxes are unreadable
Ah, and just looking into bnc#815078 finding the same report and it
apparently is a bug!
Should I raise the severity since the update is broken or do we need a
new regression bug with higher severity to get it fixed quickly?
Thanks,
Wolfgang
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
I usually have three or four Epiphany windows running with 10-15 tabs.
I'm currently running:
Version : 3.8.1
Release : 163.3
Architecture: x86_64
Whenever I switch focus to another app and then back, or whenever I
change tabs within Epiphany, the newly-focused page blanks completely,
sometimes for over a minute. This seems to be independent of actually
updating the page contents, just a repainting of the page as it was at
the last refresh.
Has anyone else seen this behaviour? Is it an upstream issue?
Thanks,
Mike
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
After pulling the most recent updates [using the GNOME 3.8 repo] the
NetworkManager on both my workstations and my laptop seems to get
out-of-sync.
Disabling the wireless after being connected does appear to stop the
wireless [verified with ip addr] but it still shows the
wireless-connection icon [i tried to get a screenshot but that doesn't
work when a shell submenu is open]. The same effect seems to occur
after disconnecting from a VPN - NM doesn't seem to be aware that the
VPN connection closed although 'ip addr' verifies that it has.
Also for VPN connections NM stopped updating DNS [/etc/resolv.con] upon
connection of the VPN. This occurs for both by laptop and my
workstations, where connect/disconnect worked previously and
added/removed DNS entries automatically.
NetworkManager-0.9.8.0-3.3.x86_64
gnome-shell-3.8.1-2.1.x86_64
--
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 having a very weird problem with one of my machines
The Symptom - shortly after logging in, gnome-shell will be
'non-responsive' with the hot corners, Super/Windows Key, etc all
failing to do anything. Clicking on the Activities or User Menu gets
no response
However, the machine is otherwise operational
This is happening on both GNOME 3.6 and 3.8 consistently, but only on
one of my machines.
If I already have windows open, these windows may still work - for
example Firefox is still perfectly responsive, as is Guake and YaST
'Core GNOME' applications like Nautilus however seem to 'lock up' at
the same time. If you happen to have any of these 'core GNOME'
application windows over the top of non-GNOME applications like
Firefox/YaST any mouse clicks seem to pass right through the GNOME
applications, activating whatever you're accidentally clicking on in
the Firefox/YaST windows below
Waiting a while seems to be all it needs to get gnome-shell working as
usual, and it doesn't occur more than once per user session, but it
does seem to be happening on every user session on this machine.
Things I believe I've ruled out
1) Weird settings in /home folder - I destroyed all hidden folders in
my home folder, and this occurs on fresh accounts
2) Nvidia vs Nouveau - yes, this machine has an Nvidia video card, but
this behaviour is happening identically on both Nvidia and Nouveau
video drivers
3) Software selection - this happens on a fresh GNOME openSUSE 12.3
installation from DVD with no customisation what so ever, as well a
fresh 12.3 Install with GNOME Stable 3.8 + guake + owncloud
4) Multi monitors - this seems to happen regardless of what multi
monitor behaviour is in place
Theories I've got left - ie "What's special about this machine?"
All my other GNOME machines and VM's all use Network Manager, this is
the one machine I has that does not. But I see nm-applet is running so
I guess gnome-shell might be doing some weird attempted init on boot,
failing, locking up, then giving up and behaving normally.
This isn't a machine I can easily activate NM on, so before I test
this theory, I would like to hear if anyone else has bumped into
anything like this, and if so, what was the fix for you if you found
one?
And if anyone else has any bright ideas where to look for any
solutions or clues so I can actually file a useful bug report for
someone, I'd appropriate it ;-)
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Hej!
I posted to opensuse-factory before, but Greg KH suggested to take this
problem to this mailing list (or upstream, but I think this is enough
for now, until we know more).
Anyways, here's the problem:
Since Gnome 3.8 hit Tumbleweed last week, Emacs shows a curious problem
when using AucTeX to typeset LaTeX documents.
When typesetting a LaTeX document, Emacs opens a new buffer with the
LaTeX output in it. When the LaTeX run is finished, Emacs displays
"LaTeX: successfully formatted {1} page" (with the appropriate number of
pages). This also ends the LaTeX-process, allowing to use a new process,
like LaTeX, Bibtex/Biblatex/Biber etc.
This is not a LaTeX problem, since it works correctly from console (and
finishes the run). It is also not TeX-engine specific, since both
XeLaTeX and pdfLaTeX show the same behaviour. Moreover, this does not
seem to be an Emacs problem, since emacs-x11 (as opposed to emacs-gtk)
does not show the same problem.
*However*, with the Gnome 3.8 update, Emacs does not do the last step,
i.e. displaying that LaTeX finished successfully, and consequently, the
LaTeX process never finishes. When calling a new LaTeX process, Emacs
then first asks whether to kill the old (unfinished process), which
needs to be accepted before a new LaTeX process can be called.
Emacs produces no error messages whatsoever, and I see no output when
starting it from console, either.
The problem goes away when downgrading the Gnome-related packages in
Tumbleweed to the normal 12.3 versions, which suggests that this is, in
fact, a Gnome problem.
It seems as if something in Gnome 3.8's core breaks the process
notifications and handlings between processes, but I have no idea what
would.
The Emacs version does not matter, the behaviour is displayed with the
standard 12.3 version, Tumbleweed version, my current compiled version
and a fresh compile from Emacs master.
Any ideas? And what should I file a bug against?
Cheers,
Peter
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Dear All,
after the upgrade to Gnome 3.8, in my home desktop system I started
to notice a serious problem when switching users.
If I log in as a user, then 'Switch User' to allow another user to
login, and then switch back to the first user (either by selecting
again the 'Switch User' entry in the menu, or going to the correct tty
with the keyboard), I see a message saying that something went wrong,
that all extensions have been turned off, and offering me to logout (I
am not using any extension).
I tried to diagnose the source of the problem, and it seems that GDM
is crashing. I see the following messages in /var/log/messages (notice
the failed asserts for xdm):
2013-04-21T02:48:22.765606+02:00 linux-3xop dbus-daemon[554]:
dbus[554]: [system] Successfully activated service
'org.freedesktop.PackageKit'
2013-04-21T02:48:22.766352+02:00 linux-3xop dbus[554]: [system]
Successfully activated service 'org.freedesktop.PackageKit'
2013-04-21T02:48:23.363053+02:00 linux-3xop polkitd[623]: Registered
Authentication Agent for unix-session:5 (system bus name :1.144
[/usr/bin/gnome-shell], object path
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
2013-04-21T02:48:23.503771+02:00 linux-3xop gnome-session[2003]:
Entering running state
2013-04-21T02:48:24.118099+02:00 linux-3xop
gnome-keyring-daemon[2000]: keyring alias directory:
/home/apaterna/.local/share/keyrings
2013-04-21T02:48:24.136829+02:00 linux-3xop goa[2152]:
secret_password_lookup_sync() returned NULL [goautils.c:210,
goa_utils_lookup_credentials_sync()]
2013-04-21T02:48:24.137199+02:00 linux-3xop goa[2152]:
/org/gnome/OnlineAccounts/Accounts/account_1366456332: Setting
AttentionNeeded to TRUE because EnsureCredentials() failed with: No
credentials found in the keyring (goa-error-quark, 4)
[goadaemon.c:1085, ensure_credentials_cb()]
2013-04-21T02:48:25.078198+02:00 linux-3xop goa[2152]:
secret_password_lookup_sync() returned NULL [goautils.c:210,
goa_utils_lookup_credentials_sync()]
2013-04-21T02:48:32.871663+02:00 linux-3xop goa[2152]: last message
repeated 2 times
2013-04-21T02:48:32.871618+02:00 linux-3xop gdm-password]:
pam_unix(gdm-password:session): session closed for user vmariani
2013-04-21T02:48:33.085460+02:00 linux-3xop kernel: [ 358.850720]
mission-control[1795]: segfault at 0 ip 00007f58bf375cb0 sp
00007fff1d63b9b8 error 4 in
libglib-2.0.so.0.3600.0[7f58bf33a000+fc000]
2013-04-21T02:48:33.320474+02:00 linux-3xop xdm[555]: GLib-GObject:
g_object_ref: assertion `object->ref_count > 0' failed
2013-04-21T02:48:33.320648+02:00 linux-3xop xdm[555]: GLib-GObject:
g_object_unref: assertion `object->ref_count > 0' failed
2013-04-21T02:48:33.321903+02:00 linux-3xop xdm[555]: GdmDisplay:
display lasted 0.000510 seconds
2013-04-21T02:48:41.666463+02:00 linux-3xop systemd-logind[532]:
Removed session 4.
I observed this error both when using the proprietary nvidia driver
and the open source nouveau driver.
I also noticed that the session for the first user opens on tty7, but
the one for the second opens on tty2, not on tty8. Is this ok?
I would really like to get to the bottom of the problem as user
switching is essential for me on the desktop. Please let me help if I
can provide more information to help with the debugging
Thank you for your help
Valerio
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org