This bug is still present in Ubuntu 19.10 and the fix "sudo modprobe
vboxdrv" still works. See:
https://askubuntu.com/q/1189888/156688
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466046
Title:
I was able to install the nodejs package (8.11.4~dfsg-0ubuntu1)
https://packages.ubuntu.com/cosmic/nodejs
on Ubuntu 18.10 with "sudo apt-get install nodejs", but when I tried to install
npm (5.8.0+ds-2)
https://packages.ubuntu.com/cosmic/npm
It failed due to nodejs-dev depending on
Sound seems to be working again now after upgrading to Ubuntu 17.10!!
Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636905
Title:
Sound card not recognized on Dell Vostro 5568
To
Public bug reported:
After upgrading from Ubuntu 17.04 to 17.10, I get a warning about that
option -e is deprecated when starting gnome-terminal from the command
line. For example, assume I want to open a gnome-terminal with two tabs,
and running separate commands in each tab:

$ gnome-terminal
Still present in Ubuntu 16.10 ):
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387131
Title:
Cannot change evince key bindings
To manage notifications about this bug go to:
An update:
To sum up the previous posts in this thread:
The problem with the internal Realtek ALC3246 soundcard of my
Dell Vostro 5568 laptop in Ubuntu (tested with 16.04 and 16.10) seems
to be related to the suspend function. The sound stops working after laptop is
suspended and sound cannot be
Ok then, I have rebooted Ubuntu again, and yes, as I expected I have now
returned to the origianl situation:
When I select "System Settings->Sound" the output device in the dialog
window shows as "Dummy Output" and when I press the "Test Sound" button
no sound is heard from either front left or
Sorry, the attached screen shot for the previous comment was not
correct, here is the correct one.
** Attachment added: "audio3.png"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+attachment/4775374/+files/audio3.png
--
You received this bug notification because you are
Rebooting with headphones unplugged worked fine for a while; then I
suspended my laptop for an hour. When I came back and the laptop was
reactivated (by opening the lid) sound was not working. Now I went to
System Settings->Sound again, and to my surprise some new items had been
added to the
Ok I rebooted Ubuntu with headphones plugged in. I went to System
Settings->Sound and confirmed that everything looked fine. However, when
I tried to play sound from youtube in Google Chrome there was no sound.
I rechecked that the sound was not muted, and that 'aplay -l' showed
correct output. I
I have now done some further research on this. First, I tried to reset
Windows 10 once again. After finished the reset and having rebooted
Windows 10 once more after that. The sound started to work in Windows 10
again. But I also discover something new: If I plugged in the headphones
in Windows
I tried to produce a PulseAudio verbose log by editing /etc/pulse/client.conf
and adding this line to the file:
extra-arguments = - --log-target=newfile:/tmp/pulseverbose.log
--log-time=1
Here is the log file I got after rebooting: see attached file
pulseverbose.log
** Attachment added:
Unfortuneately, the problem was not fixed after all. I was a little bit
to quick to conclude in my last post. Now the sound has stopped working
again (both in Windows and Ubuntu). But it starts with a problem in
Ubuntu. After unplugging the headphones, the "What kind of device did
you plug in?"
Seems like the problem has been partially resolved:
I did not mention that I had a dual boot machine with Windows 10, since I did
not think
it was relevant. Now, here is what I did:
I first reinstalled Ubuntu 16.04 (erased the Ubuntu 16.10 partition).
When I logged into Ubuntu 16.04 the sound
It was not quite correct what I said about flickering stopping only when
mouse moves. It also stops when something is output continuously to the
terminal window. For example, running the following command in gnome-
terminal window:
perl -MTime::HiRes -E '$i=0;while (1) { $i++; Time::HiRes::sleep(
I have the same problem. I installed a fresh Ubuntu 16.10 on my Lenovo
Edge540 laptop. Screen starts flickering during installation from USB
and only stops when the mouse is moving. Very annoying. See this
question on askubuntu.com :
http://askubuntu.com/q/838957/156688
seems like there are many
Public bug reported:
I just reinstalled a fresh Ubuntu 16.10 on my Dell Vostro 5568 laptop.
The audio controller on the laptop is a Realtek ALC3246 with Waves
MaxxAudio Pro. The external interface connector is a microphone
in/stereo headphones/external speakers connector.
When I select "System
*** This bug is a duplicate of bug 1533206 ***
https://bugs.launchpad.net/bugs/1533206
I have removed both wifi and bluetooth hardware from my acer aspire one
kav60, so far its just annoying, didnt try to install yet.
--
You received this bug notification because you are a member of Ubuntu
I tested this on Ubuntu 14.10 running gnome-terminal version 3.6.2 (with
UTF-8 encoding). I tried producing a captial I with strikethrough:
echo -e 'I\U0336'
The following font worked correctly:
- Ubuntu Mono
- Courier 10 Pitch
- Droid Sans Mono
- Free Mono
- TlwgMono
- TlwgTypo
- Ubuntu
This bug is also present in gnome-terminal version 3.6.2. Here is my
configuration:
$ lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04
$ apt-cache policy gnome-terminal
gnome-terminal:
Installed: 3.6.2-0ubuntu1
Candidate: 3.6.2-0ubuntu1
Version table:
***
.cfg'
Saves the title of the tab correctly to the file 'config1.cfg'.
Here is the relevant part of 'config1.cfg':
[Terminal0x325a350]
ProfileID=Default
Title=MyTabTitle
WorkingDirectory=/home/hakon/
Zoom=1
Width=80
Height=24
On the other hand, running
$ gnome-terminal
and the pressing Ctrl+Shift
Public bug reported:
I have a Bash application where I need to complete filenames and
directory names that exist in another directory relative to the current
directory. In the completion list shown in the terminal after I press
TAB, I would like to see directory names with a slash after the name,
Hi Peter, you were completely right! Now I have got some help at
stackoverflow, and it seems that helped solve this issue. There are four
things that seems must be in place to solve it:
1. compopt -o nospace
2. compopt -o filenames
3. Running compgen -f with an absolute path
4. Then
Thanks Peter! See follow-up question at stackoverflow:
http://stackoverflow.com/questions/27244300/how-to-complete-filenames-
relative-to-another-directory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the thorough answer! If I add shopt -s extglob your code is
working.
The question is how to add slashes after directory names and not file names. If
I remove -o filenames and add
compopt -o nospace I still can use compgen -f $cur but it does not add
slashes. And the completions are
Public bug reported:
I am trying to ignore certain directory names when using bash
completion. For example to ignore backup directories I use
$ cat setup.sh
_compTest() {
local curdir cur words val name
cur=${COMP_WORDS[$COMP_CWORD]}
baseFolder=.
curdir=$PWD
cd $baseFolder
I have this problem also. I am using konsole version 2.13.2 on KDE
version 4.13.3 ( Ubuntu version 14.04). Regarding the comment in #6:
there is no file 60-droid-sans-mono-fonts.conf on my system. None of
the other suggestions helped either.. If I open a gnome-terminal and
type
echo `tput
Public bug reported:
The following message is printed to standard error:
FIXME: Oxygen::WidgetSizeData: unknown window type:
meldapp.GtkVBox.GtkNotebook.GtkVBox.GtkTable.GtkVBox.MsgAreaController.MsgArea
The message is repeatedly written to stderr, the number of times
depending on how long the
Seems like all the default fonts in Chromium browser was reset to
Abyssinica SIL after installing Kubuntu desktop. After changing to
DejaVu Sans in Settings-Web Content-Customize fonts.. the fonts
are now quite readable..
--
You received this bug notification because you are a member of Ubuntu
I confirm to have the same issues. From Ubuntu 14.04 I ran apt-get
install kubuntu-desktop, after logging out from Unity and in again in
KDE plasma desktop, I think I started to see some symptoms (for example:
fonts on webpages looked ugly), and logging out again and then logging
into Unity again,
Here is an example of how the fonts now look like in many web pages:
http://askubuntu.com/questions/507966/fonts-messed-up-after-installing-kubuntu-desktop-on-ubuntu-14-04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks like the font issue can be related to the Sans-serif font family, and
that it depends also on the browser. See updated question on askubuntu.com for
an example:
http://askubuntu.com/questions/507966/fonts-messed-up-after-installing-kubuntu-desktop-on-ubuntu-14-04
--
You received this bug
32 matches
Mail list logo
