Questions related to: googledrivegui2

Asked by Michal Dziczkowski

Hello. I have an questions. Anyone know who manages the googledrivegui2 package? I can't find a propper launchpad page for it and I wanted to report a bug related to it

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Michal Dziczkowski
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Just run:

ubuntu-bug googledrivegui2

And the process will start

Revision history for this message
Manfred Hampl (m-hampl) said :
#2

I do not find any information about a package named googledrivegui2 in Ubuntu.

What output do you receive for the commands

uname -a
lsb_release -crid
apt-cache policy googledrivegui2

Revision history for this message
Michal Dziczkowski (mdziczkowski) said :
#3

> uname -a

Linux live 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

> lsb_release -crid

Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal

> apt-cache policy googledrivegui2

googledrivegui2:
  Installed: 2.1.1
  Candidate: 2.1.1
  Version table:
 *** 2.1.1 500
        500 https://debiandog.github.io/FossaDog/Packages-amd64 ./ Packages
        100 /var/lib/dpkg/status
     2.1.0 500
        500 https://debiandog.github.io/FossaDog/Packages-amd64 ./ Packages

I think I know that probably I should ask at GitHub about it

Revision history for this message
Michal Dziczkowski (mdziczkowski) said :
#4

@actionparsnip:

ubuntu-bug: command not found

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#5

Sounds like you need to contact the repository owner to report the issue.

Revision history for this message
Manfred Hampl (m-hampl) said :
#6

"ubuntu-bug: command not found"

It seems that you do not have the package apport installed.
In any case, due to the fact that googledrivegui2 is coming from a foreign source, that command would not have worked here, anyhow.

Revision history for this message
Michal Dziczkowski (mdziczkowski) said :
#7

Thanks. I asked here because it hasn't displayed much info about the package description, etc. so it was the first thing I got on thought.