Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Need help with gnome-terminal not starting #2568

Closed
2 of 3 tasks
sailnfool opened this issue Apr 1, 2024 · 19 comments
Closed
2 of 3 tasks

Need help with gnome-terminal not starting #2568

sailnfool opened this issue Apr 1, 2024 · 19 comments
Labels
User Error Issue is due to user error and not a bug with pi-apps

Comments

@sailnfool
Copy link

sailnfool commented Apr 1, 2024 •
edited by Botspot
Loading

Confirmations

What happened?

Wine (x64) shows "Error occured when calling Terminal-run"

Description

Popup window with error message in title bar: "Error occured when calling Terminal-run"

Unable to open a terminal.
Debug output below.
Default x-terminal-emulator: gnome-terminal.wrapper
Using gnome-terminal.wrapper
# Option “-x” is deprecated and might be removed in a later version of gnome-terminal.
# Use “-- ” to terminate the options and put the command line to execute after it.
�[91mterminal-run: No terminal detected as it never created the pid file within 5 seconds.�[39m
# Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached

What are your system specs (run the following command in your terminal)?

OS: Debian GNU/Linux 12 (bookworm)
OS architecture: 64-bit
Last updated Pi-Apps on: 03/31/2024
Latest Pi-Apps version: 04/01/2024
Kernel: aarch64 6.6.20+rpt-rpi-v8
Device model: Raspberry Pi 4 Model B Rev 1.4
SOC identifier: bcm2711
Cpu name: Cortex-A72
Ram size: 7.81 GB
Raspberry Pi OS image version: 2024-03-15
Language: en_US.UTF-8

(Recommended) Error log? Terminal output? Debug messages?

Unable to open a terminal.
Debug output below.
Default x-terminal-emulator: gnome-terminal.wrapper
Using gnome-terminal.wrapper
# Option “-x” is deprecated and might be removed in a later version of gnome-terminal.
# Use “-- ” to terminate the options and put the command line to execute after it.
�[91mterminal-run: No terminal detected as it never created the pid file within 5 seconds.�[39m
# Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached
@sailnfool sailnfool added the bug Something isn't working label Apr 1, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Apr 1, 2024

Hello there 👋
Thanks for submitting your first issue to the Pi-Apps project! We'll try to get back to you as soon as possible.
In the meantime, we encourage you join our Discord server, where you can ask any questions you might have.

Please respond as soon as possible if a Pi-Apps maintainer requests more information from you. Stale issues will be closed after a lengthy period of time with no response.

@Botspot Botspot closed this as completed in 209622c Apr 1, 2024
@Botspot
Copy link
Owner

Botspot commented Apr 1, 2024 •
edited
Loading

While in my tests, gnome-terminal would display that warning about option "-x" being deprecated, it still seemed to work. Maybe your version is newer and no longer functions at all.

In commit 209622c, I have changed the command slightly to avoid the warning. Please try again and let us know if this change fixed your issue.

@Botspot Botspot mentioned this issue Apr 2, 2024
Closed
3 tasks
@sailnfool
Copy link
Author

I uninstalled and re-installed pi-apps today. As reported in #2569, I found the problem appears to be related to gnome-terminal in Raspberry PI OS 64. Pi-apps ran flawlessly after I uninstalled the gnome-terminal with synaptic. Alternatively the etc/terminal-wrap code could test for the 64-bit OS and use lxterminal instead of gnome-terminal

@sailnfool
Copy link
Author

Sorry, I meant terminal-run not terminal-wrap

@Botspot Botspot reopened this Apr 2, 2024
@Botspot
Copy link
Owner

Botspot commented Apr 2, 2024 •
edited
Loading

It works from my end.

Please install gnome-terminal, then run this in a terminal: bash -x ~/pi-apps/etc/terminal-run 'sudo apt update'
Let me know if gnome-terminal successfully launches and runs this command, or if it fails as at other times.
And send all output from the command here.

@sailnfool
Copy link
Author

sailnfool commented Apr 2, 2024 via email •
edited by Botspot
Loading

@Botspot
Copy link
Owner

Botspot commented Apr 2, 2024

How can you be certain that this issue is caused by gnome-terminal when from your command output, it looked like terminal-run chose to go with lxterminal?

@Botspot
Copy link
Owner

Botspot commented Apr 2, 2024

The "sudo apt update" window closed with no messages and no updates made.

Please clarify. Did it open and then immediately close thereafter?

@Botspot
Copy link
Owner

Botspot commented Apr 2, 2024 •
edited
Loading

I have made a couple of changes to the terminal-run script that handle some error cases with the /tmp folder permissions. It is possible that is the problem here.

No need to reinstall pi-apps. To get the latest updates with a non-working terminal-run script, use this command: ~/pi-apps/updater cli-yes
Once you update, I would be interested to know what the new behavior of the terminal-run script is. It's possible that it will now output a more descriptive error.

@sailnfool
Copy link
Author

sailnfool commented Apr 2, 2024 via email

@theofficialgman
Copy link
Collaborator 

# Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached

@sailnfool this error is outside of pi-apps control. gnome-terminal seems unable to start.
try running with gnome-terminal in another terminal and see if it is able to start. I expect it not to be able to.

it is worth running tail -f /var/log/syslog in another terminal before attempting to start gnome-terminal as well to see if there are any additional logs about your broken system

@sailnfool
Copy link
Author

sailnfool commented Apr 2, 2024 via email •
edited
Loading

@theofficialgman
Copy link
Collaborator

I can't tell what you are intended to test there at all
Please use github to formulate further responses with code blocks
Follow this #2568 (comment) . All I asked was that you run gnome-terminal and tell me if it launches. If it doesn't, then it is something on your system that is broken. You can debug the issue by running tail -f /var/log/syslog in another terminal before attempting to start gnome-terminal to get additional logs

@theofficialgman theofficialgman changed the title Attempt to install Wine(x64), failed with Error Occured when calling Terminal-run Need help with gnome-terminal not starting Apr 2, 2024
@theofficialgman theofficialgman added User Error Issue is due to user error and not a bug with pi-apps and removed bug Something isn't working labels Apr 2, 2024
@Botspot
Copy link
Owner

Botspot commented Apr 3, 2024 •
edited
Loading

If I uninstall gnome-terminal, everything works fine.

But in one of your earlier comments, it seemed that terminal-run chose to use lxterminal, and it still failed. Any ideas for why that happened? I thought you were saying that only gnome-terminal was affected by your non-standard locale setting.

@theofficialgman
Copy link
Collaborator

@sailnfool in the future please don't fully change the contents of a post like that with an edit. it makes the conversation impossible to read without viewing the previous edits in context

@theofficialgman
Copy link
Collaborator

But in one of your earlier comments, it seemed that terminal-run chose to use lxterminal, and it still failed. Any ideas for why that happened? I thought you were saying that only gnome-terminal was affected by your non-standard locale setting.

I think its likely that lxterminal also requires UTF-8 locale, causing the same failure. I hope that this bug hasn't been re-introduced in the latest piOS image raspberrypi/bookworm-feedback#123

@theofficialgman
Copy link
Collaborator

Can this issue but closed? I don't think there is anything we can do about users default terminal being non-functional due to poor user locale choices.

@Botspot Botspot closed this as completed Apr 6, 2024
@sailnfool
Copy link
Author

sailnfool commented Apr 6, 2024 via email

@Botspot
Copy link
Owner

Botspot commented Apr 6, 2024

lxterminal did work correctly even with the incorrect locale setting. Now
that I have fixed the locale and reinstalled gnome-terminal. Everything
works just fine. Sorry for the wild-goose chase, but it is good to know
that if anyone else encounters a similar issue, that you can look at their
locale issues and that there are no inherent issues in pi-apps.

Well it sure looks like lxterminal was the chosen terminal from your post here: #2568 (comment)
It works now, which is what matters. Just wanted to clarify what I said earlier. Maybe lxterminal was still the chosen default, even when gnome-terminal was installed. ¯_(ツ)_/¯

On a separate note, I had used cloudbuddy as a way to access my dropbox. I
was running some large scripts to move files around in dropbox to eliminate
many of the duplications that were found by fdupes. The only reason that I
mention this is that in the meantime I had gotten my NFS mount of Dropbox
on an x86 machine running. The scripts that were moving the files around
ran significantly FASTER on the NFS mount than on the cloudbuddy. This is
NOT a critique. I am very impressed with Cloudbuddy. It is significantly
less user work to install a Dropbox with cloudbuddy than in setting up the
NFS mounting. I just noted that due to the implementation (probably due to
the Dropbox APIs) that moving files around was significantly slower. That
said, I was VERY impressed that being able to mount Dropbox without
consuming local storage on the Raspberry PI was terrific for casual use and
a simple installation step.

CloudBuddy uses the rclone project. I think that for many cloud providers, if you set up an API key and configure rclone to use it, then speeds will be higher. At least for Gdrive, rclone uses a rate-limited api key from Google, and that rate limit is applied to all rclone users who share the api key. You are on your own or that.
An easier way to get higher speeds: use rclone's built-in copy commands instead of mounting the drive. With my CloudBuddy tool, this can be done with the "browse drive" button. In that mode, there is an option to download groups of files or upload files. This is much faster, and less failure-prone.

Apologies for the long note.

No worries. I hope my response here is helpful.

I REALLY appreciate your work with PI-Apps.

Yeah, definitely credits to those involved. I can say that if it were just me working on the project without help from devs like @theofficialgman and the support from people like you, I would have lost interest years ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
User Error Issue is due to user error and not a bug with pi-apps
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sailnfool @theofficialgman @Botspot