| Summary: | [Update Candidate] drakx-net-2.22-1.mga4 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Thierry Vignaud <thierry.vignaud> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, herman.viaene, lewyssmith, neoser10, ottoleipala1, sysadmin-bugs, vzawalin1 |
| Version: | 4 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | advisory MGA4-32-OK MGA4-64-OK | ||
| Source RPM: | drakx-net-2.22-1.mga4.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Thierry Vignaud
2015-06-05 08:48:54 CEST
MGA4-64 on HP-Probook 6555b. No installation issues. BUT with old version, I had no real crashes, drakfont just did not import anything or remove a font. With the new version: it seems to import the Windows fonts, but when I choose to remove cyrillic, close drakfont, open it again and go back to the Uninstall dialogue, cyrillic is still there. So, the update does not break anything, but I cannot confirm it solves the font handling issues completely. CC:
(none) =>
herman.viaene Sorry drakfont is unrelated to this update. "How to reproduce:" was actually for drakxtools was this BR is about drakx-net What is drakfont is doing with draknet testing ? i can therry handle this we get this done. CC:
(none) =>
ozkyster Testing the draknet in MGA4-32 CC:
(none) =>
neoser10 Testing MGA4 x64 real hardware - some aspects only. I was able to reproduce Bug 12530 & Bug 13206, the 2nd & 3rd fixes in Description. The other problems cited there I know not, but will have a go if advised how to and I can (no wireless network). Updating to: libdrakx-net-2.22-1.mga4 drakx-net-applet-2.22-1.mga4 drakx-net-text-2.22-1.mga4 drakx-net-2.22-1.mga4 I confirm that the two "regressions due to the gtk+2 -> gtk+3 switch" bugs noted above are cured, OK. [I have commented them for the record]. So MGA4-64-OK partially. It needs a non-latin user for the 1st problem Bug 13354. CC:
(none) =>
lewyssmith Tested in MGA4-32 Real Hardware The #12530 does not appear in drakNFS, i have the user listing: neoser10 and guest both with the real UID, the same for the group listing. In drakSMB, I have in the add button a little popup asking for the username (listing) that listing is OK too. In drakSMB, I did not reproduce the #13206 for that is OK But, creating a share with drakNFS, using a big5 character after press the OK button to exit the drakNFS, if I return to drakNFS i get Ã¥ÂÂ天 in the share name And editing (modifing) a share with drakNFS, I get another folder named Ã¥ÂÂ天 in the same path to the original shared folder. Editing (modifing) a share with drakSMB, I do not get the another folder but, I have an error: Please select a folder to share. Please remember that i am latin charset user (Spanish) MGA4-64 on HP-Probook 6555b. No installation issues with Wifi connection (no ethernet cable connected). BUT I always define a fixed IP address at installation time in its Wifi network configuration routine. After rebooting after the drakx-net update, I found the PC got an IP address from the router. In MCC - Network Center, I found the expected settings (manual configuration, IP addresses), but those obviously had not been followed. Checking in MCC - Setup a new interface, the selector for manual configuration was NOT set. Changing that, I subsequently found all my other settings OK, let the routine restart the network, and then I got my fixed IP address back. Advisory committed to svn. Adding the feedback marker due do commments 6 and 7. Should this update to go as is, or wait for fixes for those issues? CC:
(none) =>
davidwhodgins It should go as it
Samuel Verschelde
2015-07-31 10:29:19 CEST
Whiteboard:
advisory feedback =>
advisory (In reply to Thierry Vignaud from comment #10) > It should go as it [is] In the light of this, & earlier tests, am OK'ing it both architectures. Whiteboard:
advisory =>
advisory MGA4-32-OK MGA4-64-OK
Dave Hodgins
2015-08-06 22:39:52 CEST
Keywords:
(none) =>
validated_update An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0080.html Status:
NEW =>
RESOLVED |