Re: [darktable] Upgrade to 1.1.4
by Rex Dieter
Please be careful, rewriting history (and changelog entries).
-- rex
madko wrote:
> commit 7cbe3221ef9411bb258c6d65b7f00f0de557c380
> Author: Edouard Bourguignon <madko(a)linuxed.net>
> Date: Sat Mar 9 13:57:43 2013 +0100
>
> Upgrade to 1.1.4
...
> @@ -114,11 +115,11 @@ gtk-update-icon-cache %{_datadir}/icons/hicolor
> &>/dev/null || :
>
>
> %changelog
> -* Sun Mar 10 2013 Rex Dieter <rdieter(a)fedoraproject.org> 1.1.4-1
> -- Upgrade to 1.1.4 (#913847, #919811)
> +* Sun Mar 10 2013 Edouard Bourguignon <madko(a)linuxed.net> - 1.1.4-1
> +- Upgrade to 1.1.4
>
> -* Sun Mar 10 2013 Rex Dieter <rdieter(a)fedoraproject.org> - 1.1.3-2
> -- rebuild (OpenEXR)
> +* Fri Feb 22 2013 Edouard Bourguignon <madko(a)linuxed.net> - 1.1.3-2
> +- Add some missing dependancies
>
> * Mon Feb 11 2013 Edouard Bourguignon <madko(a)linuxed.net> - 1.1.3-1
> - Upgrade to 1.1.3
11 years, 1 month
Re: Improving the Fedora boot experience
by drago01
On Tue, Mar 12, 2013 at 2:13 PM, Steve Clark <sclark(a)netwolves.com> wrote:
> On 03/12/2013 07:04 AM, drago01 wrote:
>
> On Tue, Mar 12, 2013 at 11:37 AM, Reindl Harald <h.reindl(a)thelounge.net>
> wrote:
>
> Am 12.03.2013 09:55, schrieb drago01:
>
> On Mon, Mar 11, 2013 at 10:22 PM, seth vidal <skvidal(a)fedoraproject.org>
> wrote:
>
> On Mon, 11 Mar 2013 16:18:33 -0500
> Michael Cronenworth <mike(a)cchtml.com> wrote:
>
> On 03/11/2013 04:13 PM, seth vidal wrote:
>
> I want to encourage kids, teenagers, etc to explore the OS. We need
> them to be involved in CREATING and LEARNING. So I don't want to
> scare any of them off.
>
> My OLPC does not present any boot menu or prompt.
>
> That's not an argument for why we should not present one. It is an
> argument for why they should be.
>
> Sorry but that's nonsense. Pretty much all other operating systems do
> not display the boot loader by default and you see this as a reason
> for showing it?
> What kind of weird logic is that? Or do you really think we can have
> "we do show a screen that you won't care about most of the time on
> every boot" as a selling point for fedora?
>
> who cares about OTHER operating systems?
>
> You can't develop an operating system while living under a rock you
> have to look at what the competition does.
>
> if i would want their behavior i would install them
>
> Strawman.
>
> are you guys booting the whole day your machines that
> save 2 seconds is woth any discussion?
>
> Yes 2 seconds is a LONG time when your system is using an SSD.
> Booting should be instant there is no reason why we should have to
> wait before being able to use the system. (killing grub delay gets us
> closer to that goal).
>
> I'd say booting is a more common task then messing with bootloader
> options so lets optimize for the former rather then the later.
>
> How many times do you boot your system each day? 10? Okay thats a whole 20
> additional seconds.
Depends on the day ... but the point is I (and 99.99%) of computer
uses want to turn the device on and work with it.
Not mess with random options every time for the sake of messing with
random options.
11 years, 1 month
Re: Improving the Fedora boot experience
by Fabian Deutsch
> Von: Nicolas Mailhot
> Gesendet: 12.03.13 13:52 Uhr
> Le Mar 12 mars 2013 13:30, Fabian Deutsch a écrit :
> >> Von: Máirín Duffy
> >> On 03/11/2013 05:13 PM, seth vidal wrote:
> >> > Is one line of text really that significant of a problem to present?
> >>
> >> I'm pretty sure it is because of where we are in the process at that
> >> point. For example, translations - can we render Indic or CJK glyphs to
> >> the screen at this point in the boot process? I'm not quite sure that's
> >> possible? Another thing with translations is they take up additional
> >> disk space and I think (don't quote me on this, maybe Peter or one of
> >> the other grub experts could speak up) grub2 is a bit chubby compared to
> >> grub, but its space usage is a concern so to not have to have all the
> >> translation files for the languages we support would definitely be good.
> >> (grub2's girth is one of the reasons - on upstream's recommendation -
> >> that we don't allow installing the bootloader to a partition now.)
> >
> > What about pulling the message stuff into plymouth and using dracut to
> > trigger a reboot which shows the grub menu? Something along the lines:
> > "Press ESC to see deatils or 'b' to enter the bootloader"
>
> Plymouth is not a mandatory boot process element right now, precisely
> because people who cared about fast boot found it unnecessary, and people
> who cared about maintainability also found it got in the way. Please do
> not advocate hardwiring it again.
It's actually less about plymouth itself, it's more about the idea of avoiding
to use the grub2 menu and telling the user during (early) boot how the
bootloader can be accessed.
For a non-plymouth boot I'd just display one or none grub message
(non-localized) for a short time - which will be as un-fancy as the boot
itself.
- fabian
11 years, 1 month
Requesting assistance with packaging a web app: wikindx
by Ankur Sinha
Hi folks,
I've recently packaged and submitted wikindx[1] for review[2]. I have a
few queries with the rpm, since it's a web package and not really up my
alley:
I've placed all the files in %{_datadir} as the guidelines specify[3]
(and forbid the placement of files into /var/www). Now, how is a user
supposed to use the package? Is he supposed to copy these files
into /var/www and set his application up, or is there a way to make
httpd use the files from %{_datadir}? The wikindx application makes use
of the mysql database, and also needs directories where attachments etc.
will be kept when uploaded. How are these to be managed if httpd is to
use files from %{_datadir}? I've just observed that wikindx has a new
version since I packaged it. How does one do updates with web packages?
Do we just place the new files in %{_datadir} and let the admin copy
them over to /var/www and then run the update scripts etc.?
I haven't been able to find any detailed guidelines on the wiki on how
it's supposed to work. I'd be most grateful if someone adept at
packaging web apps would please assist me with these queries and the
package in general.
wikindx is a great tool to organize one's documents and bibliography and
would be a good application to provide to Fedora users who are also
researchers.
[1] http://wikindx.sourceforge.net/
[2] https://bugzilla.redhat.com/show_bug.cgi?id=882765
[3] http://fedoraproject.org/wiki/Packaging:Guidelines#Web_Applications
--
Many thanks,
Warm regards,
Ankur: "FranciscoD"
Please only print if necessary.
Looking to contribute to Fedora? Look here: https://fedoraproject.org/wiki/Fedora_Join_SIG
http://fedoraproject.org/wiki/User:Ankursinha
http://dodoincfedora.wordpress.com/
11 years, 1 month
Ruby 2.0 in F19/Rawhide
by Vít Ondruch
Hi everybody,
Ruby 2.0 just landed in F19/Rawhide [1]. Since the rebuild was not as
fast as one would wish, there will be probably plenty of broken
dependencies. I kindly ask you for patience or better for help with
fixing any remaining issues. Just rebuild is unfortunately not enough.
Please come to Ruby-SIG ML to discuss any issues or ping me on freenode
(vondruch).
Thank you
Vít
[1] https://fedorahosted.org/rel-eng/ticket/5463#comment:4
11 years, 1 month
f18-64: Video Resolution problem on a netbook ASUS 1225C-GRY015U
by Dario Lesca
Hi, I have buy this Asus netbook with Ubuntu pre-installed:
ASUS 1225C-GRY015U
http://www.monclick.it/schede/asus/1225C-GRY015U/1225c-gry015u.htm
With a Video integrate VGA compatible controller Intel Corporation Atom
Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09) and driver
gma500
(see below lspci and lshw)
At the first power on, I do not have start Ubuntu, then do not know if
the problem (see below) there is with Ubuntu, but I have install
straightaway Fedora 18 64 bit.
After install and update f18 (kernel 3.8.2-206.fc18.x86_64), I have try
to work into Gnome 3.6, but the video performance are very slow and
gnome-shell use too many CPU :
> top - 10:30:02 up 5 min, 3 users, load average: 1,50, 1,19, 0,56
> Tasks: 163 total, 2 running, 161 sleeping, 0 stopped, 0 zombie
> %Cpu0 : 59,5 us, 3,9 sy, 0,0 ni, 34,0 id, 0,0 wa, 1,6 hi, 1,0 si, 0,0 st
> %Cpu1 : 58,8 us, 2,6 sy, 0,0 ni, 37,0 id, 0,0 wa, 1,3 hi, 0,3 si, 0,0 st
> %Cpu2 : 71,7 us, 9,1 sy, 0,0 ni, 17,3 id, 0,0 wa, 1,6 hi, 0,3 si, 0,0 st
> %Cpu3 : 63,5 us, 5,2 sy, 0,0 ni, 29,3 id, 0,0 wa, 1,6 hi, 0,3 si, 0,0 st
> KiB Mem: 2039580 total, 942292 used, 1097288 free, 30068 buffers
> KiB Swap: 4095996 total, 0 used, 4095996 free, 439180 cached
> pid to signal/kill
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 1706 lesca 20 0 1949m 170m 48m S 246,3 8,5 2:13.89 gnome-shell
> 672 root 20 0 192m 49m 8244 S 19,2 2,5 0:13.80 Xorg
> 2042 lesca 20 0 115m 1444 1024 R 1,6 0,1 0:00.71 top
> 65 root 20 0 0 0 0 R 1,3 0,0 0:01.14 kworker/2:2
> 1985 lesca 20 0 720m 16m 11m S 1,3 0,8 0:01.51 gnome-terminal
> 1407 lesca 20 0 129m 2084 904 S 1,0 0,1 0:03.46 sshd
> 1473 lesca 20 0 115m 1464 1040 S 1,0 0,1 0:02.84 top
Furthermore, the video resolution is fixed to 1366x768 (16:9) and when I
attach a video projector (this is very important for me) with a 1024x768
resolution It's not possible to clone the monitors and see what what I'm
projecting. Switch via Fn+monitor I can only see netbook monitor or
projector...
Question: there is some way to resolve the high CPU usage of gnome-shell
and change the video resolution when projector is connect?
Many thanks.
lspci:
> 00:00.0 Host bridge: Intel Corporation Atom Processor D2xxx/N2xxx DRAM Controller (rev 03)
> 00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09)
> 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
> 00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
> 00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 02)
> 00:1c.2 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 3 (rev 02)
> 00:1c.3 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 4 (rev 02)
> 00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02)
> 00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02)
> 00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02)
> 00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02)
> 00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02)
> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
> 00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)
> 00:1f.2 SATA controller: Intel Corporation NM10/ICH7 Family SATA Controller [AHCI mode] (rev 02)
> 00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
> 02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)
> 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05)
--
Dario Lesca - sip:dario@solinos.it
(Inviato dal mio Linux Fedora18+Gnome3)
11 years, 1 month
Proposal: Rawhide tracker bug
by Kevin Fenzi
Greetings.
I'd like to propose we create a rawhide tracker bug.
Probibly name it: RawhideBlocker
(But I don't care what colour the bikeshed is)
This bug would be used for the following types of bugs against the
'rawhide' version:
- bugs that prevent the daily rawhide compose from completing.
(In practice this can only be a small subset of packages used for the
compose in the chroot)
- bugs that break the rawhide buildroot. In practice these are usually
noticed pretty quickly and the offending build is just untagged until
it can be fixed, but there could be cases where the fix is more
complex and has a bug associated with it.
- bugs that cause a large number of rawhide systems to be unbootable.
This would be things like dracut or kernel or glibc or systemd issues
that cause most rawhide installs to fail to boot.
(we could add additional criteria as we go)
The idea is that folks running rawhide could watch this bug and more
easily see issues that are major as they appear and know when they got
fixed. They could also add bugs to this and developers could see that
the bug is high priority and more resources could be brought to bear on
it. Additionally we could gain some insight into how often these kind
of bugs happen and how long it takes to fix them.
This would of course require people watching the bug to note any bugs
added to it that are NOT in the above criteria, but I think that should
be easily possible with enough people watching the bug.
Thoughts?
kevin
11 years, 1 month
Non responsive state for systemd
by David Highley
Twice now we have one Fedora 18 system where systemd seems to get into a
non responsive state. We are not able to get the status of any service
and we're not able to do an init 6 to restart the system.
Did notice today that a full process list showed a message about abrt
and something to the effect "nobody cared". We also see a number of
defunct processes that seem to never clear. So far the only remedy we
have found is a hard power cycle.
11 years, 1 month