[Fedora QA] #177: Create script to move/rename wiki pages
by fedora-badges
#177: Create script to move/rename wiki pages
-------------------------+--------------------------------------------------
Reporter: jlaska | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Wiki | Version:
Keywords: |
-------------------------+--------------------------------------------------
Because of ticket#154 ... we could use help from a quick python script
that would use the mediawiki api (and python-simplemediawiki) to rename
existing category pages. I have some sample scripts I can point someone
to if interested.
The mediawiki api (see http://fedoraproject.org/w/api.php) explains the
access details and arguments. We just need a script that we can provide a
new and an old name, and it will handle renaming the category.
Optional bonus would be a script that moved all pages from one category,
to another.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/177>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 10 months
nouveau and multimonitor with mutter problems
by Gianluca Cecchi
Hello,
I'm trying here as F15 has been just released. Perhaps same problem in
rawhide too..
During latest days I have tested my XPS M1330 Dell laptop with nvidia
proprietary drivers and now I'm evaluating switching to nouveau.
I have final F15 x86_64.
No xorg.conf file and no nvidia rpm bits.
I connect a 19" monitor to vga.
Starting in fallback mode all is ok and I can configure laptop
(1280x800) under monitor (1280x1024).
In gdm the login box is inside laptop and I can see background inside
the monitor too.
After login my top bar is positioned at top of laptop display.
I can drag windows from top to bottom display crossing the top bar and
vice versa.
The status bar is at bottom of laptop.
If I set the default gnome 3 with effects, I have the same behaviour
at gdm login, and the same positioning of top bar after login.
But Inside the external monitor I see the background image, without
being able to put windows in this monitor.
When dragging a window it stops right under the top bar, no way. And
all new windows are opened inside laptop display.
If I use the classic Alt+drag operation I can traverse top bar and
arrive with top part of this window about half height of the external
monitor....
My nvidia adapter is:
01:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce
8400M GS] (rev a1)
In system settings --> graphics I see the driver detected as
Gallium 0.4 on NV86
in both fallback mode and standard mode xrandr gives:
Screen 0: minimum 320 x 200, current 1280 x 1824, maximum 8192 x 8192
LVDS-1 connected 1280x800+0+1024 (normal left inverted right x axis y
axis) 287mm x 180mm
1280x800 60.0*+
1024x768 59.9
800x600 59.9
640x480 59.4
720x400 59.6
640x400 60.0
640x350 59.8
VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y
axis) 338mm x 270mm
1280x1024 60.0*+ 75.0
1152x864 75.0
1024x768 75.1 70.1 60.0
832x624 74.6
800x600 72.2 75.0 60.3 56.2
640x480 72.8 75.0 66.7 60.0
720x400 70.1
HDMI-1 disconnected (normal left inverted right x axis y axis)
$ cat /proc/cmdline
ro root=UUID=91e7d1a8-7208-491c-ba3e-47ec918f66d6 rd_NO_LUKS rd_NO_LVM
rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16
KEYTABLE=us rhgb quiet elevator=deadline
$ lsmod|grep nouve
nouveau 525018 2
ttm 55120 1 nouveau
drm_kms_helper 27515 1 nouveau
drm 187984 4 nouveau,ttm,drm_kms_helper
i2c_algo_bit 5014 1 nouveau
i2c_core 25468 6
i2c_i801,videodev,nouveau,drm_kms_helper,drm,i2c_algo_bit
video 12432 1 nouveau
$ lsmod|grep nvi
$
Any hint on using gnome 3 standard or otherwise to have fallback mode
to work as a full gnome 2.x?
Thanks in advance,
Gianluca
12 years, 11 months
DVD F14 -> F15 Problems
by Garry Williams
I upgraded to F15 from F14 using the DVD yeterday. I experienced a
few glitches:
1. I was not asked to include the updates repository during the
update process. Sad. Now I will have to do an update after first
boot.
2. This is apparently a general problem not really related to the
specific upgrade. I noticed that the upgrade process was slow. The
disk just churned forever. After booting for the first time, I ran
yum erase on my debuginfos so that the subsequent yum update would not
pull those in. This erase command took way too long.
I think the rpm database gets into a state that needs attention. This
fixed it:
sudo rm -f /var/lib/rpm/__db.001 /var/lib/rpm/__db.002 \
/var/lib/rpm/__db.003 /var/lib/rpm/__db.004
sudo rpm --rebuilddb
After that, yum operations sped up an order of magnitude.
3. The first boot ended at multiuser.target instead of
graphical.target. When I entered the command
sudo systemctl isolate graphical.target
kdm came up and allowed a normal desktop login.
Hmmm. I compared another system that I upgraded using preupgrade and
that one had the correct graphical.target file linked in
/etc/systemd/system . So I had to do this to correct the problem:
sudo rm /etc/systemd/system/default.target
sudo ln -s /lib/systemd/system/runlevel5.target \
/etc/systemd/system/default.target
I don't know why this happened with the DVD upgrade and not with the
preupgrade upgrade.
4. I then did a yum update and waited a few hours while over 500
packages were downloaded and updated/installed. This was almost 1GB
of downloads. Most packages did not have delta rpms.
5. I run KDE and after logging in and starting Kmail, it refused to
start, complaining about akonadi not being available:
Test 5: ERROR
...
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
<repeated many times>
Test 10: ERROR
...
Akonadi control process not registered at D-Bus.
Test 15: ERROR
...
No resource agents found.
(Wow, this is a fragile piece in kdepim.)
The fix for this ended up being:
sudo yum --enablerepo=kde-testing update
Now the system is operating as expected and all looks good. I'd be
happy to open any bugs any of you think should be reported, but I
think others have already encountered most of this stuff.
Thank you for another excellent Fedora release.
--
Garry Williams
12 years, 11 months
Gnome 3
by Lawrence E Graves
I have read all of the opinions about Gnome 3 and was reluctant to
participate in the discussion but something would not let me leave it
alone.
Many of you have purchased new cars and I am quite sure there were some
things on the car that were not quite what you thought they would be but
I asked the question "Did you go to the dealer and complain or did you
just work it out."
Yes, I have only been using Fedora for about 7 years and Gnome 3 is
"NEW" but I have discovered that every day I wake up is new but I just
work it out.
I believe if we concentrate on the solutions rather than the problems it
will all get resolved. I just wish I could help on the level needed to
help fix those things that are broken. Enough said. I have learned to
stay in the boat whatever the storms may be.
--
Lawrence E Graves <lgraves(a)risingstarmbc.com>
All things are workable but not all things work.
Prov. 3:5&6
12 years, 11 months
My Fedora 15 beta experiences so far
by Alan
I have to admit, this is the most painful Fedora installation I have ever
done. (And I have used them all.)
The networking came up as IPv6 *only*. My router does not do IPv6 and my
ISP (Qwest) does not know when their network ever will. In order to get it
to work I had to hack files in /etc/sysconfig and use dhclient to get an
address since the Network Manager applet is dumbed down to absolute
worthlessness. (More on that later.) The networking problems seem to have
been fixed, but there were far too many of them. (Having no default route
for fixed IP addresses was a pain.)
If I were to grade Gnome 3 it would be "incomplete". It looks nice, but
it is missing large chunks of functionality. For example, network
configuration is useless. Gnome screen saver's config panel is no where to
be found. To switch the desktop with a mouse now takes 2-3 clicks where it
used to take one. There are no applets to be found. The desktop is bare,
unless you use an the Gtweakui program to hack it. (Which most users will
not ever know about since it is not installed by default.) The option to
use the "classic style" is a lie. It is still Gnome 3, but with a
kinda-sorta Gnome 2 look. (With all the above still missing.)
Gnome 2 had similar problems. When it was first released, it was dumbed
down and was lacking most of the functionality of Gnome 1. Now that they
finally have Gnome 2 working well I guess they felt they had to pitch it
all out and start over. This new design looks nice, but is not that
usable. A UI should make it easier to get to what you want to do, not add
useless mouse clicks.
My biggest complaint though is the kernel. I am getting kernel panics in
ext4! (When I can get a log I will post it. It does not get written to
disk since the filesystem dies.)
Another thing... I cannot find a way to disable the Nouveau kernel module.
I have tried all the methods that worked before (rdblacklist and the
modules blacklist.) Nothing seems to work. I am going to have to rebuild
the kernel rpm. Why is this more difficult?
The reason I went to this version when I did was due to a sort of double
bind. Fedora 13 uses 2.6.34. USB3 does not work well with that kernel. (I
have already spoken with the maintainer. She thinks she knows the cause
and is going to backport the patch.) 2.6.35+ works with USB3, but another
program I use often does not work with my hand-rolled kernel. (Threading
issue.) Upgrade seemed like a good option. Now I am not so sure.
Hopefully I will be able to make this thing work. I may have to go to KDE
for a bit until the Gnome developers finish writing it. (How long that
will take, I have no idea...)
12 years, 11 months
fedora 15 final - startup applications
by Johan Scheepers
Good day,
Just installed fedora 15 - gnome 3 not possible due to card limitations.
Operating on fallback.
I do not seem to locate the option to place applications to startup
while booting.
In the past it was easy.
Kindly point me in the right direction please.
Thanks
Johan S
12 years, 11 months
Fedora 14 to 15: no getty's
by A.J. Werkman`
I just updated a F14 system to F15. After the update I can't login via
the console. Login through the network over ssh is possible.
Does this mean that the update procedure hasn't translated getty
startup procedure to systemd conventions? As I still am not quite
familiar with systemd, can anyone tell me how to verify this and how to
correct this.
Koos.
12 years, 11 months
Heads up: impending IPv6 Test Day
by Adam Williamson
Hey, folks. If you follow the trac ticket notifications on test@ you may
have noticed this already, but I know it's easy to tune those out, and
I'm CCing devel@ so people following that list know about this too.
We're planning a Fedora IPv6 Test Day to coincide with World IPv6 Day on
June 8. This has been kicked off by some folks inside Red Hat whose job
it is to understand IPv6 (those poor, poor kids), so thanks to Linda and
her team for bringing it to the Fedora community. We have a trac ticket
for co-ordinating the event here:
https://fedorahosted.org/fedora-qa/ticket/192
and the Wiki page for it is here:
https://fedoraproject.org/wiki/QA/Test_Day:2011-06-08_IPv6
it would be really good if people can pencil in this event on their
calendars so we can get some testing of Fedora 15's IPv6 preparedness,
and it would also be great if those who understand what the hell they're
doing with IPv6 could check over the Wiki page for accuracy and
completeness. Finally it would also help if people who don't understand
what the hell they're doing with IPv6 - like me! - could try and follow
the instructions, and let us know - via this thread, or the trac ticket
- if they struggle or find something unclear or don't seem to be able to
make it work as intended, so we can improve the instructions. I've
already noted, for example, that it's not particularly clear what you
should do if you're using a router - whether to try and set the tunnel
up on the router, or whether you can just do it on one of the machines
behind the router.
Thanks everyone!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
12 years, 11 months
gnome-shell-extensions-drive-menu not ejecting devices
by Pratyush Sahay
Hello,
In the PackageKit GUI (Add/Remove Software) , the shell-extension :
gnome-shell-extensions-drive-menu has the following description :
" Adds a menu in the system status area that tracks removable disk
devices attached and offers to browse them and eject/unmount them "
However, clicking on the mounted devices only opens nautilus for browising
the device, but doesnt eject the drives. I even tried clicking on the far
end of the menu where the mounted symbol comes, but that doesnt help.
--
Regards,
Pratyush Sahay
12 years, 11 months
Release criteria updates: desktop question
by Adam Williamson
Hey, folks. Some release criteria stuff!
I've created the F16 criteria pages, copied across from F15. I added
some criteria we agreed on back in October 2010 to the Final page;
somehow we managed not to add these onto the F15 page, but they're in
there now. Those are:
* The final release notes (in both branded and generic form) from the
Documentation team must be present in the release repository in packaged
form
* A spin-kickstarts package which contains the exact kickstart files
used to build the release must be present in the release repository. The
included kickstarts must define the correct set of release repositories
* A fedora-release package and a generic-release package appropriately
versioned and containing the correct names, information and repository
configuration for a final Fedora release (as opposed to a pre-release)
must be present in the release repository
I also added the recently-agreed logger criterion to the Alpha page:
* A system logging infrastructure must be available and enabled by
default. It must provide at least basic local file-based logging of
kernel messages, and allow other components to write log messages. This
must be done in accordance with relevant standards accepted by the
Project
Finally, I have a new proposal for the issue of 'supported' desktops,
which is blocking another planned criterion that we've been meaning to
add for a while. I'm now proposing the term 'release-blocking desktops':
it's simple, it does what it says on the tin, and it doesn't imply any
value judgments about the desktops in question. How does that sound?
So all current reference to 'desktop' or 'the desktop' would be replaced
by 'release-blocking desktops', and the proposed image size criterion
would read:
* The network installation image, DVD image, and live images for
release-blocking desktops must meet current size requirements
Feedback please! :) For reference, the new F16 pages are:
https://fedoraproject.org/wiki/Fedora_16_Alpha_Release_Criteria
https://fedoraproject.org/wiki/Fedora_16_Beta_Release_Criteria
https://fedoraproject.org/wiki/Fedora_16_Final_Release_Criteria
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
12 years, 11 months
