Re: [gentoo-user] How can I bring back Konqueror as my man page viewer?
On Saturday 18 Aug 2012 06:51:54 Nilesh Govindrajan wrote: On Sat 18 Aug 2012 06:21:55 AM IST, Nikos Chantziaras wrote: In KDE, I'm very used to simply type man:foo and have the man page of foo pop up immediately in Konqueror without having to open a terminal or anything. However, since I installed Chromium and making it my default browser, now man: brings up Chromium instead. That doesn't work; instead of displaying the man page, it downloads the *.bz2 from the local file system :-/ How can I set Konqueror to be the program that handles KDE's man: command? Umm, my default browser is Firefox, but when I open Konqueror and type man:ls I get to see the man page. But if I launch using Alt+F2, it opens Firefox. I think this needs some xdg tweaking, using xdg-mime. I don't know the type of URL for man:, else could have posted the command. The solution may be to find out the mime type of man pages, then create a .desktop file to handle it and use xdg-settings to set it up. I am thinking along the lines of: [Desktop Entry] # ... Exec=/usr/bin/konqueror %U MimeType=text/man_page_thing;text/bz2; or similar. However, the problem is that man pages are not a distinct mime type, but compressed text files. So this may cause konqueror to become the default application for opening all such mime types - which will be a pain. Not sure if a default application can be defined on a path basis, whereby only text files in e.g. /usr/share/man/man1/* would be opened with Konqueror. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] qt-webkit doesn't compile
- Mail original -
De: Kermit kermit@gmail.com
À: gentoo-user@lists.gentoo.org
Envoyé: Vendredi 17 Août 2012 07:04:44
Objet: Re: [gentoo-user] qt-webkit doesn't compile
On Fri, Aug 17, 2012 at 08:21:28AM +0200, Alain Didierjean wrote:
As title says, qt-webkit-4.8.2 doesnt compile on an amd64 config
and a new install.
Known problem ?
Known solution ?
Or should I fill a bug report ?
I'm sure that it works OK, it's not a bug. It must be your config
error. You may need to paste more detail infomation about the
errors.
$ eix qt-webkit
[I] x11-libs/qt-webkit
Available versions: (4) 4.7.4 4.8.1 4.8.2 **4.8.[1]
{{aqua dbus debug +exceptions +gstreamer (+)icu +jit kde pch
qpa}}
Installed versions: 4.8.2(4)(03:53:07 PM 07/28/2012)(exceptions
gstreamer jit -aqua -debug -icu -pch -qpa)
Homepage:http://qt-project.org/ http://qt.nokia.com/
Description: The WebKit module for the Qt toolkit
[1] qt /var/lib/layman/qt
You're right, I think I have some config problem with my new (and unfinished)
install. qt-webkit is part of
'emerge kde-meta'. To day I couldn't compile rrdtool. Now the problem is:
what's missing on my system?
That's where I need help.
Joined excerpts (hopefully meaningful) of returns from emerge after failure
err
Description: Binary data
rrerr
Description: Binary data
[gentoo-user] Re: Anyone compiled libreoffice-3.6.0.4 yet? [WORKAROUND]
On 08/09/2012 01:19 PM, walt wrote: This has been slow and painful so far. First, the build stops repeatedly because of zero-length library files. The gentoo libreoffice package doesn't yet compile with the 'binfilter' useflag set, so I unset it and the install completed. Second, the ebuild is using only one CPU out of four, so this is taking much longer than before. Ugh. This is a completely separate problem, which is very annoying but not fatal. There are some parts of the libreoffice build which take much longer than normal because 'make' uses 100% of CPU for long periods, while accomplishing very little. Those sections eventually complete, and the rest of the build proceeds at full speed by using all four of the CPU's. I think the reason that 'make' is being so slow is that certain kinds of child processes are segfaulting (i.e. become 'defunct') and make has to stop and respawn the failed processes until they succeed, which obviously takes a lot of extra time. The build does eventually finish in spite of all those defunct processes -- no idea why it works in the end, though. Can anyone confirm that 'make' is behaving the same way for you while building libreoffice-3.6.0.4?
Re: [gentoo-user] How can I bring back Konqueror as my man page viewer?
Am Samstag, 18. August 2012, 03:51:55 schrieb Nikos Chantziaras: In KDE, I'm very used to simply type man:foo and have the man page of foo pop up immediately in Konqueror without having to open a terminal or anything. However, since I installed Chromium and making it my default browser, now man: brings up Chromium instead. That doesn't work; instead of displaying the man page, it downloads the *.bz2 from the local file system :-/ How can I set Konqueror to be the program that handles KDE's man: command? open system-settings. Open mime/applications/whatever submenu (called 'Dateizuordnungen' in German). application-xtroff-man and application-xtroff-man-compressed should be the things you have to set. Click on 'embedded' and choose KManPart And that it is always shown in the embedded part. We are talking about KDE here - not gnome. It should not be necessary to fiddle with desktop files. -- #163933
[gentoo-user] Re: How can I bring back Konqueror as my man page viewer?
On 18/08/12 17:41, Volker Armin Hemmann wrote: Am Samstag, 18. August 2012, 03:51:55 schrieb Nikos Chantziaras: In KDE, I'm very used to simply type man:foo and have the man page of foo pop up immediately in Konqueror without having to open a terminal or anything. However, since I installed Chromium and making it my default browser, now man: brings up Chromium instead. That doesn't work; instead of displaying the man page, it downloads the *.bz2 from the local file system :-/ How can I set Konqueror to be the program that handles KDE's man: command? open system-settings. Open mime/applications/whatever submenu (called 'Dateizuordnungen' in German). application-xtroff-man and application-xtroff-man-compressed should be the things you have to set. Click on 'embedded' and choose KManPart And that it is always shown in the embedded part. We are talking about KDE here - not gnome. It should not be necessary to fiddle with desktop files. This is already set up that way. Except that x-troff-man-compressed is grayed out because there's no file extension listed.
[gentoo-user] revdep-rebuild problem
Hi, I'm using Gentoo for a couple of years and am quite amazed how good it works. So thanks to all involved in its develpoment. However, after today's update, when I run revdep-rebuild, I get the message * Checking dynamic linking consistency * broken /usr/lib64/libogrove.la (requires -lstdc++) * broken /usr/lib64/libospgrove.la (requires -lstdc++) * broken /usr/lib64/libostyle.la (requires -lstdc++) I would expect that revdep-rebuild re-builds the broken libraries, but instead it only re-builds app-text/openjade. Hence I can run revdep-rebuild again and again ad nauseam without any effect. Another, quite unrelated question: Whenever I run emerge --update --pretend I'm warned in advance if a portage update is available. It seems that emerge is able to warn about critical updates. On the other hand it happpened several times that *after* an update I've been told that my system is completely broken and will not re-boot unless I compile a new kernel. It would be nice if I can be warned *before* I run emerge without the --pretend option. Then I could postpone the update to the next weekend, when I have more time. My propsal is to add a warning similar to that I get when portage updates are available, so that users know in advance that a particular update will break the system. Of course, this mailing list is not the proper place for such suggestions. Can anybody tell me whom I should ask? Regards, Reinhard -- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotu...@web.de Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
Re: [gentoo-user] revdep-rebuild problem
Am Sonntag, 19. August 2012, 00:37:36 schrieb Reinhard Kotucha: Hi, I'm using Gentoo for a couple of years and am quite amazed how good it works. So thanks to all involved in its develpoment. However, after today's update, when I run revdep-rebuild, I get the message * Checking dynamic linking consistency * broken /usr/lib64/libogrove.la (requires -lstdc++) * broken /usr/lib64/libospgrove.la (requires -lstdc++) * broken /usr/lib64/libostyle.la (requires -lstdc++) so, find out which package these three belong to - and remove them. n emerge --update --pretend why pretend? I'm warned in advance if a portage update is available. It seems that emerge is able to warn about critical updates. only about portage updates. On the other hand it happpened several times that *after* an update I've been told that my system is completely broken and will not re-boot unless I compile a new kernel. really? never saw that. Only with xorg-drivers after a xorg-server update. It would be nice if I can be warned *before* I run emerge without the --pretend option. Then I could postpone the update to the next weekend, when I have more time. so you want portage to read every single ebuild, making the operation A LOT longer? I am sorry but I am not willing to waste so much time. My propsal is to add a warning similar to that I get when portage updates are available, so that users know in advance that a particular update will break the system. please enlighten me which update breaks a system. Can't remember one. Hm, back with libssco maybe? Of course, this mailing list is not the proper place for such suggestions. Can anybody tell me whom I should ask? bugzilla. Feature request. -- #163933
Re: [gentoo-user] revdep-rebuild problem
A few extra inline comments to reinforce what you just said: On Sun, 19 Aug 2012 01:02:24 +0200 Volker Armin Hemmann volkerar...@googlemail.com wrote: Am Sonntag, 19. August 2012, 00:37:36 schrieb Reinhard Kotucha: Hi, I'm using Gentoo for a couple of years and am quite amazed how good it works. So thanks to all involved in its develpoment. However, after today's update, when I run revdep-rebuild, I get the message * Checking dynamic linking consistency * broken /usr/lib64/libogrove.la (requires -lstdc++) * broken /usr/lib64/libospgrove.la (requires -lstdc++) * broken /usr/lib64/libostyle.la (requires -lstdc++) so, find out which package these three belong to - and remove them. n emerge --update --pretend why pretend? I'm warned in advance if a portage update is available. It seems that emerge is able to warn about critical updates. only about portage updates. and it's hard-coded: if (update available) print alarming message On the other hand it happpened several times that *after* an update I've been told that my system is completely broken and will not re-boot unless I compile a new kernel. really? never saw that. Only with xorg-drivers after a xorg-server update. It would be nice if I can be warned *before* I run emerge without the --pretend option. Then I could postpone the update to the next weekend, when I have more time. so you want portage to read every single ebuild, making the operation A LOT longer? I am sorry but I am not willing to waste so much time. Not only that but it's impossible for portage to know this before hand unless some dev puts the information in the ebuild. And the infra to check that does not exist. This is all right correct and proper. The only way to know an update breaks something is to build and test it. That's how Ubuntu does it: the dev builds it, installs it, finds it breaks stuff. So it gets committed to a repo with a warning that *the*dev*already*knows*about* The Gentoo dev DOES NOT know about it, and cannot either. These breakages are usually dependant on the environment they are used in and only the user knows that. As you and I well know, the compiling Gentoo user is that analogy of the Ubuntu DEV My propsal is to add a warning similar to that I get when portage updates are available, so that users know in advance that a particular update will break the system. please enlighten me which update breaks a system. Can't remember one. Hm, back with libssco maybe? jpeg-7, expat2 Those were dealt with in the only sane manner possible: ~arch: tough. Keep both pieces. arch: news item in advance Of course, this mailing list is not the proper place for such suggestions. Can anybody tell me whom I should ask? bugzilla. Feature request. -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] revdep-rebuild problem
Am Sonntag, 19. August 2012, 01:20:05 schrieb Alan McKinnon: A few extra inline comments to reinforce what you just said: My propsal is to add a warning similar to that I get when portage updates are available, so that users know in advance that a particular update will break the system. please enlighten me which update breaks a system. Can't remember one. Hm, back with libssco maybe? jpeg-7, expat2 both broke world, not system. -- #163933
[gentoo-user] Re: How can I bring back Konqueror as my man page viewer?
On Sat, 18 Aug 2012 18:10:01 +0300
Nikos Chantziaras rea...@gmail.com wrote:
On 18/08/12 17:41, Volker Armin Hemmann wrote:
Am Samstag, 18. August 2012, 03:51:55 schrieb Nikos Chantziaras:
In KDE, I'm very used to simply type man:foo and have the man
page of foo pop up immediately in Konqueror without having to
open a terminal or anything.
However, since I installed Chromium and making it my default
browser, now man: brings up Chromium instead. That doesn't
work; instead of displaying the man page, it downloads the *.bz2
from the local file system :-/
How can I set Konqueror to be the program that handles KDE's
man: command?
open system-settings. Open mime/applications/whatever submenu
(called 'Dateizuordnungen' in German).
application-xtroff-man
and
application-xtroff-man-compressed
should be the things you have to set. Click on 'embedded' and
choose KManPart
And that it is always shown in the embedded part.
We are talking about KDE here - not gnome. It should not be
necessary to fiddle with desktop files.
This is already set up that way. Except that x-troff-man-compressed
is grayed out because there's no file extension listed.
It's not greyed for me, and I just set both up that way, but KDE is
still opening man:foo with my default web browser, Firefox. KDE is
putting a decompressed copy in /var/tmp/kdecache-${username}/krun/ and
Firefox displays it ok, but I'd much rather be seeing it in Konqueror.
[gentoo-user] Re: How can I bring back Konqueror as my man page viewer?
On 19/08/12 04:30, »Q« wrote:
On Sat, 18 Aug 2012 18:10:01 +0300
Nikos Chantziaras rea...@gmail.com wrote:
On 18/08/12 17:41, Volker Armin Hemmann wrote:
Am Samstag, 18. August 2012, 03:51:55 schrieb Nikos Chantziaras:
In KDE, I'm very used to simply type man:foo and have the man
page of foo pop up immediately in Konqueror without having to
open a terminal or anything.
However, since I installed Chromium and making it my default
browser, now man: brings up Chromium instead. That doesn't
work; instead of displaying the man page, it downloads the *.bz2
from the local file system :-/
How can I set Konqueror to be the program that handles KDE's
man: command?
open system-settings. Open mime/applications/whatever submenu
(called 'Dateizuordnungen' in German).
application-xtroff-man
and
application-xtroff-man-compressed
should be the things you have to set. Click on 'embedded' and
choose KManPart
And that it is always shown in the embedded part.
We are talking about KDE here - not gnome. It should not be
necessary to fiddle with desktop files.
This is already set up that way. Except that x-troff-man-compressed
is grayed out because there's no file extension listed.
It's not greyed for me, and I just set both up that way, but KDE is
still opening man:foo with my default web browser, Firefox. KDE is
putting a decompressed copy in /var/tmp/kdecache-${username}/krun/ and
Firefox displays it ok, but I'd much rather be seeing it in Konqueror.
It only displays it here if there's no selection page (POSIX vs Linux
version of the man page; for example, man:longjmp).
[gentoo-user] What's the current state of Arduino on Gentoo?
I know (through simple discovery) that I can't simply emerge arduino and expect things to work. I know, because they don't, and I've already found these references: https://bugs.gentoo.org/show_bug.cgi?id=340042 https://bugs.gentoo.org/show_bug.cgi?id=378387 https://bugs.gentoo.org/show_bug.cgi?id=377039 and http://en.gentoo-wiki.com/wiki/Crossdev#AVR_Architecture (the instructions for which don't currently work) -- :wq
[gentoo-user] openrc cann't logger my boot log
Hi, everyone. For some unknown reason , my gentoo can't start up , but i can see the grub menu. So i went into ubuntu and chroot into the gentoo . Then i want to log some message to find out some thing . I have already enable the devfs and the rc_logger in the /etc/rc.conf ubuntu / # rc-service -l | grep devfs devfs ubuntu / # grep rc_logger /etc/rc.conf # rc_logger launches a logging daemon to log the entire rc process to rc_logger=YES After that , i reboot the computer . But it didn't have the /var/log/rc.log . Then i have no idea... Can anyone help ? and if you want more message , Please tell me. PS: my gentoo was normal last night . Then i didn't do some thing like upgrade the kernel . etc. -- 好好学习，天天向上！！！
[gentoo-user] Re: openrc cann't logger my boot log
It's my problem . Please ignore this mail..Sorry 2012/8/19 赵佳晖 jiahui.tar...@gmail.com Hi, everyone. For some unknown reason , my gentoo can't start up , but i can see the grub menu. So i went into ubuntu and chroot into the gentoo . Then i want to log some message to find out some thing . I have already enable the devfs and the rc_logger in the /etc/rc.conf ubuntu / # rc-service -l | grep devfs devfs ubuntu / # grep rc_logger /etc/rc.conf # rc_logger launches a logging daemon to log the entire rc process to rc_logger=YES After that , i reboot the computer . But it didn't have the /var/log/rc.log . Then i have no idea... Can anyone help ? and if you want more message , Please tell me. PS: my gentoo was normal last night . Then i didn't do some thing like upgrade the kernel . etc. -- 好好学习，天天向上！！！ -- 好好学习，天天向上！！！
