[Bug 1466046] Re: virtualbox doesnt run VMs since the vboxdrv module is not loaded automatically
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: virtualbox doesnt run VMs since the vboxdrv module is not loaded automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1466046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev
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 libssl1.0-dev. I solved this issue by installing npm with the install script at: https://github.com/npm/cli That is, I used the following command: curl -L https://www.npmjs.com/install.sh | sudo sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794589 Title: libssl1.0-dev conflicts libssl-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636905] Re: Sound card not recognized on Dell Vostro 5568
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726380] [NEW] Option “-e” is deprecated and might be removed in a later version of gnome-terminal
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 --tab --active -e 'bash -c "echo Hello; exec bash"' --tab -e 'bash -c "echo Hello2; exec bash"' Option “-e” 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. Option “-e” 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. But how can I run separate commands for each tab if I am supposed to use -- to terminate the options? For example, the following does not work:  $ gnome-terminal --tab --active -- bash -c "echo Hello; exec bash" --tab -- bash -c "echo Hello2; exec bash" It just opens a single tab. See also: https://askubuntu.com/q/968032/156688 --- System information: $ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 $ apt-cache policy gnome-terminal gnome-terminal: Installed: 3.24.2-0ubuntu4 Candidate: 3.24.2-0ubuntu4 Version table: *** 3.24.2-0ubuntu4 500 500 http://no.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726380 Title: Option “-e” is deprecated and might be removed in a later version of gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1387131] Re: Cannot change evince key bindings
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: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1387131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636905] Re: Sound card not recognized on Dell Vostro 5568
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 recovered unless Ubuntu (or Windows) is reinstalled. Workaround: I have now tested three USB sound cards to work around the issue with the internal sound card: - Deltaco UAC-03 (cheep, and bad sound quality but works out of the box ) - SD-UAUDV2-C119 SDM USB 2.0, 7.1 surround, Xear 3D (cheep, medium sound quality, works out of the box ) - Creative Sound Blaster X-Fi HD (expensive, but excellent sound quality, SPDIF output is not working out of the box) -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636905] Re: Sound card not recognized on Dell Vostro 5568
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 front right speaker. Running aplay -l gives: $ aplay -l aplay: device_list:268: no soundcards found... Any advice on what to do next? -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636905] Re: Sound card not recognized on Dell Vostro 5568
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 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636905] Re: Sound card not recognized on Dell Vostro 5568
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 Output Tab ( see attached file ). It now showed three additional devices: "HDMI/DisplayPort: Built-in Audio", "HDMI/DisplayPort 2: Built-in Audio", and "HDMI/DisplayPort 3: Built-in Audio". But none of these devices worked any better than the original "Headphones: Built-in Audio". If I now uplugged the headphones, there was no sound from the speakers either. And if I tried to replug the headphones, I did not get the popup window about unknown audio device, and still no sound. (aplay -l still shows correct output). I will now try to reboot again and see what happens. I expect I will now have come back to my original problem where sound is permanently disabled, and the sound card is not recognized at all. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636905] Re: Sound card not recognized on Dell Vostro 5568
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 then unplugged the headphones, and sound started to work ( from the speakers ). Then I replugged the headphones, and I got the popup dialog, and then sound started to work from the headphones also. Everything looking fine so far. I then tried to unplug and replug the headphones a few times. Working fine. I will now try to reboot Ubuntu with headphones unplugged. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636905] Re: Sound card not recognized on Dell Vostro 5568
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 10, the sound stopped working in Windows 10 also. If I clicked on the sound icon in the Windows taskbar, Windows would try to fix the sound problem, and asked me to reboot to implement the proposed fix. Then sound started to work again after rebooting ( but only from the speakers ). If I plugged in the headphones, it would work well until I unplugged them. After that the sound stopped working again. Also note: In Windows 10, there was no popup dialog when I plugged in my headphones the first time (In Ubuntu I get the annoying popup dialog asking what device I plugged in). So this might be an indication that the popup dialog is really not necessary in Ubuntu? Anyway, the next thing I did: After having ensured the sound was working from Windows ( after Windows had fixed the sound problem, and I had rebooted windows to implement the fix ) was to boot into Ubuntu. Now the sound worked from Ubuntu 16.04 also ( as expected, since I had not plugged in any headphones yet). I now tested that the speakers produced sound in Ubuntu and then opened the terminal window and ran the commands: $ ls /proc/asound/ card0 cards devices hwdep modules oss PCH pcm seq timers version $ ls /proc/asound/card0 codec#0 codec#2 eld#2.0 eld#2.1 eld#2.2 id pcm0c pcm0p pcm3p pcm7p pcm8p $ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 $ lspci -v | grep Audio 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) Then, opened System Settings->Sound, and confirmed that there was no "Dummy output" in the Output tab. Instead, it now showed "Speakers: Built-in Audio" instead. I then plugged in the headphones, and got the popup dialog "Unknown audio device" and I chose headphones and confirmed that sound was working from the headphones. Then I checked System Settings->Sound again and confirmed that a new item "Headphones: Built-in Audio" was shown in the Output tab. I then unplugged and replugged the headphones five times, every time it worked fine (except for the irritating popup window appearing each time I plugged in the headphones). (The next thing to try now is to reboot Ubuntu once more. I will continue this comment after having rebooted) -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636905] Re: Sound card not recognized on Dell Vostro 5568
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: "PulseAudio verbose log created at reboot." https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+attachment/4775013/+files/pulseverbose.log -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636905] Re: Sound card not recognized on Dell Vostro 5568
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?" dialog does not show the next time I replug the headphones ( which is fine, see https://bugs.launchpad.net/ubuntu/+source/unity- settings-daemon/+bug/1297790 ) however what is not fine is that there is no sound. System Settings->Sound show "Dummy output" in the Output tab, and the system does not recognize the sound card any longer. For example: $ ls /proc/asound/* ls: cannot access '/proc/asound/*': No such file or directory $ aplay -l aplay: device_list:268: no soundcards found... $ sudo lspci -v | grep Audio [no output] The strange thing is that the problem then propagates to Windows 10. How is that possible? Is there settings on the sound card that survives a reboot? If that is the case, how can one reset the sound card to its initial configuration? -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636905] Re: Sound card not recognized on Dell Vostro 5568
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 problem was still there. I then logged into Windows 10 an suddenly realized that the sound problem was also present in Windows 10. So I now suspected it might be a hardware issue and not related to Ubuntu at all. But before ordering service on the machine I decided to try to reinstall Windows 10 also. >From Windows, I selected "Reset Windows" (option "Remove everything"). After logging back into Windows 10 after the reset, the sound problem was still there, but the same day I was about to ship the laptop for service, I logged back into Windows a last time, and, voila, the sound problem was suddenly gone. I then logged back into Ubuntu 16.04, and to my great relief the sound was now working from Ubuntu also! So then it was not a hardware issue, but what was it then? If I should guess now, the problem could maybe be related to the external interface connector on the Dell laptop. Since it is a multipurpose microphone in/stereo headphones/external speakers/headset connector it might have confused Ubuntu? The reason is: Each time I try to connect the headphones in Ubuntu I get a popup dialog asking what audio device I am trying to connect. If I choose headphones it works fine until the next reboot. After that I need to unplug them and replug them for sound to start working again. The problem could also be related to Ubuntu 16.10 vs. Ubuntu 16.04. To check this I would have to reinstall Ubuntu 16.10, but I do not have the courage to do that currently.. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634451] Re: Screen flickers when booting ubuntu 16.10 on USB stick
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( 0.2 );
say "Hello $i" }'
causes the flickering to stop. However, if I increase the sleep delay
between writes to the terminal from 0.2 to 0.3 seconds, flickering
starts again. So the output must be continuous for the flickering to
stop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634451
Title:
Screen flickers when booting ubuntu 16.10 on USB stick
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634451/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634451] Re: Screen flickers when booting ubuntu 16.10 on USB stick
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 people having this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634451 Title: Screen flickers when booting ubuntu 16.10 on USB stick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636905] [NEW] Sound card not recognized on Dell Vostro 5568
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 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 front right speaker ( I have ensured sound is not muted ). Note: Before reinstalling, I asked a question on askubuntu,com: http://askubuntu.com/q/841759/156688 So reinstallation of Ubuntu 16.10 did not help on my sound problem. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553609] Re: blueman-applet crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out
*** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553609 Title: blueman-applet crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1553609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 299158] Re: Liberation Mono, Droid Sans Mono: Combining diacritics out of place
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 Mono The following fonts displayed the strikethrough incorrectly on the following character: - Dejavu Sans Mono - Liberation Mono - Monospace - Nimbus Mono L See also this question: http://askubuntu.com/questions/643568/displaying-unicode-strikethrough- in-gnome-terminal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: Liberation Mono, Droid Sans Mono: Combining diacritics out of place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/299158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294159] Re: Option --active doesn't work as expected
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: *** 3.6.2-0ubuntu1 0 500 http://no.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status When I open gnome-terminal with multiple tabs from the command line, I would like to preselect (on the command line) which one of the tabs should get focus. I tried gnome-terminal --tab -t A --active --tab -t B to set tab A as the active, but instead tab B becomes the active one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294159 Title: Option --active doesn't work as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1294159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440413] [NEW] gnome-terminal --save-config does not save tab titles
Public bug reported: I am trying to save the current gnome-terminal configuration, such that I can later restore it. However, there seems to be a problem when saving Terminal windows with tabs. For example, running: $ gnome-terminal --tab -t MyTabTitle $ gnome-terminal --save-config='config1.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+T to open a new tab, and then right-clicking the tab header bar and choosing Set Title.. from the dropdown menu and typing MySecondTabTitle to set the tab title manually. Then from the same terminal running: $ gnome-terminal --save-config='config2.cfg' saves the configuration to file 'config2.cfg', but the title MySecondTabTitle is not saved to the file. Here is the relevant section from 'config2.cfg': [Terminal0x3216350] ProfileID=Default WorkingDirectory=/home/hakon/ Zoom=1 Width=159 Height=42 --- My problem is that I cannot use the first approach above (specifying tab name on the command line) since I usually do not know what the tab names would be at this point. The tab names are instead created dynamically during my work session. And, at the end of my work session I would like to save my configuration using 'gnome-terminal --save-config'.. so I need that command to save the tab titles to the config file.. $ 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: *** 3.6.2-0ubuntu1 0 500 http://no.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440413 Title: gnome-terminal --save-config does not save tab titles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1440413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439851] [NEW] complete -o filenames incorrectly adds slashes after directory names
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,
and filenames with no slash after. This will help the user to
distinguish between directory names and filenames.
As I understand it, there are two ways to achieve this:
a) either use 'complete -o nospace', or
b) use 'complete -o filenames -o nospace'
For option a), there is a problem as soon as the depth of the path exceeds 1.
For example: If I have directories
- a/b/c
- a/b/d
I will, after pressing TAB in the terminal window get
$ cmd a/
b/c b/d
so the completion list will be 'b/c', 'b/d' instead of the less verbose
'c', 'd' (which is also desired, and also how 'complete -o filenames'
works..)
For option b) , the problem is that 'complete -o filenames' will add
slashes after completion words that exist as directory names in the
current directory. This is of course, correct if you try to complete
names in the current directory, but if the completion words are taken
from another directory, this can lead to either multiple slashes (two
slashes) after directory names, or to filenames with trailing slashes (
a filename should of course not have a trailing slash after it).
Here is an example, that I hope will illustrate the problems:
First generate some dummy directories and files:
$ mkdir a
$ touch b
$ mkdir c
$ mkdir dir1
$ touch dir1/a
$ mkdir dir1/b
$ mkdir dir1/c
$ mkdir dir1/b/c
$ mkdir dir1/b/d
Then consider the following completion setup:
$ cat setup
_my_test1() {
local cur comp_dir
cur=${COMP_WORDS[$COMP_CWORD]}
comp_dir=$PWD
COMPREPLY=( $( cd $comp_dir; compgen -f $cur ) )
}
complete -o filenames -o nospace -F _my_test1 test1
_my_test2() {
local cur comp_dir
cur=${COMP_WORDS[$COMP_CWORD]}
comp_dir=$PWD/dir1
COMPREPLY=( $( cd $comp_dir; compgen -f $cur ) )
}
complete -o filenames -o nospace -F _my_test2 test2a
complete -S '/' -o nospace -F _my_test2 test2b
_my_test3() {
local cur comp_dir temp word
cur=${COMP_WORDS[$COMP_CWORD]}
comp_dir=$PWD/dir1
temp=( $(cd $comp_dir; compgen -f $cur) )
COMPREPLY=()
for word in ${temp[@]} ; do
[[ -d $comp_dir/$word ]] word=$word/
COMPREPLY+=( $word )
done
}
complete -o nospace -F _my_test3 test3
_my_test4() {
local cur comp_dir temp word
cur=${COMP_WORDS[$COMP_CWORD]}
comp_dir=$PWD/dir1
temp=( $(cd $comp_dir; compgen -f $cur) )
COMPREPLY=()
for word in ${temp[@]} ; do
[[ -d $comp_dir/$word ]] word=$word/
COMPREPLY+=( $word )
done
}
complete -o filenames -o nospace -F _my_test4 test4
_my_test5() {
local cur comp_dir temp word
cur=${COMP_WORDS[$COMP_CWORD]}
comp_dir=$PWD/dir1
temp=( $(cd $comp_dir; compgen -f $cur) )
COMPREPLY=()
for word in ${temp[@]} ; do
[[ -d $comp_dir/$word ]] word=$word/
[[ -d $word ]] word=${word%/}
COMPREPLY+=( $word )
done
}
complete -o filenames -o nospace -F _my_test5 test5
Then source the file in the Bash terminal window:
$ . setup
Then:
- 'test1': will complete correctly in the current directory. This example is
just to show how the completion should work when the directory to complete in,
is different from the current directory.
- 'test2a': will not add slashes after directory names in 'dir1', but will
incorrectly add slashes after directory names that also exist in the current
directory.
- 'test2b' : Investigates how 'complete -o nospace' works without '-o
filenames' option
- 'test3' : Same as 'test2b', but also manually adds slashes after
directory names in 'dir1'.. (but still leads to the verbose completion
lists described above in a))
- 'test4' : same as 'test2a', but also manually adds slashes after directory
names in 'dir1',
but still unwanted slashes are added after names that also exist in the
current directory
- 'test5' : Same as 'test4' but also tries to trick Bash completion, by
removing slashes from names that also exists in the current directory.
Notice that still there is no way to avoid the incorrect slash after the
file 'a' in 'dir1'. The reason is that the name 'a' also exists as a
directory name in the current directory..
$ lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04
$ apt-cache policy bash-completion
bash-completion:
Installed: 1:2.1-4
Candidate: 1:2.1-4
Version table:
*** 1:2.1-4 0
500 http://no.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
** Affects: bash-completion (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439851
Title:
complete -o filenames
[Bug 1394920] Re: complete -o filename can't be used with filenames relative to another directory to handle space vs. trailing /
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 postprocessing the results of compgen
a) removing absoulte path prefix
b) adding slashes after filenames
So here is minimal example (not handling quoting and spaces in file
names):
_compTest() {
local cur tmp val
cur=${COMP_WORDS[$COMP_CWORD]}
tmp=~/tmp/
tmp_escaped=${tmp//\//\\\/}
cur=$tmp$cur
COMPREPLY=( $(compgen -f $cur) )
for ((i=0 ; i${#COMPREPLY[@]}; i++ )) ; do
val=${COMPREPLY[$i]}
[[ -d $val ]] val=$val/
COMPREPLY[$i]=${val/$tmp_escaped/}
done
}
complete -o filenames -o nospace -F _compTest aaa
Thanks again for excellent help!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394920
Title:
complete -o filename can't be used with filenames relative to another
directory to handle space vs. trailing /
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1394920/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394920] Re: complete -o filename can't be used with filenames relative to another directory to handle space vs. trailing /
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. https://bugs.launchpad.net/bugs/1394920 Title: complete -o filename can't be used with filenames relative to another directory to handle space vs. trailing / To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1394920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394920] Re: complete -o filename can't be used with filenames relative to another directory to handle space vs. trailing /
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 not broken at / (if I insert it manually) such that I get a completion list with a/b/c instead of just c when I try to complete a/b.. Do I have to add a slash to $COMP_WORDBREAKS variable? There is a post a stackoverflow : http://stackoverflow.com/questions/10528695/how-to-reset-comp-wordbreaks-without-effecting-other-completion-script It refers to a function _get_comp_words_by_ref .. where is this function documented? I searched the bash manual, http://www.gnu.org/software/bash/manual/bashref.html but it is not mentioned there.. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394920 Title: complete -o filename can't be used with filenames relative to another directory to handle space vs. trailing / To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1394920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394920] [NEW] Filename completion not working if current directory does not match with COMPREPLY array
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
words=( $(compgen -f $cur) )
COMPREPLY=()
for val in ${words[@]} ; do
name=$(basename $val)
if [[ $name == backup ]] ; then
continue
fi
COMPREPLY+=( $val )
done
cd $curdir
}
complete -o filenames -F _compTest aaa
After sourcing this:
$ . setup.sh
I can type
$ aaa tabtab
and it works fine. However if I use another baseFolder, for example
setting
baseFolder=$HOME/base
in the above script (setup.sh) (where $HOME/base is different from the
current directory) the completion list is no longer what I would expect.
That is:
* slashes are missing at the end of directory names, and
* a space is added after each completed directory name, instead of a slash (/)
$ lsb_release -rd
Description:Ubuntu 14.04.1 LTS
Release:14.04
$ apt-cache policy bash-completion
bash-completion:
Installed: 1:2.1-4
Candidate: 1:2.1-4
Version table:
*** 1:2.1-4 0
500 http://no.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
100 /var/lib/dpkg/status
** Affects: bash-completion (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394920
Title:
Filename completion not working if current directory does not match
with COMPREPLY array
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1394920/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 972279] Re: Konsole displays bold text with normal weight
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 bold`bold`tput sgr0` it works fine (I get bold text) but it does not work in konsole.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972279 Title: Konsole displays bold text with normal weight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/konsole/+bug/972279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382759] [NEW] meld prints FIXME messages to standard error when files are identical on Ubuntu 14.04
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 files are. System information: $ lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 $ apt-cache policy meld meld: Installed: 1.8.4-1 Candidate: 1.8.4-1 Version table *** 1.8.4-1 0 500 http://no.archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages 100 /var/lib/dpkg/status (Note: I have only tested this from Kubuntu) To reproduce the error: $ echo 1 1.txt $ echo 1 2.txt $ meld 1.txt 2.txt This will produce 2 lines with the message when the user exits meld. The message also appears when there are a large number of identical lines in the beginning of the file, such that the change highlighting incomplete message appears. Expected output: None. This error message messes up my terminal window, and gives no useful information to the user. ** Affects: meld (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382759 Title: meld prints FIXME messages to standard error when files are identical on Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meld/+bug/1382759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335446] Re: Installing kubuntu-desktop to normal ubuntu ruins unity
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335446 Title: Installing kubuntu-desktop to normal ubuntu ruins unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1335446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335446] Re: Installing kubuntu-desktop to normal ubuntu ruins unity
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, more symptoms became apparent. The most important issue for me now is to get the fonts back as they were. Some web pages is almost unreadable with the current fonts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335446 Title: Installing kubuntu-desktop to normal ubuntu ruins unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1335446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335446] Re: Installing kubuntu-desktop to normal ubuntu ruins unity
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. https://bugs.launchpad.net/bugs/1335446 Title: Installing kubuntu-desktop to normal ubuntu ruins unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1335446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335446] Re: Installing kubuntu-desktop to normal ubuntu ruins unity
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335446 Title: Installing kubuntu-desktop to normal ubuntu ruins unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1335446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
