Bug 11838 - Fresh install of Mageia 4 Beta, fully updated. Google Chrome doesn't install using GUI
Summary: Fresh install of Mageia 4 Beta, fully updated. Google Chrome doesn't install ...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2013-12-01 04:30 CET by sreejiraj eluvangal
Modified: 2015-03-31 02:57 CEST (History)
1 user (show)

See Also:
Source RPM: google-chrome-current
CVE:
Status comment:


Attachments
screenshot (178.94 KB, image/png)
2013-12-01 04:41 CET, sreejiraj eluvangal
Details

Description sreejiraj eluvangal 2013-12-01 04:30:16 CET
Description of problem:


Version-Release number of selected component (if applicable):Latest Google Chrome from Google's Google Chrome official download page (as of 1 Dec 2013.)


How reproducible:Always


Steps to Reproduce:
1.Go to Google.com/chrome
2.Download the 64 bit rpm installer package
3.Click and install using software installer
4.It says "A problem that we were not expecting has occurred.."
5.Try to install the package by urpmi - it will show "In order to satisfy the 'sendmail-command' dependency, one of the following packages is needed:
 1- postfix-2.10.2-2.mga4.x86_64: Postfix Mail Transport Agent (to install)
 2- sendmail-8.14.7-3.mga4.x86_64: A widely used Mail Transport Agent (MTA) (to install)..."
6.Clicking yes to installing one of the dependencies helps you install Google Chrome on command line.

Reproducible: 

Steps to Reproduce:
Comment 1 sreejiraj eluvangal 2013-12-01 04:39:43 CET
I used the Live DVD Gnome to install mageia on my system.
Comment 2 sreejiraj eluvangal 2013-12-01 04:41:04 CET
Created attachment 4551 [details]
screenshot
Comment 3 Manuel Hiebel 2013-12-01 19:05:33 CET
using command: urpmi -debug /path/to/the.rpm give what ?

Keywords: (none) => NEEDINFO

Comment 4 Nic Baxter 2015-03-31 02:57:05 CEST
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
CC: (none) => nic
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.