Debian 9: synaptic package manager won't launch from command line
Clash Royale CLAN TAG#URR8PPP
Every time I enter this line:
sudo pkexec synaptic
The synaptic package manager opens, but always followed by this error message:
E: Could not open file - open (2: No such file or directory)
E: _cache->open() failed, please report.
If I close the error box, synaptic will simultaneously close with it. How do I fix this bug and finally launch synaptic?
@Henrik, I just ran
sudo apt update
This is the complete response that was generated in terminal:
Ign:1 http://ftp.us.debian.org/debian stretch InRelease
Get:2 http://deb.debian.org/debian stretch-backports InRelease [91.8 kB]
Hit:3 http://ftp.us.debian.org/debian stretch Release
Get:5 http://deb.debian.org/debian stretch-backports/main amd64
Packages.diff/Index [27.8 kB]
Get:6 http://deb.debian.org/debian stretch-backports/main amd64 Packages
2018-12-24-0808.38.pdiff [622 B]
Get:6 http://deb.debian.org/debian stretch-backports/main amd64 Packages
2018-12-24-0808.38.pdiff [622 B]
Fetched 120 kB in 1s (75.7 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: http://ftp.us.debian.org/debian/dists/stretch/Release.gpg: The key(s)
in the keyring /etc/apt/trusted.gpg are ignored as the file is not
readable by user '_apt' executing apt-key.
W: http://deb.debian.org/debian/dists/stretch-backports/InRelease: The
key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not
readable by user '_apt' executing apt-key.
debian command-line synaptic
|
show 3 more comments
Every time I enter this line:
sudo pkexec synaptic
The synaptic package manager opens, but always followed by this error message:
E: Could not open file - open (2: No such file or directory)
E: _cache->open() failed, please report.
If I close the error box, synaptic will simultaneously close with it. How do I fix this bug and finally launch synaptic?
@Henrik, I just ran
sudo apt update
This is the complete response that was generated in terminal:
Ign:1 http://ftp.us.debian.org/debian stretch InRelease
Get:2 http://deb.debian.org/debian stretch-backports InRelease [91.8 kB]
Hit:3 http://ftp.us.debian.org/debian stretch Release
Get:5 http://deb.debian.org/debian stretch-backports/main amd64
Packages.diff/Index [27.8 kB]
Get:6 http://deb.debian.org/debian stretch-backports/main amd64 Packages
2018-12-24-0808.38.pdiff [622 B]
Get:6 http://deb.debian.org/debian stretch-backports/main amd64 Packages
2018-12-24-0808.38.pdiff [622 B]
Fetched 120 kB in 1s (75.7 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: http://ftp.us.debian.org/debian/dists/stretch/Release.gpg: The key(s)
in the keyring /etc/apt/trusted.gpg are ignored as the file is not
readable by user '_apt' executing apt-key.
W: http://deb.debian.org/debian/dists/stretch-backports/InRelease: The
key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not
readable by user '_apt' executing apt-key.
debian command-line synaptic
Maybe I should re-install debian? There doesn't seem to be anyway around this.
– piece0fshite
Dec 24 '18 at 8:11
1
I had never heard ofpkexec
before, but a quick look at the man page suggets to me that it's rather redundant in your command. I've never cared for synaptic, so I don't know if the problem might be synaptic-specific or if your package database has been destroyed. My suggestion is that you try to runsudo apt update
and show us the complete input+output, maybe that will tell us something that allows us to help you. Whether there's a way around it depends a lot on what has happened.
– Henrik
Dec 24 '18 at 9:47
Google has lots of suggestions for this error. Which one(s) have you already tried?
– roaima
Dec 24 '18 at 10:18
@Henrik See my recent edit above for response, as it was too long for comment section.
– piece0fshite
Dec 24 '18 at 16:10
@roaima There are fixes for it in the different versions of ubuntu and mint, but there's nothing for it in debian 9. The closest I could find was for debian squeeze/wheezy (bugs.debian.org/cgi-bin/bugreport.cgi?bug=708294), but the info is outdated because there appears to be no synaptic.conf file in root.
– piece0fshite
Dec 24 '18 at 16:21
|
show 3 more comments
Every time I enter this line:
sudo pkexec synaptic
The synaptic package manager opens, but always followed by this error message:
E: Could not open file - open (2: No such file or directory)
E: _cache->open() failed, please report.
If I close the error box, synaptic will simultaneously close with it. How do I fix this bug and finally launch synaptic?
@Henrik, I just ran
sudo apt update
This is the complete response that was generated in terminal:
Ign:1 http://ftp.us.debian.org/debian stretch InRelease
Get:2 http://deb.debian.org/debian stretch-backports InRelease [91.8 kB]
Hit:3 http://ftp.us.debian.org/debian stretch Release
Get:5 http://deb.debian.org/debian stretch-backports/main amd64
Packages.diff/Index [27.8 kB]
Get:6 http://deb.debian.org/debian stretch-backports/main amd64 Packages
2018-12-24-0808.38.pdiff [622 B]
Get:6 http://deb.debian.org/debian stretch-backports/main amd64 Packages
2018-12-24-0808.38.pdiff [622 B]
Fetched 120 kB in 1s (75.7 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: http://ftp.us.debian.org/debian/dists/stretch/Release.gpg: The key(s)
in the keyring /etc/apt/trusted.gpg are ignored as the file is not
readable by user '_apt' executing apt-key.
W: http://deb.debian.org/debian/dists/stretch-backports/InRelease: The
key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not
readable by user '_apt' executing apt-key.
debian command-line synaptic
Every time I enter this line:
sudo pkexec synaptic
The synaptic package manager opens, but always followed by this error message:
E: Could not open file - open (2: No such file or directory)
E: _cache->open() failed, please report.
If I close the error box, synaptic will simultaneously close with it. How do I fix this bug and finally launch synaptic?
@Henrik, I just ran
sudo apt update
This is the complete response that was generated in terminal:
Ign:1 http://ftp.us.debian.org/debian stretch InRelease
Get:2 http://deb.debian.org/debian stretch-backports InRelease [91.8 kB]
Hit:3 http://ftp.us.debian.org/debian stretch Release
Get:5 http://deb.debian.org/debian stretch-backports/main amd64
Packages.diff/Index [27.8 kB]
Get:6 http://deb.debian.org/debian stretch-backports/main amd64 Packages
2018-12-24-0808.38.pdiff [622 B]
Get:6 http://deb.debian.org/debian stretch-backports/main amd64 Packages
2018-12-24-0808.38.pdiff [622 B]
Fetched 120 kB in 1s (75.7 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: http://ftp.us.debian.org/debian/dists/stretch/Release.gpg: The key(s)
in the keyring /etc/apt/trusted.gpg are ignored as the file is not
readable by user '_apt' executing apt-key.
W: http://deb.debian.org/debian/dists/stretch-backports/InRelease: The
key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not
readable by user '_apt' executing apt-key.
debian command-line synaptic
debian command-line synaptic
edited Dec 24 '18 at 16:09
asked Dec 24 '18 at 7:12
piece0fshite
62
62
Maybe I should re-install debian? There doesn't seem to be anyway around this.
– piece0fshite
Dec 24 '18 at 8:11
1
I had never heard ofpkexec
before, but a quick look at the man page suggets to me that it's rather redundant in your command. I've never cared for synaptic, so I don't know if the problem might be synaptic-specific or if your package database has been destroyed. My suggestion is that you try to runsudo apt update
and show us the complete input+output, maybe that will tell us something that allows us to help you. Whether there's a way around it depends a lot on what has happened.
– Henrik
Dec 24 '18 at 9:47
Google has lots of suggestions for this error. Which one(s) have you already tried?
– roaima
Dec 24 '18 at 10:18
@Henrik See my recent edit above for response, as it was too long for comment section.
– piece0fshite
Dec 24 '18 at 16:10
@roaima There are fixes for it in the different versions of ubuntu and mint, but there's nothing for it in debian 9. The closest I could find was for debian squeeze/wheezy (bugs.debian.org/cgi-bin/bugreport.cgi?bug=708294), but the info is outdated because there appears to be no synaptic.conf file in root.
– piece0fshite
Dec 24 '18 at 16:21
|
show 3 more comments
Maybe I should re-install debian? There doesn't seem to be anyway around this.
– piece0fshite
Dec 24 '18 at 8:11
1
I had never heard ofpkexec
before, but a quick look at the man page suggets to me that it's rather redundant in your command. I've never cared for synaptic, so I don't know if the problem might be synaptic-specific or if your package database has been destroyed. My suggestion is that you try to runsudo apt update
and show us the complete input+output, maybe that will tell us something that allows us to help you. Whether there's a way around it depends a lot on what has happened.
– Henrik
Dec 24 '18 at 9:47
Google has lots of suggestions for this error. Which one(s) have you already tried?
– roaima
Dec 24 '18 at 10:18
@Henrik See my recent edit above for response, as it was too long for comment section.
– piece0fshite
Dec 24 '18 at 16:10
@roaima There are fixes for it in the different versions of ubuntu and mint, but there's nothing for it in debian 9. The closest I could find was for debian squeeze/wheezy (bugs.debian.org/cgi-bin/bugreport.cgi?bug=708294), but the info is outdated because there appears to be no synaptic.conf file in root.
– piece0fshite
Dec 24 '18 at 16:21
Maybe I should re-install debian? There doesn't seem to be anyway around this.
– piece0fshite
Dec 24 '18 at 8:11
Maybe I should re-install debian? There doesn't seem to be anyway around this.
– piece0fshite
Dec 24 '18 at 8:11
1
1
I had never heard of
pkexec
before, but a quick look at the man page suggets to me that it's rather redundant in your command. I've never cared for synaptic, so I don't know if the problem might be synaptic-specific or if your package database has been destroyed. My suggestion is that you try to run sudo apt update
and show us the complete input+output, maybe that will tell us something that allows us to help you. Whether there's a way around it depends a lot on what has happened.– Henrik
Dec 24 '18 at 9:47
I had never heard of
pkexec
before, but a quick look at the man page suggets to me that it's rather redundant in your command. I've never cared for synaptic, so I don't know if the problem might be synaptic-specific or if your package database has been destroyed. My suggestion is that you try to run sudo apt update
and show us the complete input+output, maybe that will tell us something that allows us to help you. Whether there's a way around it depends a lot on what has happened.– Henrik
Dec 24 '18 at 9:47
Google has lots of suggestions for this error. Which one(s) have you already tried?
– roaima
Dec 24 '18 at 10:18
Google has lots of suggestions for this error. Which one(s) have you already tried?
– roaima
Dec 24 '18 at 10:18
@Henrik See my recent edit above for response, as it was too long for comment section.
– piece0fshite
Dec 24 '18 at 16:10
@Henrik See my recent edit above for response, as it was too long for comment section.
– piece0fshite
Dec 24 '18 at 16:10
@roaima There are fixes for it in the different versions of ubuntu and mint, but there's nothing for it in debian 9. The closest I could find was for debian squeeze/wheezy (bugs.debian.org/cgi-bin/bugreport.cgi?bug=708294), but the info is outdated because there appears to be no synaptic.conf file in root.
– piece0fshite
Dec 24 '18 at 16:21
@roaima There are fixes for it in the different versions of ubuntu and mint, but there's nothing for it in debian 9. The closest I could find was for debian squeeze/wheezy (bugs.debian.org/cgi-bin/bugreport.cgi?bug=708294), but the info is outdated because there appears to be no synaptic.conf file in root.
– piece0fshite
Dec 24 '18 at 16:21
|
show 3 more comments
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490729%2fdebian-9-synaptic-package-manager-wont-launch-from-command-line%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490729%2fdebian-9-synaptic-package-manager-wont-launch-from-command-line%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Maybe I should re-install debian? There doesn't seem to be anyway around this.
– piece0fshite
Dec 24 '18 at 8:11
1
I had never heard of
pkexec
before, but a quick look at the man page suggets to me that it's rather redundant in your command. I've never cared for synaptic, so I don't know if the problem might be synaptic-specific or if your package database has been destroyed. My suggestion is that you try to runsudo apt update
and show us the complete input+output, maybe that will tell us something that allows us to help you. Whether there's a way around it depends a lot on what has happened.– Henrik
Dec 24 '18 at 9:47
Google has lots of suggestions for this error. Which one(s) have you already tried?
– roaima
Dec 24 '18 at 10:18
@Henrik See my recent edit above for response, as it was too long for comment section.
– piece0fshite
Dec 24 '18 at 16:10
@roaima There are fixes for it in the different versions of ubuntu and mint, but there's nothing for it in debian 9. The closest I could find was for debian squeeze/wheezy (bugs.debian.org/cgi-bin/bugreport.cgi?bug=708294), but the info is outdated because there appears to be no synaptic.conf file in root.
– piece0fshite
Dec 24 '18 at 16:21