This issue hit me yesterday also.
$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 24.04.2 LTS
Release:24.04
- Attached the journal.txt and prevjournal.txt.
- No crash file found in /var/crash.
- No relevant file found in https://errors.ubuntu.com/user/ID.
The only
Public bug reported:
No sound. Impossible to install the driver for hp 850 G6
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.
Public bug reported:
I'm on Ubuntu 20.04. My Wifi set-up has multiple access points
throughout my home, and they all have the same SSID. It doesn't matter
where I am in my home though, network manager always connects to one
particular AP. If I list all the access points with `nmcli dev wifi
list`
Public bug reported:
I just installed ubuntu, and immediately had problems of very loud and
crackling sound no matter what sound I played.
I tried the three solutions listed here
https://wiki.ubuntu.com/Audio/PositionReporting, the three of them resulted in
no sound at all, and now even if I re
After deleting the .Xauthority file, I can now successfully log into a
Unity session.
The problem seems to be gone (rebooting worked fine after this). Maybe
somebody can figure out how I got into this situation, but otherwise the
bug can be closed as far as I'm concerned.
--
You received this bu
If I *remove* xserver-xorg-video-intel, lightdm is able to show me the
login screen. However, there is corruption on the screen and trying to
log into a Unity or Gnome session just shows a blank screen and then
puts me back into the login screen after 1 second.
--
You received this bug notificati
Public bug reported:
After updating from 16.04 to 16.10, lightdm doesn't start.
Adding 'nomodeset' for booting allows it to start, but apparently lacks
all acceleration.
Trying different kernels doesn't help, including the one from 16.04.
Sorry for brevity, I'm writing this on my phone...
Prob
Linux and I asked for help on a french
forum since this is my native language.
Remi
Le mardi 24 février 2015 7h15, Christopher M. Penalver
a écrit :
Remi, as per http://xorg.freedesktop.org/wiki/RadeonFeature/ there is no
indication your card is not supported. Despite this, this bug
99,9% sure that the problem is a material one, since my graphic card is
not supported by any Linux distribution.I will not do any additionnal test and
I will install a new graphic card soon.
Thanks
Remi
Le lundi 23 février 2015 23h26, Christopher M. Penalver
a écrit :
Remi, this
Public bug reported:
I've been unable to pair my Logitech K810. I figured out that the new
device setup wizard reports the wrong PIN. I used bluez-hcidump before
trying to pair from the setup wizard. The setup wizard PIN differs from
the one reported by bluez-hcidump. The PIN reported by bluez-hci
Swâmi,
We've all laid out these arguments many times over. Yes, this issue is
frustrating (and I regret having vented some of my own frustration in my
first comments) but let's keep it civil.
There are proposed solutions. I, for one, think Andreas' proposal is the
best way out of the current dead
Swâmi,
We've all laid out these arguments many times over. Yes, this issue is
frustrating (and I regret having vented some of my own frustration in my
first comments) but let's keep it civil.
There are proposed solutions. I, for one, think Andreas' proposal is the
best way out of the current dead
I'm at a loss as to what to do to help find a solution for everyone.
fr-oss is a great layout with many useful improvements over fr-latin9,
but the missing ControlR is a deal breaker. I'm personally back to using
the default "fr" layout and I'll advise users to do the same if they
want their Contr
I'm at a loss as to what to do to help find a solution for everyone.
fr-oss is a great layout with many useful improvements over fr-latin9,
but the missing ControlR is a deal breaker. I'm personally back to using
the default "fr" layout and I'll advise users to do the same if they
want their Contr
Nicolas,
Where does the need to *have* a key for nbsp come from? Isn't a compose
combo more appropriate and less error-prone?
Cheers
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/
Nicolas,
Where does the need to *have* a key for nbsp come from? Isn't a compose
combo more appropriate and less error-prone?
Cheers
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/22
Public bug reported:
I regularly lost image on my screen. This happen instantly and I believe this
is a graphic card issue with Ubuntu since it work correctly with Windows.
I get stuck with vertical lines grey/blue screen image and the only solution
is to restart the computer. No more icons, mo
(In reply to comment #60)
> Gentlemen, I am really stuck at that point.
Allow me to sum it up.
- Nicolas is the sole advocate of having Control_R mapped to Level5.
- The rest of us want to go back to having both left and right Control
behaving the same way.
I'm not quite sure how you want us
(In reply to comment #60)
> Gentlemen, I am really stuck at that point.
Allow me to sum it up.
- Nicolas is the sole advocate of having Control_R mapped to Level5.
- The rest of us want to go back to having both left and right Control
behaving the same way.
I'm not quite sure how you want us
For some reason, I found myself using the 'fr oss' layout in Gnome 3.10.
And I must say that finding out that this layout was picked as the
default left me speechless: two keys on my keyboard no longer behave
according to what's *on* the actual key:
- the right control key, which just says "Ctrl"
For some reason, I found myself using the 'fr oss' layout in Gnome 3.10.
And I must say that finding out that this layout was picked as the
default left me speechless: two keys on my keyboard no longer behave
according to what's *on* the actual key:
- the right control key, which just says "Ctrl"
Hi,
I made one more test today.
Went to simple-scan preference window (Menu Document--> Preferences).
"Scan side" option was "Front and back".
I changed it to "Front" only.
Then the "Scan all pages from feeder" indeed now scan all pages, but
after last page, the printer does not stop and shows
Hi again, sorry I was busy those last few days.
Here is the result of your suggest command : "scanimage --all-options"
scanimage --all-options
All options specific to device
`hpaio:/usb/Officejet_6300_series?serial=CN86AFV38X04J5':
Scan mode:
--mode Lineart|Gray|Color [Color]
Sel
Thanks robert.
I tested using your recommendation scanimage.
$ scanimage > test.pbm
--> looks like scanning ok.
However, to test the multipage feeder scanning, I used the following
command :
$ scanimage --batch >test_batch.pbm
Scanning -1 pages, incrementing by 1, numbering from 1
Scanning pag
Note :
I got rid off the autosave.db, preventing first time simple-scan to
launch quickly.
I updated to simple-scan latest version. Simple Scan 3.11.3, released on
2013-12-18.
Still experiencing same issue : impossible to scan multiple pages in a
row via the scan all pages in feeder feature.
lo
2 additional informations :
1st time I launch simple-scan, it takes forever to appear. cf log
obtained by simplescan -d :
$ simple-scan -d
[+0.00s] DEBUG: simple-scan.vala:582: Starting Simple Scan 3.10.0, PID=11029
[+0.00s] DEBUG: Connecting to session manager
[+0.66s] WARNING: g_object_set_val
Public bug reported:
Using on Jan 5th 2013 :
Ubuntu 13.10.
simplescan 3.10.0-0ubuntu1
sane-utils + libsane (1.0.23-0ubuntu3)
libsane-hpaio 3.13.9-1
hplip 3.13.9.1 but was also faulty with 3.10 or 3.11.
architecture amd64
Dell lattitude D630
A simple page scan would work but nothing would
I've got 10.10.10 over here and also since I upgraded to 3.6.23 I got exactly
the same issue. When I tried to shut down, a message box prompted me that
firefox-bin wasn't shut down proparly and I had to kill the process or force a
shut down.
Also when I closed Firefox and I tried to start it aga
problem occurs when you shut down the computer with Firefox still
running. Simple solution is to delete the "lock" and ".parantlock" files
from: //personal folder/.mozilla/firefox/(insert).default and firefox
will run just fine again.
--
You received this bug notification because you are a member
29 matches
Mail list logo