1
Printing and Scanning / Re: Can't get Canon PIXMA G5050 to install
« on: Today at 11:50:46 AM »Quote
I've followed the manualWhat exactly happens when you plug your printer into the USB on the PC and power it up ?
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
Installing Software / Re: Installing an antivirus system and the weather app available on Linux Lite 6.6
« on: September 28, 2023, 05:21:12 AM »
If you installed the weather tool from Lite Software, you may need to add it to your panel.
Right click somewhere free on the bar at the bottom of the screen.
Click 'Panel'
Clcik 'Add New Item'
Scroll down the list to find 'Weather Update'
Highlight 'Weather Update'
Click Add
This should place the icon on bottom right near the date/time on a conventional set up.
Right click somewhere free on the bar at the bottom of the screen.
Click 'Panel'
Clcik 'Add New Item'
Scroll down the list to find 'Weather Update'
Highlight 'Weather Update'
Click Add
This should place the icon on bottom right near the date/time on a conventional set up.
3
Updates / Re: Esc key to wake from Suspend.
« on: September 28, 2023, 12:50:45 AM »
Those settings change the system behaviour (auto mount, open with Thunar and Desktop icons) when a USB storage device is inserted on my system, but there may be other settings somewhere which is causing your issue. As I can't reproduce your problem and you don't know which update triggered the problem I can only suggest a few things.
If your settings are correct to generate the desktop icon then there may be a problem with the mechanism. You may want to check the log on your system when inserting a device.
With the settings correct, boot up your system to a idle state. Close any applications.
Note the system time in terms of HH:MM:SS
Insert the USB device and allow time (say 15 seconds) for the system to react.
Open a terminal (press Ctrl, Alt, T together)
Enter the command followed by return/enter - replacing HH:MM:SS with the time you noted.
You would expect to see a number of events indicating.
a) The physical device being detected
b) The storage being mounted.
What happens or doesn't happen next may provide some clue. In particular, look for gvfs and dbus activity after the device is mounted.
Instructions for posting images should have been in your sign up mails and are also in the posting guidelines
https://www.linuxliteos.com/forums/introductions/forum-posting-guidelines/
If your settings are correct to generate the desktop icon then there may be a problem with the mechanism. You may want to check the log on your system when inserting a device.
With the settings correct, boot up your system to a idle state. Close any applications.
Note the system time in terms of HH:MM:SS
Insert the USB device and allow time (say 15 seconds) for the system to react.
Open a terminal (press Ctrl, Alt, T together)
Enter the command followed by return/enter - replacing HH:MM:SS with the time you noted.
Code: [Select]
journalctl -b --since HH:MM:SSYou would expect to see a number of events indicating.
a) The physical device being detected
b) The storage being mounted.
What happens or doesn't happen next may provide some clue. In particular, look for gvfs and dbus activity after the device is mounted.
Instructions for posting images should have been in your sign up mails and are also in the posting guidelines
https://www.linuxliteos.com/forums/introductions/forum-posting-guidelines/
4
Updates / Re: Esc key to wake from Suspend.
« on: September 27, 2023, 05:32:52 AM »
Do you know which update triggered the changes ?
I don't use any form of suspend or hibernate so can't really comment on that.
For me, when inserting USB drive the system reflects the setup chosen in the options.
It auto mounts, presents an icon for the drive on the desktop and opens the file manager.
This behaviour has been consistent - regardless of updates.
Check your settings by
Click Menu
Begin typing 'Removable' in the search box
When you see 'Removable Drives and Media' click it
If necessary, change the ticks to your requirement.
The desktop icon appearing may need setting under this
Right click on desktop
Click Desktop Settings
Select the 'Icons' tab
Ensure tick against 'Removable Devices'
I don't use any form of suspend or hibernate so can't really comment on that.
For me, when inserting USB drive the system reflects the setup chosen in the options.
It auto mounts, presents an icon for the drive on the desktop and opens the file manager.
This behaviour has been consistent - regardless of updates.
Check your settings by
Click Menu
Begin typing 'Removable' in the search box
When you see 'Removable Drives and Media' click it
If necessary, change the ticks to your requirement.
The desktop icon appearing may need setting under this
Right click on desktop
Click Desktop Settings
Select the 'Icons' tab
Ensure tick against 'Removable Devices'
5
Start up and Shutdown / Re: Wrong keyboard on logscreen
« on: September 25, 2023, 05:46:01 AM »
Do you know which update/upgrade triggered the problem ?
Do you use the System restore Utility (aka timeshift) ?
You could try rolling back the system state to see if it helps.
There was a new kernel on or around 29th August.
If you keep old kernels on disk try booting off one before the problem started.
Do you use the System restore Utility (aka timeshift) ?
You could try rolling back the system state to see if it helps.
There was a new kernel on or around 29th August.
If you keep old kernels on disk try booting off one before the problem started.
6
Updates / Re: error log while installing updates - vscodium repository
« on: September 25, 2023, 03:39:19 AM »
Looks like there is a problem with the gitlab paulcarroty vscodium repository at the moment.
It could be a temporary issue at gitlab which they can resolve.
Your system update/upgrade won't run properly unless gitlab resolve the issue or the repository is removed from the system.
For an urgent update/upgrade it may be possible to suspend the gitlab repository from your list.
What instructions did you follow to install vscodium ?
It could be a temporary issue at gitlab which they can resolve.
Your system update/upgrade won't run properly unless gitlab resolve the issue or the repository is removed from the system.
For an urgent update/upgrade it may be possible to suspend the gitlab repository from your list.
What instructions did you follow to install vscodium ?
7
Updates / Re: cant able to update, recieved the error message - CDROM
« on: September 24, 2023, 06:10:54 AM »
The error message posted looks like an attempt to run updates on a system booted from a 'Live image' media.
A Live image is typically a USB drive or a DVD created by burning an ISO file using something like etcher or rufus and is for limited use, such as testing the hardware or using as a base for a full installation to disk.
A system running a Live image is not intended to be updated and will report this error.
If the OS has been fully installed to an internal disk and rebooted then the update should work.
If it is intended to run the OS from USB (rather than installing to a disk) extra steps are required to create a 'persistent' image when preparing the USB drive.
A Live image is typically a USB drive or a DVD created by burning an ISO file using something like etcher or rufus and is for limited use, such as testing the hardware or using as a base for a full installation to disk.
A system running a Live image is not intended to be updated and will report this error.
If the OS has been fully installed to an internal disk and rebooted then the update should work.
If it is intended to run the OS from USB (rather than installing to a disk) extra steps are required to create a 'persistent' image when preparing the USB drive.
8
Installing Linux Lite / Re: LL6.2 installed. During update install, process ended with error msg (attached)
« on: September 23, 2023, 01:40:38 AM »Can i ask a question?Yes. but if it is on a different subject to this thread, it would be best to open a new thread.
9
Updates / Re: Computer will not update - PPA
« on: September 18, 2023, 10:56:59 AM »
Have you removed the stacer software and related ppa repository as advised in post 4 ?
10
Updates / Re: Computer will not update - PPA
« on: September 18, 2023, 01:06:42 AM »
Please post your error logs if you are having problems with updates. You can re-run the update and upgrade commands and make them record the results to text files. If you post the text files back here it might show what is happening.
To do this, open a terminal by pressing 'Ctrl' 'Alt' and 'T' keys together.
In the terminal window, type or paste in these commands followed by return/enter each time. Answer any prompts and enter your password if asked.
Running those commands should create two files called apt-get-update.txt and apt-get-upgrade.txt in your home directory. The filenames will be prefixed with date and time information. You can open them to review what they contain.
Post back attaching the two files.
To do this, open a terminal by pressing 'Ctrl' 'Alt' and 'T' keys together.
In the terminal window, type or paste in these commands followed by return/enter each time. Answer any prompts and enter your password if asked.
Code: [Select]
sudo apt-get update | tee ~/"$(date +"%Y_%m_%d_%T")-apt-get-update.txt"Code: [Select]
sudo apt-get upgrade | tee ~/"$(date +"%Y_%m_%d_%T")-apt-get-upgrade.txt"Running those commands should create two files called apt-get-update.txt and apt-get-upgrade.txt in your home directory. The filenames will be prefixed with date and time information. You can open them to review what they contain.
Post back attaching the two files.
11
Updates / Re: Computer will not update - PPA
« on: September 15, 2023, 02:41:26 PM »
It would have been odd if the command line worked ok.
The version of Linux Lite being used is focal based. The stacer PPA software does not have a release compatible with focal. This conflict is causing the update process to error. The incompatible stacer software should be removed from the system.
After removing the stacer application, ensure that the stacer PPA reference is removed from the update list.
Removing the PPA reference from the update list should allow the update to run.
See
https://www.linuxliteos.com/manual/software.html#pparem
If using PPA software, it is important that the PPA has a release that is compatible with the OS in use.
See this link for advice on selecting and installing PPAs
https://www.linuxliteos.com/manual/software.html#ppa
The version of Linux Lite being used is focal based. The stacer PPA software does not have a release compatible with focal. This conflict is causing the update process to error. The incompatible stacer software should be removed from the system.
After removing the stacer application, ensure that the stacer PPA reference is removed from the update list.
Removing the PPA reference from the update list should allow the update to run.
See
https://www.linuxliteos.com/manual/software.html#pparem
If using PPA software, it is important that the PPA has a release that is compatible with the OS in use.
See this link for advice on selecting and installing PPAs
https://www.linuxliteos.com/manual/software.html#ppa
12
Updates / Re: Computer will not update - PPA
« on: September 15, 2023, 12:41:07 AM »Quote
I can update / upgrade from the command line.
Do you mean you can successfully update from the command line ?
If yes, that would be odd. In order to work out what is going on, please can you run the commands you are using and post them and the resulting output back here?
13
Updates / Re: linuxlite1-Nitro-AN515-52nitro update failed 6.6 - Could not get Lock
« on: September 14, 2023, 01:00:53 AM »
Any update process requires exclusive access to the update resources and will 'lock' them until finished to prevent other update process being started.
In this case 'apt' has locked the update resources and is preventing another update process starting.
Manual updates, background update checks, package managers are examples which need to lock the resource.
Background checks may be running at any time but commonly run just after boot.
Before running a manual update, any package managers need to be closed to avoid a clash.
Depending on the speed of the connection and the size of the updates, the resource may be locked for significant time.
This condition should self clear once the process completes so sometimes all that is needed is to wait.
If the problem does not self-resolve it is possible that something (like an interrupted update) may have broken the mechanism and more investigation will be required to clear the lock.
In this case 'apt' has locked the update resources and is preventing another update process starting.
Manual updates, background update checks, package managers are examples which need to lock the resource.
Background checks may be running at any time but commonly run just after boot.
Before running a manual update, any package managers need to be closed to avoid a clash.
Depending on the speed of the connection and the size of the updates, the resource may be locked for significant time.
This condition should self clear once the process completes so sometimes all that is needed is to wait.
If the problem does not self-resolve it is possible that something (like an interrupted update) may have broken the mechanism and more investigation will be required to clear the lock.
14
Installing Software / Re: Trouble getting VLC installed properly and working
« on: September 13, 2023, 12:27:20 AM »
Those commands are not allowed to run at user level. Prefix them with
Code: [Select]
sudo and enter your password if asked.
15
Updates / Re: Update Issue - PPA
« on: September 12, 2023, 07:15:53 AM »
The version of Linux Lite being used is jammy based. The stebbins handbrake PPA software does not have a release compatible with jammy. This conflict is causing the update process to error.
The incompatible stebbins software should be removed from the system.
After removing the software itself, ensure that the stebbins PPA reference is removed from the update list.
Removing the PPA reference from the update list should allow the update to run.
See
https://www.linuxliteos.com/manual/software.html#pparem
If using PPA software, it is important that the PPA has a release that is compatible with the OS in use.
See this link for advice on selecting and installing PPAs
https://www.linuxliteos.com/manual/software.html#ppa
The incompatible stebbins software should be removed from the system.
After removing the software itself, ensure that the stebbins PPA reference is removed from the update list.
Removing the PPA reference from the update list should allow the update to run.
See
https://www.linuxliteos.com/manual/software.html#pparem
If using PPA software, it is important that the PPA has a release that is compatible with the OS in use.
See this link for advice on selecting and installing PPAs
https://www.linuxliteos.com/manual/software.html#ppa