In Fedora22, GCC not enabled the -fstack-protector by default, why?
by 乱雪
Such as:
// x.c
#include <stdio.h>
int main(void) {
char x[] = "abc";
printf("%s\n", x);
return 0;
}
and using GCC compile it:
➜ gcc x.c -v
......
/usr/libexec/gcc/x86_64-redhat-linux/5.1.1/cc1 -quiet -v x.c -quiet -dumpbase x.c -mtune=generic -march=x86-64 -auxbase x -version -o /tmp/ccqowh4f.s
......
as you see, GCC not enabled the -fstack-protector by default. And in Ubuntu:
➜ gcc x.c -v
/usr/lib/gcc/x86_64-linux-gnu/4.6/cc1 -quiet -v -imultilib . -imultiarch x86_64-linux-gnu x.c -quiet -dumpbase x.c -mtune=generic -march=x86-64 -auxbase x -version -fstack-protector -o /tmp/cc0aswkw.s
the enabled the -fstack-protector by default.
why?
8 years, 3 months
Fwd: Submission deadline for Changes of Fedora 23
by Paul W. Frields
Do we have system wide changes still to file for F23?
ISTM we have a few contenders that are not yet listed in the proposed
changes[1] list:
* Integrating distro upgrade
* D-Bus activation in gnome-session? (does this affect non-GNOME?)
* Boxes import OVF/OVA (iff. this affects Fedora deliverables, either
new requirements, or which can be dropped)
* Live USB changes -- since this affects e.g. docs/websites, possibly
a marketing angle
[1] https://fedoraproject.org/wiki/Releases/23/ChangeSet
--
Paul
----- Forwarded message from Jan Kurik <jkurik(a)redhat.com> -----
Date: Tue, 16 Jun 2015 08:39:19 -0400 (EDT)
From: Jan Kurik <jkurik(a)redhat.com>
To: devel-announce(a)lists.fedoraproject.org
Subject: Submission deadline for Changes of Fedora 23
X-Mailer: Zimbra 8.0.6_GA_5922 (ZimbraWebClient - FF38 (Linux)/8.0.6_GA_5922)
X-BeenThere: devel-announce(a)lists.fedoraproject.org
Hi everyone!
Changes submission deadline for Fedora 23 [1] is coming pretty soon - in one week on June 23rd. With Alpha release in August.
Please, submit your System Wide Changes by this deadline, earlier better. As the deadline mainly applies for System Wide changes it is always good to have most of Self Contained Changes proposed as well.
In case you'll need any help with your Change proposals, feel free to contact me.
Best Regards,
Jan
[1] https://fedoraproject.org/wiki/Releases/23/Schedule
--
Jan Kuřík
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
----- End forwarded message -----
8 years, 3 months
Re: Do not disturb mode in F22/Gnome 3.16
by Norman L Smith
I have written a simple extension to provide a Do Not Disturb Button.
I have cc'ed Ankur Sinha and Heiko Adams. I ask they test the
extension to insure it is adequate for their needs. If I receive
a positive response I will upload it to the ego site.
The following instructions should be all that is needed to test.
I suspect they may be a bit pedantic but here goes...
$ git clone https://github.com/nls1729/acme-code.git
$ cd acme-code/donotdisturb-button@nls1729
$ make zip-file
The file donotdisturb-button(a)nls1729.zip should be found
in the current directory.
Execute the gnome-tweak-tool (Tweak Tool).
Extensions -> Install Shell Extension
Navigate to directory containing donotdisturb-button(a)nls1729.zip.
Open
Log out and log in.
Execute the gnome-tweak-tool (Tweak Tool).
Extensions
Find "Do not disturb button"
Set to ON
A new button should appear on the left top panel.
The button can be toggled with the mouse or keyboard.
The extension should function with the Screen Shield
and Screen Lock.
If the button is set to busy and notifications are
received. Toggling the button to available will
display the queued notifications.
If notifications are received during Screen Lock or
Screen Shield the queued notifications can be displayed
on the Notification Section of the Calendar.
Please let known what you think.
Norman
8 years, 3 months
Workstation WG Recap 2015-June-22
by Michael Catanzaro
We wound up leaving early since the only people present were myself,
Kalev, and Jens. Please folks, set your calendars, alarms, and roosters
as needed. We're not going to make any grand decisions with the Great
Leader^W^W Paul on vacation, but we should still be able to have a
quorum and an effective meeting.
Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2015-06
-22/workstation.2015-06-22-13.02.html
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2015-06
-22/workstation.2015-06-22-13.02.txt
Log: http://meetbot.fedoraproject.org/fedora-meeting/2015-06
-22/workstation.2015-06-22-13.02.log.html
===============================
#fedora-meeting: Workstation WG
===============================
Meeting started by mcatanzaro at 13:02:33 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting/2015-06
-22/workstation.2015-06-22-13.02.log.html
.
Meeting summary
---------------
* Roll call! (mcatanzaro, 13:02:49)
* xdg-app (mcatanzaro, 13:08:35)
* We need more folks present to discuss whether or how Fedora will
integrate xdg-app. Defer until the next meeting. (mcatanzaro,
13:14:57)
Meeting ended at 13:15:10 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mcatanzaro (16)
* zodbot (4)
* kalev (4)
* juhp_ (3)
* Corey84 (2)
* rdieter (0)
* juhp (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
8 years, 3 months
Fedora runtime and apps (again)
by Alexander Larsson
Hi, it's me again. I've been doing some more work on a fedora-based
runtime and apps for xdg-app.
First of all I've cleaned up the runtime itself. It is now consists of
a new rpm, "fedora-runtime"[1], which has a bunch of requires for all
the packages which are supposed to be in the runtime, as well as some
special configuration (ld.so, fontconfig) needed in the runtime.
There is also a fedora-sdk rpm which pulls in fedora-runtime + dnf and
a few development tools.
I've built these rpms in the copr here:
https://copr.fedoraproject.org/coprs/alexl/fedora-runtime/
This means that the rpm-ostree json file[2] which describes the runtime
is super-trivial, as it just has the f22 repo and the copr repo, and
lists just the fedora-runtime package. See
If you have rpm-ostree-2015.6-2.fc22 installed (in koji for f22) all
you have to do is check out
https://github.com/alexlarsson/fedora-runtime and run "make" (or
something like "make PROXY="--proxy=http://127.0.0.1:8123" if you have a http proxy set
up).
If you just want to test this i've updated the repo at
http://people.redhat.com/~alexl/repo/
You should be able to test it (and the evince demo app i built) by
installing xdg-app 0.3.1 (in updates-testing) and doing:
xdg-app add-remote --no-gpg-verify --user fedora http://people.redhat.com/~alexl/repo/
xdg-app install-runtime --user fedora org.fedoraproject.Platform 22
xdg-app install-app --user fedora org.gnome.evince
xdg-app run org.gnome.evince
I've also done various kinds of experiments with creating applications
from existing fedora packages. In the end I realized that the only sane
way to make it work is to rebuild the packages with a custom rpm setup
that has %{_prefix} as "/app" and some other stuff. So, i set up a mock
configuration[3] that lets you easily rebuild packages in /app. It
mostly sets rpm macros and environment variables so that things build,
although I had to make changes to some packages (rpm to make brp
-compress compress inside /app, and check-rpaths to make rpaths in
/app/lib* ok, and pkg-config to be able to override .pc variables[4]).
These packages are in the copr above, so the mock config will
automatically pick them up.
There are also some simple scripts running mock in the git repo, so you
can easily rebuild an app from srpms. Here is how I built the evince
app:
for srpm in ghostscript-9.16-2.fc22.src.rpm ghostscript-fonts-5.50-33.fc21.src.rpm poppler-data-0.4.7-3.fc22.src.rpm poppler-0.30.0-3.fc22.src.rpm libspectre-0.2.7-5.fc22.src.rpm libgxps-0.2.2-11.fc22.src.rpm gnome-desktop3-3.16.2-1.fc22.src.rpm evince-3.16.1-1.fc22.src.rpm; do
./build-srpm.sh srpms/$srpm
done
xdg-app build-init evincedir org.gnome.evince org.fedoraproject.Sdk org.fedoraproject.Platform 22
./build-app.sh evince evincedir
xdg-app build-finish --command=evince --socket=x11 --filesystem=host evincedir
xdg-app build-export /some/repo evincedir
All the srpms I rebuilt for evince worked as-is when rebuilt in /app,
but I'm pretty sure some specfiles may need minor tweaks to fully
support building in a different prefix, and we still need to rename the
desktop files to the app-ids for the exports to work.
Is this work something we as a project are interested in doing?
[1] https://github.com/alexlarsson/fedora-runtime/blob/master/specfiles/fedor...
[2] https://github.com/alexlarsson/fedora-runtime/blob/master/fedora-runtime....
[3] https://github.com/alexlarsson/fedora-runtime/blob/master/fedora-app-22-x...
[4] https://bugs.freedesktop.org/show_bug.cgi?id=90917
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Alexander Larsson Red Hat, Inc
alexl(a)redhat.com alexander.larsson(a)gmail.com
He's an ungodly devious dog-catcher searching for his wife's true killer.
She's a transdimensional renegade schoolgirl in the wrong place at the
wrong time. They fight crime!
8 years, 3 months
Do not disturb mode in F22/Gnome 3.16
by Ankur Sinha
Hi,
I just realised this - the "busy"/"do not disturb mode" isn't in Gnome
3.16. Before, when notifications were still at the bottom, there was a
button that let the user set the notifications on silent. It was really
convenient, and if I remember correctly, it even set the empathy status
to "busy". Any chance this could be added, or any chance it's there and
I just haven't found it? At the moment, the only way I can find of
emulating this behaviour is to go to notifications in settings and turn
off "notification banners".
--
Thanks,
Regards,
Ankur Sinha "FranciscoD"
http://fedoraproject.org/wiki/User:Ankursinha
8 years, 3 months
automount of a volume has wrong permissions, can't open files
by Chris Murphy
I have files on an HFS+ volume that were created on OS X. When I'm in
Fedora 22, applications give me permissions errors when trying to open
them. I have to go to the CLI to fix this, there's no way to do it in
the GUI. Obviously this shouldn't happen, so it's a bug.
But, I can't figure out which component's bug. What actually
instigates automount in GNOME, and does it tell udisks2 what
permissions to use when automounting? That determines if it's some
GNOME component or if it's udisks2 or maybe something else.
# journalctl
Jun 15 21:18:15 f22m.localdomain udisksd[1272]: Mounted /dev/sda5 at
/run/media/chris/temphfs on behalf of uid 1000
# mount
/dev/sda5 on /run/media/chris/temphfs type hfsplus
(rw,nosuid,nodev,relatime,umask=22,uid=0,gid=0,nls=utf8,uhelper=udisks2)
[chris@f22m temphfs]$ ls -lhd /run/media/chris/temphfs/
drwxr-xr-x. 1 root root 9 Jun 15 20:12 /run/media/chris/temphfs/
[chris@f22m temphfs]$ getfacl /run/media/chris/temphfs/
getfacl: Removing leading '/' from absolute path names
# file: run/media/chris/temphfs/
# owner: root
# group: root
user::rwx
group::r-x
other::r-x
Thanks,
--
Chris Murphy
8 years, 3 months
