Upgrade to kernel 3.19.0.0 (rc3) partially breaks VirtualBox guest additions
by Peter Laursen
Kernel 3.19.0.0 (rc3) was rolled out today to Fedora Desktop Rawhide (I use
the xfce 'spin').
as posted in VirtualBox forums:
https://forums.virtualbox.org/viewtopic.php?f=3&t=65475
Fedora's 'bleeding edge' distro "rawhide" has rolled out kernel version
3.19.0.0 today. Virtualbox guest additions 4.1.20 fail with desktop
integation (only a ~1000 pixel horizontal resolution can be achived). Mouse
integration and shared folder integration is OK. I *do have* rebuilt the
guest additions after the kernel upgrade - just telling in advance in case
somebody should feel like to ask!
--
Hilsen / Regards
Peter Laursen
9 years, 3 months
runtimes, app bundles, etc
by Matthias Clasen
I've promised that I would give some status update on the work that Alex
is doing on sandboxed apps and app bundles. I can't really do a much
better job than Alex himself, so I'll just summarize the highlights and
point at the wiki page that we've set up.
---
The high-level goals of this effort are to provide infrastructure that
allows build and distribute applications independently of the base
system, and to run applications in a well-defined environment that is
isolated from the host system.
The work that Alex has been doing revolves around the concepts of
runtimes, app bundles and sdks.
A runtime provides a well-defined environment that an app can run in.
Examples would be "GNOME 3.14" or "KDE 5.6". A runtime can be thought of
as a /usr with fixed contents. When a bundled app gets run, the runtime
it needs gets mounted at /usr.
An app bundle contains a metadata file that describes the application,
what runtime it needs, and various other things. The other parts of the
app bundles are the actual application files, which get mounted
under /self when the app is run, and a list of exported files - these
typically are things that the host environment needs to know about the
application: a desktop file, icon, d-bus service file, and so on. This
implies that there is still an install step for these app bundles: the
exported files get copied into a well-known place where the host system
can find them.
Both runtimes and app bundles can be installed per-user and system-wide.
With the way things are currently set up, per-user installations end up
in $HOME/.local/share/xdg-app/ and system-wide installations
in /usr/share/xdg-app.
An sdk is basically the 'devel' parts of a runtime, split off. E.g.
there is a "GNOME 3.14" sdk that corresponds to this runtime. Building
an app bundle is done by installing the sdk, and then building the app
against it, with --prefix=/self.
The current implementation uses ostree to distribute both runtimes and
applications as well as updates, but that does not have to be the only
distribution mechanism. I expect that we will ship a 'reference runtime'
for GNOME upstream, but Fedora and other distros could very well provide
their own implementation of this. Bundled applications can coexist just
fine with 'traditional' apps, and it is also conceivable to ship app
bundles wrapped in packages.
Not all pieces of this outline are fully developed yet, but Alex has
written an xdg-app tool, which can install and update runtimes, sdks and
applications, and has initial support for building applications. The Sdk
also supports using (s)rpms as building blocks for application bundles -
it ships with a preconfigured rpmbuild and rpmdb.
The repositories we have contain runtimes for GNOME 3.14 and 3.16, as
well as a number of example apps:
gedit
gnome-builder
glxgears (demonstrating working GL in bundles)
paplay (demonstrating working audio in bundles)
---
For further details, and for pointers to code you can run on your
system, see https://wiki.gnome.org/Projects/SandboxedApps
Matthias
9 years, 3 months
Linux desktop and high resolution laptops
by Peter Laursen
I am in the process of buying a laptop for travel. it should be 13"-14".
relatively small and lightweight - and still with *power*.
I came across:
https://www.mm-vision.dk/vision-b4385-baerbar-med-ips-panel. They have the
option to purchase with no OS installed (hooray!) and you can choose
between different CPUs, RAM configs and disk systems. It is also not very
expensive specs taken into consideration, really.
But monitor is 3200x1800 pixels on a 13" monitor. And that is the problem.
This machine is designed for Win8, where the 'tiled interface' is DPI-aware
and will scale automatically. I plan to install a dual-boot of Win7 and
Linux (SuSE or Fedora), and they will both be completely hopeless to use on
this system as everything (icons, controls) will be extremely small in
almost every interface and application.
I may opt for this instead: http://mysn.eu/schenker-s413. 14" monitor with
1920*1440 (HDMI) will just accurately work if the monitor is good quality.
It also has similar configuration options as the one above.
I dont think Linux Desktop people takes this seriously enough (or they do
not communicate it). It will IMO take ~12 months and most laptops sold
will a have a monitor with so high resolution that the Linux Desktop will
be a museum item for people who like to play around with old hardware - and
as a hobby only (and same will be true for Win7) .
Are there any efforts anywhere in the Linux world considering support for
high monitor resolutions (auto-scaling based on DPI) like Mac/Retina and
Win8 has? What Linux desktops/window managers have it in progress? Does
anybody know?
What say? Was it too provocative?
post mortem: this is of course not for "Fedora Desktop" only. It is for
the future of the "LInux Desktop" as such. But as Fedora now has a
dedicated Desktop distro they should be serious about it. I think there
should be no 'holy cows'. not X11 if Wayland does better and not Gnome if
Enlightment does better.
--
Hilsen / Regards
Peter Laursen
9 years, 3 months
Workstation WG Recap 2015-Jan-07
by Paul W. Frields
Minutes: http://meetbot.fedoraproject.org/meetbot/fedora-meeting/2015-01-07/workst...
Minutes (text): http://meetbot.fedoraproject.org/meetbot/fedora-meeting/2015-01-07/workst...
Log: http://meetbot.fedoraproject.org/meetbot/fedora-meeting/2015-01-07/workst...
* * *
=======================================
#fedora-meeting: Workstation WG meeting
=======================================
Meeting started by jwb at 16:00:39 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2015-01-07/workstation.20...
.
Meeting summary
---------------
* init (jwb, 16:00:40)
* Change proposals (stickster, 16:05:40)
* kalev filing Change for GNOME 3.16 + Software capabilities
(stickster, 16:36:40)
* mclasen filing Changes for nautilus + gnome-shell (stickster,
16:36:53)
* otaylor filing Change for improved battery life (stickster,
16:37:10)
* sgallagh + stickster to join discussion with rishi, cschalle, et al.
on Fedora account integration scope and see what is F22 vs. F23
doable (stickster, 16:38:03)
* ACTION: stickster to note above to WG on list, and get input on
proposed so we can move on in this meeting :-) (stickster,
16:38:59)
* App bundles upstream status (stickster, 16:40:39)
* ACTION: mclasen to follow up on list later in the week (stickster,
16:41:31)
* Upgrade notification UI mockup (stickster, 16:41:38)
* ACTION: mclasen following up with aday, we should hear back on list
shortly (stickster, 16:42:13)
* Bug triage (stickster, 16:42:48)
* ACTION: stickster bring wallpaper topic and bug topic to next agenda
(stickster, 17:06:19)
* ACTION: stickster add unattended install issue to next agenda, re:
https://bugzilla.redhat.com/show_bug.cgi?id=1178787 (stickster,
17:07:26)
Meeting ended at 17:08:03 UTC.
Action Items
------------
* stickster to note above to WG on list, and get input on proposed so we
can move on in this meeting :-)
* mclasen to follow up on list later in the week
* mclasen following up with aday, we should hear back on list shortly
* stickster bring wallpaper topic and bug topic to next agenda
* stickster add unattended install issue to next agenda, re:
https://bugzilla.redhat.com/show_bug.cgi?id=1178787
Action Items, by person
-----------------------
* mclasen
* mclasen to follow up on list later in the week
* mclasen following up with aday, we should hear back on list shortly
* stickster
* stickster to note above to WG on list, and get input on proposed so
we can move on in this meeting :-)
* stickster bring wallpaper topic and bug topic to next agenda
* stickster add unattended install issue to next agenda, re:
https://bugzilla.redhat.com/show_bug.cgi?id=1178787
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* stickster (82)
* cschalle (16)
* mclasen (15)
* ryanlerch_ (15)
* otaylor (13)
* jwb (13)
* drago01 (12)
* rdieter (11)
* halfline (9)
* mcatanzaro (9)
* sgallagh (6)
* lmacken (6)
* zodbot (5)
* kalev (5)
* cwickert (1)
* ryanlerch (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
9 years, 3 months
Workstation WG Recap 2014-Dec-17
by Paul W. Frields
Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2014-12-17/workstation.20...
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2014-12-17/workstation.20...
Log: http://meetbot.fedoraproject.org/fedora-meeting/2014-12-17/workstation.20...
* * *
======================================
#fedora-meeting: Fedora Workstation WG
======================================
Meeting started by stickster at 16:00:18 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting/2014-12-17/workstation.20...
.
Meeting summary
---------------
* Roll call! (stickster, 16:00:27)
* Surprise topic: F21 (stickster, 16:04:28)
* F21 Workstation is out, it's awesome, and congrats to everyone. That
is all. (stickster, 16:05:47)
* Change proposals (stickster, 16:06:12)
* Current Change checkpoint is proposed for 2015-Jan-20, so about 2.5
or 3 weeks after holiday (stickster, 16:08:27)
* ACTION: mclasen file gnome-shell + nautilus related changes
(stickster, 16:11:45)
* ACTION: stickster Put remaining Change items on agenda for
2015-Jan-07 to check outlook for landing (stickster, 16:12:16)
* LINK: http://fedoraproject.org/wiki/Releases/22/Schedule and
https://wiki.gnome.org/ThreePointFifteen if anyone else wants to
compare (kalev, 16:14:47)
* Current GNOME 3.16 schedule looks like a tight but workable fit for
current Fedora 22 proposed schedule (stickster, 16:15:24)
* jwb points out that some upstream stuff will require Fedora-specific
work outside the WG, e.g. app bundles (stickster, 16:27:01)
* Current big-picture, more Fedora-WS-oriented improvements: (1) app
bundles (high effort, multi-release); (2) upgrade notifications
(lower effort, maybe F22 doable) (stickster, 16:45:25)
* ACTION: mclasen dig up summary/details on current app bundles effort
so we can understand state upstream (stickster, 16:46:00)
* ACTION: mclasen look for mockups for UI portion of upgrade
notification (possibly execution?) (stickster, 16:46:34)
* For reference, a different implementation of upgrades:
https://wiki.gnome.org/Design/OS/Migration (stickster, 16:48:18)
* Resolving firewall question (stickster, 16:49:32)
* ACTION: stickster mclasen be around for FESCo meeting in ~1 hour if
this topic comes up (stickster, 17:03:58)
* ACTION: stickster start discussion on desktop@ list toward a wiki
page that covers our assumptions, problem statement, and our ideal
Workstation approach for firewall (stickster, 17:05:07)
* All other business (stickster, 17:05:28)
* ACTION: stickster Carry over bug triage topic for next meeting
(stickster, 17:05:37)
Meeting ended at 17:07:25 UTC.
Action Items
------------
* mclasen file gnome-shell + nautilus related changes
* stickster Put remaining Change items on agenda for 2015-Jan-07 to
check outlook for landing
* mclasen dig up summary/details on current app bundles effort so we can
understand state upstream
* mclasen look for mockups for UI portion of upgrade notification
(possibly execution?)
* stickster mclasen be around for FESCo meeting in ~1 hour if this topic
comes up
* stickster start discussion on desktop@ list toward a wiki page that
covers our assumptions, problem statement, and our ideal Workstation
approach for firewall
* stickster Carry over bug triage topic for next meeting
Action Items, by person
-----------------------
* mclasen
* mclasen file gnome-shell + nautilus related changes
* mclasen dig up summary/details on current app bundles effort so we
can understand state upstream
* mclasen look for mockups for UI portion of upgrade notification
(possibly execution?)
* stickster mclasen be around for FESCo meeting in ~1 hour if this
topic comes up
* stickster
* stickster Put remaining Change items on agenda for 2015-Jan-07 to
check outlook for landing
* stickster mclasen be around for FESCo meeting in ~1 hour if this
topic comes up
* stickster start discussion on desktop@ list toward a wiki page that
covers our assumptions, problem statement, and our ideal Workstation
approach for firewall
* stickster Carry over bug triage topic for next meeting
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* stickster (103)
* jwb (53)
* mclasen (48)
* cschalle_ (10)
* ryanlerch (9)
* kalev (9)
* randomuser (7)
* rdieter (5)
* zodbot (5)
* mcatanzaro (2)
* jreznik (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
9 years, 3 months
Application is ready notification
by Ryan Lerch
Just wondering if anyone here knows of the design rationale for the
(seemingly intermittent to me) notification i get informing me that an
application window is ready for my attention.
I seem to get these most when opening a file in the default application
from firefox, or opening an application from the terminal, or sometimes
when clicking on a notification from an application. In all cases when I
see this notification, I did want to see the application window to
appear and get focus.
There is a shell extenstion available to turn off this application is
ready behaviour, which I do use, but IMO, this would be a useful default
behaviour to have turned on in Workstation.
cheers,
ryanlerch
9 years, 3 months
