Same issue here as well.
The recommendation from here to grab the 21.10 package fixes it on my end:
https://askubuntu.com/questions/1345669/how-to-install-maxima-cas-on-ubuntu-21-04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
that is all well and good but if a user does not choose to do manual
partitioning the installer puts grub on sda with no input from the user.
I chose to install ubuntu using the second option in the installer which
is to erase the disk and reinstall.
--
You received this bug notification because
Public bug reported:
Ubuntu 11.04 Installer
Expected Behavior: During or prior to the grub installation I expected to be
asked where to install grub
Actual Behavior: grub installs to sda with no input from the user
The only reason this was a problem for me was because I was dual booting
*** This bug is a duplicate of bug 761134 ***
https://bugs.launchpad.net/bugs/761134
Same issue here the work around provided by Faceman works for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It doesn't appear to have been completely fixed but the volume is no
longer at a maximum when I reboot now it is however still louder than
what it should be.
--
Volume at login set to Maximum
https://bugs.launchpad.net/bugs/598308
You received this bug notification because you are a member of
Based on how the volume reacts when I adjust it via the tray icon and
the values that show up in alsamixer it seems there is some kind of
disconnect between pulse and alsa. Based on the page you linked pulse
goes through and adjusts the alsa channel levels at startup, shouldn't
these adjustments
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/598302/+attachment/1540210/+files/CurrentDmesg.txt
--
Netbook display brightness powersaving adjustment loop(on battery)
https://bugs.launchpad.net/bugs/598302
You received this bug notification
apport information
** Tags added: apport-collected
** Description changed:
Release: Ubuntu Netbook Remix 10.04 (last update 6/23/10)
Expected to Happen: Display goes to 0%/off when idle then returns to original
brightness level before going idle on action
What Happened Instead: Display
apport information
** Attachment added: Dependencies.txt
https://bugs.edge.launchpad.net/bugs/598302/+attachment/1540212/+files/Dependencies.txt
--
Netbook display brightness powersaving adjustment loop(on battery)
https://bugs.launchpad.net/bugs/598302
You received this bug notification
apport information
** Attachment added: DevkitPower.txt
https://bugs.edge.launchpad.net/bugs/598302/+attachment/1540214/+files/DevkitPower.txt
--
Netbook display brightness powersaving adjustment loop(on battery)
https://bugs.launchpad.net/bugs/598302
You received this bug notification
apport information
** Attachment added: GConfNonDefault.txt
https://bugs.edge.launchpad.net/bugs/598302/+attachment/1540215/+files/GConfNonDefault.txt
--
Netbook display brightness powersaving adjustment loop(on battery)
https://bugs.launchpad.net/bugs/598302
You received this bug
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/598302/+attachment/1540216/+files/Lspci.txt
--
Netbook display brightness powersaving adjustment loop(on battery)
https://bugs.launchpad.net/bugs/598302
You received this bug notification because you are
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/598302/+attachment/1540217/+files/Lsusb.txt
--
Netbook display brightness powersaving adjustment loop(on battery)
https://bugs.launchpad.net/bugs/598302
You received this bug notification because you are
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/598302/+attachment/1540218/+files/ProcCpuinfo.txt
--
Netbook display brightness powersaving adjustment loop(on battery)
https://bugs.launchpad.net/bugs/598302
You received this bug notification
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/598302/+attachment/1540219/+files/ProcInterrupts.txt
--
Netbook display brightness powersaving adjustment loop(on battery)
https://bugs.launchpad.net/bugs/598302
You received this bug
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/598302/+attachment/1540220/+files/ProcModules.txt
--
Netbook display brightness powersaving adjustment loop(on battery)
https://bugs.launchpad.net/bugs/598302
You received this bug notification
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/598302/+attachment/1540221/+files/UdevDb.txt
--
Netbook display brightness powersaving adjustment loop(on battery)
https://bugs.launchpad.net/bugs/598302
You received this bug notification because you
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/598302/+attachment/1540222/+files/UdevLog.txt
--
Netbook display brightness powersaving adjustment loop(on battery)
https://bugs.launchpad.net/bugs/598302
You received this bug notification because you
apport information
** Attachment added: gnome-power-bugreport.txt
https://bugs.edge.launchpad.net/bugs/598302/+attachment/1540223/+files/gnome-power-bugreport.txt
--
Netbook display brightness powersaving adjustment loop(on battery)
https://bugs.launchpad.net/bugs/598302
You received this
It seems a recent update to pulseaudio has fixed my issue. Updated my
system yesterday, june 12, which also came with a kernel update which
prompted a reboot per usual and volume levels seem to be normal now
after reboot and after a shutdown and restart.
--
Volume at login set to Maximum
Forgive me if I misspeak as I am still very new to using linux but it
seems that this may be a problem with pulseaudio and its interaction
with alsa on startup. When I run alsa-mixer in terminal at startup the
volume levels indicated match that of those displayed on the slider in
the panel applet.
** Description changed:
Release: Ubuntu 10.04 64-bit Desktop Edition
What You Expected to Happen: System volume to remain as set before reboot and
as shown in volume panel applet
What Happened Instead: After reboot/shutdown at and after login system volume
is set to maximum
Public bug reported:
Release: Ubuntu Netbook Remix 10.04 (last update 6/23/10)
Expected to Happen: Display goes to 0%/off when idle then returns to original
brightness level before going idle on action
What Happened Instead: Display brightness at active cycles until eventually
becoming 0%/off
Public bug reported:
Release: Ubuntu 10.04 64-bit Desktop Edition
What You Expected to Happen: System volume to remain as set before reboot and
as shown in volume panel applet
What Happened Instead: After reboot/shutdown at and after login system volume
is set to maximum
Extended Description:
24 matches
Mail list logo