Hi guys,
I am wondering whether any of you also get hit by the "Additional
Multimedia Codecs Required" denial-of-service attack with GNOME on
Tumbleweed (and what to possibly do about it)?
In a nutshell, now and then, out of a sudden, without any trigger
that I could see
"Additional Multimedi Codecs Required"
"An application is requesting additional multimedia codecs"
shows up in the notification area. At a rate of two or perhaps
three per second.
Sometimes it goes away after a bit (in particular various attempts
and arbitrary mouse clicking?), sometimes <Alt><F2> "r" <Return>
helps.
Debugging this I guess it might be related to the following repeating
N times (in journalctl)?
Jun 17 23:41:30 anthias.pfeifer.com kde4-kopete.desktop[2566]: ** Message: PackageKit: xid = 0
Jun 17 23:41:30 anthias.pfeifer.com kde4-kopete.desktop[2566]: ** Message: PackageKit: desktop_id = (null)
Jun 17 23:41:30 anthias.pfeifer.com kde4-kopete.desktop[2566]: ** Message: PackageKit: Codec nice name: Vorbis decoder
Jun 17 23:41:30 anthias.pfeifer.com kde4-kopete.desktop[2566]: ** Message: PackageKit: ignoring field named streamheader
Jun 17 23:41:30 anthias.pfeifer.com kde4-kopete.desktop[2566]: ** Message: PackageKit: structure: gstreamer1(decoder-audio/x-vorbis)()(64bit)
Still, is there a way to set some rate limiting on the GNOME
notification side? (If not, might that be considered a useful
addition?)
Gerald
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Dear GNOMEs,
It's again time: we will start integrating GNOME 3.23.90 into
GNOME:Factory during the next couple days.
As this is an alpha version and we do not want to break any potential
users having this repo enabled, we will disable publishing again for
the time being.
If you have the repo enabled, you can keep doing so - nothing should
break, you just won't get updates in it anymore.
The next step is to submit GNOME 3.23.91 (next week) towards
openSUSE:Factory and get into the Staging area (we are already actively
bribing again to get Staging:G assigned).
GNOME 3.23.91 will NOT be accepted into openSUSE:Factory and will NOT
reach tumbleweed users; this will only serve us to finalize integration
testings and potentially adjust openQA tests where needed.
Shortly after, the same excercise will happen for GNOME 3.23.92 and if
all goes well we should be able to deliver GNOME 3.24.0 shortly after
it has been released upstream. The public release is planned for March
22nd 2017.
If you want to already have a glimpse at what will come your way, there
is the GNOME:Next repo which tracks unstable versions throughout their
development cycle - and for the less adventurous we produce a live
image out of those packages, which you can find at
http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/?P=G
NOME_Next*
Since about a week ago, there are even openQA tests running for this
image (oposite to the standard Tumbleweed process, though, openQA has
NO decisive influence on the release of a new iso file - it is FIRST
published, THEN tested)
The test overview can be found at
https://openqa.opensuse.org/group_overview/35
Cheers,
Dominique, in the name of the entire GNOME Team
Dear GNOMEs,
It's again time: we will start integrating GNOME 3.23.90 into
GNOME:Factory during the next couple days.
As this is an alpha version and we do not want to break any potential
users having this repo enabled, we will disable publishing again for
the time being.
If you have the repo enabled, you can keep doing so - nothing should
break, you just won't get updates in it anymore.
The next step is to submit GNOME 3.23.91 (next week) towards
openSUSE:Factory and get into the Staging area (we are already actively
bribing again to get Staging:G assigned).
GNOME 3.23.91 will NOT be accepted into openSUSE:Factory and will NOT
reach tumbleweed users; this will only serve us to finalize integration
testings and potentially adjust openQA tests where needed.
Shortly after, the same excercise will happen for GNOME 3.23.92 and if
all goes well we should be able to deliver GNOME 3.24.0 shortly after
it has been released upstream. The public release is planned for March
22nd 2017.
If you want to already have a glimpse at what will come your way, there
is the GNOME:Next repo which tracks unstable versions throughout their
development cycle - and for the less adventurous we produce a live
image out of those packages, which you can find at
http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/?P=G
NOME_Next*
Since about a week ago, there are even openQA tests running for this
image (oposite to the standard Tumbleweed process, though, openQA has
NO decisive influence on the release of a new iso file - it is FIRST
published, THEN tested)
The test overview can be found at
https://openqa.opensuse.org/group_overview/35
Cheers,
Dominique, in the name of the entire GNOME Team
Hi,
with latest packages from Tumbleweed I use the CalDAV backend (with htt
ps://calserv.provo.novell.com ) and I can see my appointments.
I also configured (Edit->preferences->Calendar & tasks-> Show a
reminder for every appointment) to 1 min so I thought I'll get
reminders for *every* meeting. But I get not a single reminder for any
meeting.
Any ideas where to look for a possible solution?
TIA,
Tom
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Hello,
I'm experiencing a strange glitch in GNOME applications like
gnome-terminal or gedit, which support a title- and border-less
fullscreen mode. Before I file a bug, I'd like to know if someone can
reproduce the following behavior:
1.) Start gnome-terminal (or gedit) in GNOME on Wayland
2.) Press F11 to enter fullscreen mode
3.) Press F11 again to switch back to windowed mode
What I'm seeing is that the application flickers and sometimes shows
window decorations at the top shortly, but it stays in fullscreen mode.
After pressing F11 repeatedly, the applications sometimes manages to
switch back to a normal window, but always in maximized state; i.e. the
original geometry is lost.
This seems to happen only on Wayland. X11 works fine. I also couldn't
reproduce this behavior on another distro. Could someone who is running
Tumbleweed + Wayland + GNOME please try and let me know if it happens
for them, too?
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org