Re: [arch-general] Gnome 3, a bug?
On 05/04/2011 11:56 PM, Magnus Therning wrote: On Mon, May 2, 2011 at 17:54, Damien Churchill wrote: You can disable extensions, taken from the Gnome Shell extensions page [1] "Per-user and systemwide extensions can be disabled with the GSettings key org.gnome.shell.disabled-extensions" [1] http://live.gnome.org/GnomeShell/Extensions Yes, indeed it does say that, but it doesn't say how to actually disable them :-) I've tried to disable AlternateTab without success. Here's what I've tried so far: % gsettings set org.gnome.shell disabled-extensions "@as ['AlternateTab'] % gsettings set org.gnome.shell disabled-extensions "@as ['alternate-tab'] Has anyone else managed to disable extensions? /M Yes. Disabling the extension is pretty simple. Just go into the /usr/share/gnome-shell/extensions directory, rename the extension folder to .backup or something like .disabled. (just keep the original folder name in case you want to re-enable later). You can then do an alt-f2 "lg" and enter and go to the extensions tab to verify what is/is not there. To make the change alt+f2 "r" enter to restart the gnome-shell.
Re: [arch-general] Gnome 3, a bug?
On Mon, May 2, 2011 at 17:54, Damien Churchill wrote: > You can disable extensions, taken from the Gnome Shell extensions page [1] > > "Per-user and systemwide extensions can be disabled with the GSettings > key org.gnome.shell.disabled-extensions" > > [1] http://live.gnome.org/GnomeShell/Extensions Yes, indeed it does say that, but it doesn't say how to actually disable them :-) I've tried to disable AlternateTab without success. Here's what I've tried so far: % gsettings set org.gnome.shell disabled-extensions "@as ['AlternateTab'] % gsettings set org.gnome.shell disabled-extensions "@as ['alternate-tab'] Has anyone else managed to disable extensions? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus
Re: [arch-general] ArchLinux for mipsel (Loongson)
El 04/05/11 02:59, javier dijo: > On Sat, Apr 30, 2011 at 5:19 PM, Jonathan Beatty[via ArchLinux] > wrote: > > On 04/30/2011 04:52 PM, javier wrote: > >> Has the site have an English version? I'd like to look into packages > >> page, > >> and the aur packages page as well, to see if it make sense to try it > >> out... > >> > >> I moved back to debian some time back precisely cause arch was all for > >> x86, > >> so I didn't think it was going to support the lemote mini-pcs neither > >> loongson in general. I do have mini-pcs, so it's great news to me, :-)-- > >> View this message in context: > >> http://archlinux.2023198.n4.nabble.com/ArchLinux-for-mipsel-Loongson-tp3418315p3486638.html > >> Sent from the arch general mailing list archive at Nabble.com. > >> > > > > Parabola GNU/Linux, an Arch derivative, already has a MIPS port. :) It's > > functional. > > Hi, do you know which flags are being used to compile the loongson2f > packets? I'm referring to: > > -march=loongson2f -mtune=loongson2f -mabi=64 -O3 > > This can be found by looking at: > > /etc/makepkg.conf > > If I remember correctly, :-) > > Perhaps using loongson2f is not such great idea, since ther will come > a3, and others... However, using the 64bits ABI might increase > performance for some applications (loongson2f is not the fastest CPU > ever, so any help on performance is good)... Hey, We're using -march=loongson2f -mabi=n32 for the Parabola port. -- Salud! Nicolás Reynolds, xmpp:fa...@kiwwwi.com.ar omb:http://identi.ca/fauno blog:http://selfdandi.com.ar/ gnu/linux user #455044 OTR: C0CB1F0F 01DB5E18 2D634C2A A4626858 E7C7C3A2 http://parabolagnulinux.org http://endefensadelsl.org pgpm3pob09oDd.pgp Description: PGP signature
Re: [arch-general] ArchLinux for mipsel (Loongson)
On Sat, Apr 30, 2011 at 5:19 PM, Jonathan Beatty[via ArchLinux] wrote: > On 04/30/2011 04:52 PM, javier wrote: >> Has the site have an English version? I'd like to look into packages >> page, >> and the aur packages page as well, to see if it make sense to try it >> out... >> >> I moved back to debian some time back precisely cause arch was all for >> x86, >> so I didn't think it was going to support the lemote mini-pcs neither >> loongson in general. I do have mini-pcs, so it's great news to me, :-)-- >> View this message in context: >> http://archlinux.2023198.n4.nabble.com/ArchLinux-for-mipsel-Loongson-tp3418315p3486638.html >> Sent from the arch general mailing list archive at Nabble.com. >> > > Parabola GNU/Linux, an Arch derivative, already has a MIPS port. :) It's > functional. Hi, do you know which flags are being used to compile the loongson2f packets? I'm referring to: -march=loongson2f -mtune=loongson2f -mabi=64 -O3 This can be found by looking at: /etc/makepkg.conf If I remember correctly, :-) Perhaps using loongson2f is not such great idea, since ther will come a3, and others... However, using the 64bits ABI might increase performance for some applications (loongson2f is not the fastest CPU ever, so any help on performance is good)... Thanks, -- Javier. -- View this message in context: http://archlinux.2023198.n4.nabble.com/ArchLinux-for-mipsel-Loongson-tp3418315p3496900.html Sent from the arch general mailing list archive at Nabble.com.
Re: [arch-general] [signoff] cronie-1.4.7-7
[2011-05-04 23:21:50 +0300] Grigorios Bouzakis: > Shouldn't cronie have an optional dependency on smtp-server like dcron did? Indeed; good catch. I'll make a new package. -- Gaetan
Re: [arch-general] Hamster removed?
On 05/04/2011 11:10 PM, rikuthero...@gmail.com wrote: Hi! I'm not sure if this is the proper list to ask this, but I'll try :-) I just notice that the package "hamster-applet" is no longer avaiable. I can understand that the applet will no longer works with GNOME3, but that package included more stuff like: - An standalone application, without any need of use gnome-panel - A console client Is there any chance to create a new package that includes those applications? I use hamster a lot and will love to still have it from Arch repositories. Thanks! you can update hamster applet to 2.91.2 and push it into aur. -- Ionuț
Re: [arch-general] [signoff] cronie-1.4.7-7
Gaetan Bisson wrote:
>
> A new version of cronie is in [testing]. The only difference with the
> previous one is that it does not have replaces=('dcron') and has
> conflicts=('cron').
>
> So users who wish to keep using dcron have nothing to do, but cronie
> will be the default cron daemon on new installs in the future.
Shouldn't cronie have an optional dependency on smtp-server like dcron did?
Greg
Re: [arch-general] pacman "Targets" sort order
I don't know if they were sorted alphabetically before. But you could use 'pacman -Sy && pacman -Qu | sort' to get them sorted in that way. Wim On Wed, May 4, 2011 at 9:23 PM, Grigorios Bouzakis wrote: > David C. Rankin wrote: > > Guys, > > > >I don't know if I am remembering correctly, but I thought the upgrade > > "Targets" were sorted alphabetically by name prior to the pacman upgrade > a > > month or two ago. Now, it looks like they are listed either by > repository, > > then alphabetized or some other logic that ends up -- almost > alphabetized. > > Specifically: > > > > Targets (35): bluez-4.93-1 run-parts-3.4.4-1 ca-certificates-20110421-3 > >dcron-4.5-2 libzip-0.10-1 ebook-tools-0.2.1-2 eina-svn- > >58920-1 eet-svn-58955-1 evas-svn-58958-1 > ecore-svn-58945-1 > >e_dbus-svn-58954-1 embryo-svn-58829-1 edje-svn-58887-1 > >pciutils-3.1.7-4 udev-167-2 eeze-svn-58668-1 efreet- > >svn-58672-1 e-svn-58940-1 gutenprint-5.2.7-1 > hdf5-1.8.6-1 > >libidn-1.21-1 libxcb-1.7-2 networkmanager-0.8.999-1 > openssh- > >5.8p2-1 python2-cairo-1.10.0-1 > python2-distribute-0.6.16-1 > >qt-4.7.3-1 rp-pppoe-3.10-6 sudo-1.8.1.p1-1 telepathy- > >qt4-0.5.16-1 zziplib-0.13.60-1 texlive-bin-2010.1-8 > texlive- > >core-2010.22154-1 udev-compat-167-2 usbutils-002-2 > > > > bluez -> run-parts -> ca-certificates?? > > > >In the past, I would scan the list to make sure there were no updates > that > > I didn't want or that I needed to put off due to bugs or what not. Now > I've > > been bitten a time or two by searching through long Target lists and > > confirming there were no unwanted updates only to find out that an > unwanted > > update was alphabetized higher-up or lower in the target list. > > > >Has the target list always sorted by repo, then by name --or-- was the > list > > fully sorted by name earlier? If so, is it easy to change? > > > >In short lists, it's not really a big deal, but when you have over 100 > > targets, having them sorted by name really helps. What say the pacman > gurus? > > It looks to me your list is alphabetically sorted. Did you take > dependencies into account? > > > Greg >
[arch-general] Hamster removed?
Hi! I'm not sure if this is the proper list to ask this, but I'll try :-) I just notice that the package "hamster-applet" is no longer avaiable. I can understand that the applet will no longer works with GNOME3, but that package included more stuff like: - An standalone application, without any need of use gnome-panel - A console client Is there any chance to create a new package that includes those applications? I use hamster a lot and will love to still have it from Arch repositories. Thanks! -- Pablo Recio Quijano Desarrollador Django Yaco Sistemas - http://www.yaco.es/
Re: [arch-general] Pruning the bugtracker
On Wed, May 4, 2011 at 9:19 PM, Grigorios Bouzakis wrote: > JM wrote: >> I have browsed through all High and Medium severity bugreports and >> categorized some of them here: >> https://wiki.archlinux.org/index.php/User:Fijam . >> >> 'Candidates for closing' are divided into two categories: strong and >> weak. Strong candidates have not been replied to in over 4 months >> (with some bugs seeing no activity for over a year) with the last >> comment asking for more information or confirmation whether the bug >> still persists. I have not yet started issuing closure requests but >> will do so in two weeks if noone replies to those reports. Weak >> candidates have not been replied to in less than four months, the >> resolution of the bug was unclear or the original submitter found >> another solution and failed to provide any more information. I will >> wait for another month before issuing closure requests. Note: jelle >> van der waa (jelly) asked for confirmation on many of those bugs and >> deserves all the praise. >> >> I have also identified some bugs where more input or a confirmation of >> a fix is needed and asked for it. Will try to do initial triaging on >> those bugs or mark them as candidates for closing if the submitter >> fails to respond. >> >> There was also a couple of bug reports that seemed to be going >> nowhere. There was either a failure in communication, unresolved >> argument, a patch with no feedback from the developers or a request to >> split a bug into two or more specific reports. These should probably >> be reviewed again. >> >> There are still Low and Very Low severity bugs to go through, so >> perhaps some other user wants to pick up where I left :) > > Thanks for doing this. You could have used the already set up > https://wiki.archlinux.org/index.php/Bug_Day_TODO page though instead of > your user page. > That might need a bit of cleaning up but if you're willing to transfer > properly the ones on your page there i will help with this if you lack > the time to invest doing the clean up yourself. > > > Greg > I have seen this page but it is a bit of a mess. I will clean it up and merge both lists during the weekend, possibly adding a category 'candidates for removal' based on my own criteria if that's OK. JM
Re: [arch-general] pacman "Targets" sort order
David C. Rankin wrote: > Guys, > >I don't know if I am remembering correctly, but I thought the upgrade > "Targets" were sorted alphabetically by name prior to the pacman upgrade a > month or two ago. Now, it looks like they are listed either by repository, > then alphabetized or some other logic that ends up -- almost alphabetized. > Specifically: > > Targets (35): bluez-4.93-1 run-parts-3.4.4-1 ca-certificates-20110421-3 >dcron-4.5-2 libzip-0.10-1 ebook-tools-0.2.1-2 eina-svn- >58920-1 eet-svn-58955-1 evas-svn-58958-1 ecore-svn-58945-1 >e_dbus-svn-58954-1 embryo-svn-58829-1 edje-svn-58887-1 >pciutils-3.1.7-4 udev-167-2 eeze-svn-58668-1 efreet- >svn-58672-1 e-svn-58940-1 gutenprint-5.2.7-1 hdf5-1.8.6-1 >libidn-1.21-1 libxcb-1.7-2 networkmanager-0.8.999-1 openssh- >5.8p2-1 python2-cairo-1.10.0-1 python2-distribute-0.6.16-1 >qt-4.7.3-1 rp-pppoe-3.10-6 sudo-1.8.1.p1-1 telepathy- >qt4-0.5.16-1 zziplib-0.13.60-1 texlive-bin-2010.1-8 texlive- >core-2010.22154-1 udev-compat-167-2 usbutils-002-2 > > bluez -> run-parts -> ca-certificates?? > >In the past, I would scan the list to make sure there were no updates that > I didn't want or that I needed to put off due to bugs or what not. Now I've > been bitten a time or two by searching through long Target lists and > confirming there were no unwanted updates only to find out that an unwanted > update was alphabetized higher-up or lower in the target list. > >Has the target list always sorted by repo, then by name --or-- was the > list > fully sorted by name earlier? If so, is it easy to change? > >In short lists, it's not really a big deal, but when you have over 100 > targets, having them sorted by name really helps. What say the pacman gurus? It looks to me your list is alphabetically sorted. Did you take dependencies into account? Greg
Re: [arch-general] Pruning the bugtracker
JM wrote: > I have browsed through all High and Medium severity bugreports and > categorized some of them here: > https://wiki.archlinux.org/index.php/User:Fijam . > > 'Candidates for closing' are divided into two categories: strong and > weak. Strong candidates have not been replied to in over 4 months > (with some bugs seeing no activity for over a year) with the last > comment asking for more information or confirmation whether the bug > still persists. I have not yet started issuing closure requests but > will do so in two weeks if noone replies to those reports. Weak > candidates have not been replied to in less than four months, the > resolution of the bug was unclear or the original submitter found > another solution and failed to provide any more information. I will > wait for another month before issuing closure requests. Note: jelle > van der waa (jelly) asked for confirmation on many of those bugs and > deserves all the praise. > > I have also identified some bugs where more input or a confirmation of > a fix is needed and asked for it. Will try to do initial triaging on > those bugs or mark them as candidates for closing if the submitter > fails to respond. > > There was also a couple of bug reports that seemed to be going > nowhere. There was either a failure in communication, unresolved > argument, a patch with no feedback from the developers or a request to > split a bug into two or more specific reports. These should probably > be reviewed again. > > There are still Low and Very Low severity bugs to go through, so > perhaps some other user wants to pick up where I left :) Thanks for doing this. You could have used the already set up https://wiki.archlinux.org/index.php/Bug_Day_TODO page though instead of your user page. That might need a bit of cleaning up but if you're willing to transfer properly the ones on your page there i will help with this if you lack the time to invest doing the clean up yourself. Greg
[arch-general] pacman "Targets" sort order
Guys, I don't know if I am remembering correctly, but I thought the upgrade "Targets" were sorted alphabetically by name prior to the pacman upgrade a month or two ago. Now, it looks like they are listed either by repository, then alphabetized or some other logic that ends up -- almost alphabetized. Specifically: Targets (35): bluez-4.93-1 run-parts-3.4.4-1 ca-certificates-20110421-3 dcron-4.5-2 libzip-0.10-1 ebook-tools-0.2.1-2 eina-svn- 58920-1 eet-svn-58955-1 evas-svn-58958-1 ecore-svn-58945-1 e_dbus-svn-58954-1 embryo-svn-58829-1 edje-svn-58887-1 pciutils-3.1.7-4 udev-167-2 eeze-svn-58668-1 efreet- svn-58672-1 e-svn-58940-1 gutenprint-5.2.7-1 hdf5-1.8.6-1 libidn-1.21-1 libxcb-1.7-2 networkmanager-0.8.999-1 openssh- 5.8p2-1 python2-cairo-1.10.0-1 python2-distribute-0.6.16-1 qt-4.7.3-1 rp-pppoe-3.10-6 sudo-1.8.1.p1-1 telepathy- qt4-0.5.16-1 zziplib-0.13.60-1 texlive-bin-2010.1-8 texlive- core-2010.22154-1 udev-compat-167-2 usbutils-002-2 bluez -> run-parts -> ca-certificates?? In the past, I would scan the list to make sure there were no updates that I didn't want or that I needed to put off due to bugs or what not. Now I've been bitten a time or two by searching through long Target lists and confirming there were no unwanted updates only to find out that an unwanted update was alphabetized higher-up or lower in the target list. Has the target list always sorted by repo, then by name --or-- was the list fully sorted by name earlier? If so, is it easy to change? In short lists, it's not really a big deal, but when you have over 100 targets, having them sorted by name really helps. What say the pacman gurus? -- David C. Rankin, J.D.,P.E.
[arch-general] Pruning the bugtracker
I have browsed through all High and Medium severity bugreports and categorized some of them here: https://wiki.archlinux.org/index.php/User:Fijam . 'Candidates for closing' are divided into two categories: strong and weak. Strong candidates have not been replied to in over 4 months (with some bugs seeing no activity for over a year) with the last comment asking for more information or confirmation whether the bug still persists. I have not yet started issuing closure requests but will do so in two weeks if noone replies to those reports. Weak candidates have not been replied to in less than four months, the resolution of the bug was unclear or the original submitter found another solution and failed to provide any more information. I will wait for another month before issuing closure requests. Note: jelle van der waa (jelly) asked for confirmation on many of those bugs and deserves all the praise. I have also identified some bugs where more input or a confirmation of a fix is needed and asked for it. Will try to do initial triaging on those bugs or mark them as candidates for closing if the submitter fails to respond. There was also a couple of bug reports that seemed to be going nowhere. There was either a failure in communication, unresolved argument, a patch with no feedback from the developers or a request to split a bug into two or more specific reports. These should probably be reviewed again. There are still Low and Very Low severity bugs to go through, so perhaps some other user wants to pick up where I left :) Cheers, JM
Re: [arch-general] bugtracker registration
On Wednesday 04 May 2011 19:12:07 Steven Vancoillie wrote: > I would like to report a bug and thus I followed the procedure for > registering on the Arch Linux Bugtracker. However, I haven't received any > confirmation code (e-mail) after about a day. Can it be that this takes > such a long time? Re-registering doesn't work, it says the username is > already taken. On the other hand, when trying to use the lost password > retrieval, it tells me the user does not exist. Please send me your username and/or your mail address associated. -- Andrea
[arch-general] bugtracker registration
Hi, I would like to report a bug and thus I followed the procedure for registering on the Arch Linux Bugtracker. However, I haven't received any confirmation code (e-mail) after about a day. Can it be that this takes such a long time? Re-registering doesn't work, it says the username is already taken. On the other hand, when trying to use the lost password retrieval, it tells me the user does not exist. Thank you for your help. Steven
Re: [arch-general] qtcurve for gtk3/GNOME3?
On 05/04/2011 10:10 AM, Ray Rashif wrote: On 3 May 2011 08:19, David Rosenstrauch wrote: I'm not loving this GNOME3 upgrade. Latest irritation is that all the gtk apps are no longer picking up the qtcurve theme that I use on all my apps to make a uniform desktop. Is there any way to enable this? You may try a different style: * AUR/oxygen-gtk3-git * ln -s /usr/share/themes/oxygen-gtk/gtk-3.0 ~/.config/gtk-3.0 Should work in non-KDE environments. Tnx for the heads up. DR
Re: [arch-general] qtcurve for gtk3/GNOME3?
On 3 May 2011 08:19, David Rosenstrauch wrote: > I'm not loving this GNOME3 upgrade. Latest irritation is that all the gtk > apps are no longer picking up the qtcurve theme that I use on all my apps > to make a uniform desktop. Is there any way to enable this? You may try a different style: * AUR/oxygen-gtk3-git * ln -s /usr/share/themes/oxygen-gtk/gtk-3.0 ~/.config/gtk-3.0 Should work in non-KDE environments. -- GPG/PGP ID: 8AADBB10
Re: [arch-general] strange files
2011/5/3 Juan Diego Tascón : > > Hi, > > I'm getting files with random names created in my home directory, last > one was: s5EZVJ and they always have the same content: "Hello World", > is anyone else getting the same? no ... i am definitely not getting anything like this, and i would be _extremely_ surprised to learn of anyone else with this rather odd "problem". it sounds like you have some rogue (test?) script running that never got killed, or similar ... i'd start grepping the FS, the output of `lsof`, and other /proc magic files for references to you homedir and/or the words 'Hello' or 'World'. maybe use inotify or similar to catch the offender red-handed. maybe others have more specific/concrete suggestions. ... at the risk of sounding like an ass, this post made me laugh pretty hard :-) C Anthony
Re: [arch-general] strange files
On Tue, May 03, 2011 at 09:30:23AM -0500, Juan Diego Tascón wrote: > Hi, > > I'm getting files with random names created in my home directory, last > one was: s5EZVJ and they always have the same content: "Hello World", > is anyone else getting the same? Since when did this start happening? Also, who else apart from you has access to this machine? PS: And no at least i am not experiencing this issue.
