@mkukri
A couple of years ago I had 2 installations of EndeavourOS on two different
partition, and the Efi menu showed 2 different entries. I can't remember
exactly but the menu entries looked like these:
- EndeavourOS 12345...
- EndeavourOS 14789...
I don't know if the boot process is meant to
It looks like any kind of drag and drop doesn't work in the snap version of
Firefox under Wayland session.
First I've noticed that I couldn't personalize the toolbar, therefore I've open
this bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1760449
Then I realized also tabs couldn't be mo
@Heinrich Schuchardt (xypron)
Thanks, tried both workarounds but with no success.
Didn't mention before but switching on my computer I can still get the
EFI boot menu pressing F12. From there I can select any other system and
set one of them as the default system at boot.
--
You received this bu
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1965689/+attachment/5571166/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965689
apport information
** Tags added: apport-collected wayland-session
** Description changed:
Fresh install of Ubuntu 22.04 on multi-boot system.
Steps:
1. Switch on computer.
2. You see for about 10 seconds a black screen instead GRUB MENU.
3. After 10 seconds Ubuntu boots normally.
Public bug reported:
Fresh install of Ubuntu 22.04 on multi-boot system.
Steps:
1. Switch on computer.
2. You see for about 10 seconds a black screen instead GRUB MENU.
3. After 10 seconds Ubuntu boots normally.
Extra tests:
- During the 10 seconds of black screen, I can press ENTER and Ubuntu w
** Tags added: hirsute impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944477
Title:
Wayland - double monitor: edge tiled windows change position after
suspension
To manage notifications ab
Public bug reported:
- System: Ubuntu 21.04 (experienced also with Ubuntu 21.10)
- Wayland session
- Hardware setup: laptop connected to 2 extra monitors
- Laptop screen: off
- Samsung (left monitor): on
- LG (right monitor): on
- DESCRIPTION
Edge tiled windows can be placed in a different
@seb128
Yes correct, it was automatic partitioning.
I've chosen the "Install Ubuntu alongside.." option: https://postimg.cc/N2hnmtxR
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925187
Title:
erro
Just to confirm everything I've written in message #25.
I've repeated the same tests with the deily iso 20/4.
The workaround at message #13 is no more needed for Ubuntu 21.04, but it
can still be useful for Ubutnu 20.10
The step:
sudo apt install --reinstall grub-pc
can be more easily replaced b
> juliank
> This is a feature, not a bug.
It's what I thought once I was aware of all these troubles:
https://discourse.ubuntu.com/t/groovy-to-use-grub2-for-booting-installer-media-in-any-modes-on-all-architectures/16871/34
But it looks like nobody knew about EFI partition with BIOS and I've
been
Hi everybody,
As guiverc I have updated Ubiquity on a older Ubuntu iso image to get version
21.04.19
In good part I can confirm good news!
...but there are still bizarre things
I've performed 2 test installation:
1- MANUALLY CHOSING A PARTITION
Same result reported by guiverc at comment #24
Th
** Description changed:
Ubiquity 21.04.19 installed via apt on a previous iso daily-build as an
iso with 21.04.19 at the moment is not available.
DESCRIPTION:
- Partition table: msdos (MBR)
- /dev/sda1 with Ubuntu already installed
- /dev/sda2 and /dev/sda3 both Ext4
Install
** Summary changed:
- Ubiquity 21.04.19 fails in 'install alongside' in extended partition
+ Ubiquity 21.04.19 ends in 'error install grub' but Ubuntu get installed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Public bug reported:
Ubiquity 21.04.19 installed via apt on a previous iso daily-build as an
iso with 21.04.19 at the moment is not available.
DESCRIPTION:
- Partition table: msdos (MBR)
- /dev/sda1 with Ubuntu already installed
- /dev/sda2 and /dev/sda3 both Ext4
Installation modality: Install
> juliank
> Jeremie, the correct workaround is to deselect the EFI system partition when
> you configure partitions in the installer, as I explained in comment #5.
Let's say that the EFI partition is not selected, it only shows the type (EFI)
but it's not selected a mount point.
As reported in co
> juliank:
> Jeremie, you reported a separate bug for the issue of the installer
> automatically picking
> up the USB stick's USB, please comment there if you have to.
I know and I apologize, but here is where many other users experienced
problems related to EFI/BIOS and I thought it could be a g
@lproven
Good observation.
The EFI boot partition is created inside USB device at least with the latest
versions of major gui utilities available in Ubuntu: gnome-disk-utility and
usb-creator-gtk.
balenaEtcher also does it.
--
You received this bug notification because you are a member of Ubun
There's an easier WORKAROUND in case you have no space for an extra EFI
partition.
First of all a resume of the issues related to 'EFI on BIOS'.
The system itself get installed. Problem is that Ubiquity thinks that an ESR
(EFI) partition is needed even on computers with BIOS. And it does installs
Got the WORKAROUND and it's quite easy :D
(Thanks guiverc, you gave the idea!)
As you have done I tried to boot the system keeping the USB installer device
connected to the computer. I've just set 'first boot from hard disk' inside
bios settings... and the system boots.
Then I've uninstalled gru
** Description changed:
Ubuntu 21.04 - 16/4 daily build - Ubiquity 21.04.15
Even on computers with old BIOS an ESR (EFI) partition will be
automatically created when installing Ubuntu using one of the automatic
options like "Erase disk and install Ubuntu", "Install Ubuntu alongside
ot
** Description changed:
Ubuntu 21.04 - 16/4 daily build - Ubiquity 21.04.15
Even on computers with old BIOS an ESR (EFI) partition will be
automatically created when installing Ubuntu using one of the automatic
options like "Erase disk and install Ubuntu", "Install Ubuntu alongside
ot
Some more info:
- I repeated the installation selecting the "don't use this partition" option
for the EFI partition of the USB device.
The result is still the same like in the example of guiverc:
/dev/sda1 on /target type ext4
/dev/sdb2 on /target/boot/efi
- I filed a new bug report: bug #192485
** Description changed:
Ubuntu 21.04 - 16/4 daily build - Ubiquity 21.04.15
Even on computers with old BIOS an ESR (EFI) partition will be
automatically created when installing Ubuntu using one of the automatic
options like "Erase disk and install Ubuntu", "Install Ubuntu alongside
ot
Public bug reported:
Ubuntu 21.04 - 16/4 daily build - Ubiquity 21.04.15
Even on computers with old BIOS an ESR (EFI) partition will be
automatically created when installing Ubuntu using one of the automatic
options like "Erase disk and install Ubuntu", "Install Ubuntu alongside
other system", et
Hi and thanks for your reply.
I'm going to do some more tests.
Anyway, if you select "Erase the disk and install Ubuntu" the installer
is going to create an ESP on /dev/sda (see the attached picture). I
didn't perform this type of installation (I did it few months ago and it
actually create the ES
Hi,
I've tried to install the 16/4 daily build with Ubiquity 21.04.15, but I'm
still experiencing the same problems.
I've just in case filed this bug report: bug #1924823
I've tried to manually install Ubuntu on one of the Ext4 primary partition.
Didn't try any other modality, just seen that sel
Public bug reported:
This bug report is a duplicated of bug #1902269 performed with Ubuntu 21.10.
Basically installation fail when the installer doesn't find an EFI (ESR)
partition on computers with legacy BIOS.
This time I have used Ubuntu 21.04 also to test the new version of
Ubiquity package
Same problem on 21.04, Ubuntu installer thinks that BIOS is UEFI.
Just 2 months left before the the final release. Any chance for a fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893964
Title:
After many months, I had the opportunity to put my hands on the computer that
had these audio problems:
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/comments/31)
...and now the audio works without any workaround.
Current Ubuntu version: 20.04.2
Kernel: 5.8.0-41
--
You received
@Timo Aaltonen
The new package fix the problem. Good job!
Here what I've done:
1. enabled the proposed repository
2. updated gnome-shell-extension-desktop-icons to version
20.04.0+git20200908-5~ubuntu20.10.0
3. Test case: created a file in the desktop and tried drag & drop inside an
open folder.
My bug report #1902269 has been marked as duplicated of this one even if
the description it's not exactly the same.
In any case it looks the problem is related to the EFI (ESP) partition,
that should never be used on old BIOS or UEFI in Legacy Mode, but for
some reasons the installer want it... ev
** Description changed:
(I'm duplicating this bug
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964 in order
to provide more data to developers).
Installation with manual partitioning of Ubuntu 20.10 on BIOS hardware
fails while executing "grub-install /dev/sda".
We
Public bug reported:
(I'm duplicating this bug
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964 in order
to provide more data to developers).
Installation with manual partitioning of Ubuntu 20.10 on BIOS hardware
fails while executing "grub-install /dev/sda".
We already know as re
Similar problem with:
- Ubuntu 20.04 LTS
- Fujitsu LifeBook A530
- $ lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High
Definition Audio (rev 05)
THE PROBLEM:
No sound. Gnome audio system settings shows "Dummy Audio" as output device.
Trying with Lubuntu
Just to confirm gjs version 1.63.92-1 fixes the problem.
(P.S. focal-proposed activated)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865169
Title:
volume and light not working in Gnome Shell 3.3
Bug is still there.
Quick example when my computer starts:
if I don't do anything, Ubuntu 19.10 will be booted.
If I press [F12] I get the Boot Menu list, which shows:
1. ubuntu
2. deepin
3. CD/DVD Drive ...
4. Drive0 HDD ...
There is only 1 entry for Ubuntu (which is the one for 19.10) but on my
Public bug reported:
Gnome Tweaks in Ubuntu 19.04
Selecting "Top Bar -> Application Menu", there is no way to hide the app
menu.
I suppose this happens because the app menu has been changed in the
latest Gnome Shell version and that's why the switch has no effect.
** Affects: gnome-tweaks (Ubun
Mines 3.26.0 - Ubuntu 17.10
I found a related upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=789399
** Bug watch added: GNOME Bug Tracker #789399
https://bugzilla.gnome.org/show_bug.cgi?id=789399
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi,
Another main problem is that the *buntu 17.10 ISO images are still
down-loadable. Not all the users read linux news and are aware of this bad bug.
Unfortunately a warning on the ubuntu.com download page is not enough. There
are infinite ways to reach the download links of the 17.10.
Also, d
I found the same problem with the language setup on Ubuntu 17.10.
This could be related to the new Gnome Settings (just let me know if you think
I should open a new bug report).
I was running Ubuntu 17.10 in Italian language, previously installed
with the old Gnome Settings. I wanted to switch to
** Summary changed:
- Settings for external monitor are delete after reboot, suspension, log out
+ Settings for external monitor are deleted after reboot, suspension, log out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I have open a new bug related to the fact that gnome settings doesn't
"remember" the setup for external monitors after log out, restart..
Please add comment here: https://bugs.launchpad.net/ubuntu/+source
/gnome-control-center/+bug/1716341
--
You received this bug notification because you are a
Public bug reported:
New Gnome Settings on Ubuntu 17.10
Settings for external monitor are working but after reboot/suspension
/log-out log-in, the system will not remember the setup.
Example:
1- open Gnome Settings and select "Devices → Displays"
2- set the external monitor as "Single Display" a
After the latest updates with the new Gnome Settings I can change the
setup for external monitors.
The problem is that the system doesn't remember the settings, so after a
log out (or restart or suspension, etc..) I need always to open again
Gnome Settings and set the external monitor as "Single D
*** This bug is a duplicate of bug 1714410 ***
https://bugs.launchpad.net/bugs/1714410
@Peter Magnusson
Thanks, I've marked the report as duplicated of Bug #1714410.
Hopefully this bug will disappear once the new Gnome Settings will be
updated to the new version https://bugs.launchpad.net/ubu
Public bug reported:
Fresh install of Ubuntu 17.10 (laptop + external monitor).
Running "Settings → Displays → Primary (or Secondary)", all the options:
- Primary
- Secondary Display
- Mirror
- Turn Off
are not working.
Also "Arrange Combined Displays" is not working.
ProblemType: Bug
DistroR
Public bug reported:
Ubuntu 17.10 - WAYLAND SESSION
Mid-click lower (it can be set with Tweaks → Windows → Titlebar Actions
→ Middle Click → Lower) doesn't work any more with all the Gnome
applications that use the new titlebar (headerbar).
It's still working with some apps that use the classic
@Sean
I tried your fstab entry and it works perfectly, even if I switch off the
computer immediately after the boot.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577120
Title:
Mounted NFS
OK, it seems that workaround #4 works if I wait a bit before
shutdown/reboot. If I switch off the computer immediately after the
boot, the problem will still be there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
@Sean
I have tried to use your workaround #4 but unfortunately didn't work on my
computer.
Please could you let me know which options are you using on your /etc/fstab?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Hi Brian,
It works.
I've just enabled the -proposed and installed the libmtp
1.1.6-20-g1b9f164-1ubuntu2.1 package. Then I've connected the BQ 4.5 via
USB.cable. Nautilus starts automatically as expected.
Thanks, well done!
--
You received this bug notification because you are a member of Ubun
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376212
Title:
BQ Aquaris E4.5 Android Phone not recognised by libmtp
To manage n
Public bug reported:
Ubuntu 14.04 doesn't mount the BQ Aquaris 4.5 once it is connected with usb
cable.
Everything works fine on Ubuntu 14.10 and 15.04.
Workaround
(found here http://ubuntuforums.org/showthread.php?t=2270325)
Installing an updated version of libmtp from this repo
https://launch
Thank you very much Lem, it works with Unity Tweak Tool.
In the meantime I discovered that it works also running the following
command:
$ dconf write /org/gnome/desktop/wm/preferences/action-middle-click-
titlebar "'lower'"
It might sound crazy, but this is one of the most important feature to m
The middle click problem came back in Ubuntu 15.04.
(Also tried the daily-live "26-Mar iso 64bit")
I had a look into dconf-editor and unfortunately there's no way to set
"lower" in /org/gnome/desktop/wm/preferences/action-middle-click-
titlebar.
--
You received this bug notification because you
Public bug reported:
(python-moinmoin 1.9.7 on Ubuntu 14.04)
Tried to creat a class in the .css file for tables without borders, but testing
the class in a wiki page, like this:
|| ... || ... ||
didn't work. As a workaround I tried to remove the double quotes:
|| ... || ... ||
It worked and I h
Today I was updating one of the system (Lubuntu) on one of my test partitions.
The system wasn't the default one at the boot, but as the grub packages have
been updated, after the re-boot I have discovered that it was set as the boot
default system...
This bug creates problems even with the upda
Discovered the same problem on Ubuntu 14.04 and 14.10.
One of the worst thing is that a step of the installation (GRUB position
in the "mount point" settings) is just broken and doesn't work properly
with multi-boot systems. The last installed *buntu will be always set as
the default system, even
Before performing the reverse bisect process I thought to ask directly
in the linux-acpi mailing list which was the patch (or the set of
patches) that have fixed the acpi/backlight issue .
This is the answer:
(original message http://marc.info/?l=linux-acpi&m=140429106012604&w=2)
Hi Christopher,
in the last couple of days I tried the kernels I didn't try before and now I
can tell for sure that the fix arrived with the v3.16rc1 kernel. I also had a
look at the bisect documentation and tried to move my first steps.
In the meantime Aaron Lu, the guy that was looking after
Some good news.
I've tried the upstream kernel 3.16-rc2 and the brightness shortcut
"Fn+F6/Fn+F7" is now working out of the box without any workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318299/+attachment/4124592/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318299
Title
Right, this should be OK http://marc.info/?l=linux-
acpi&m=140178030214298&w=2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318299
Title:
[Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 do
@Christopher
Here the bug report on the Linux mailing list:
http://lkml.iu.edu//hypermail/linux/kernel/1406.0/00478.html
hope it's OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318299
Title:
[
Hi Christopher,
Tried the 3.15-rc7 kernel but the problem is still there. Pressing
Fn+F6/Fn+F7 the brightness doesn't change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318299
Title:
[Fujitsu L
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.15-rc7
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/131829
** Description changed:
(Fujitsu Lifebook A512 - Ubuntu 14.04 - Linux 3.13.0-24-generic x86_64)
Pressing Fn+F6 or Fn+F7 the brightness doesn't change.
-
WORKAROUND (found here http://ubuntuforums.org/showthread.php?t=2192471)
1) The command:
for i in /sys/class/backlight/*; do
Here the new bug related to Fujitsu Lifebook A512:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318299
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249219
Title:
8086:0116 [Lenovo B570] b
Public bug reported:
(Fujitsu Lifebook A512 - Ubuntu 14.04 - Linux 3.13.0-24-generic x86_64)
Pressing Fn+F6 or Fn+F7 the brightness doesn't change.
WORKAROUND (found here http://ubuntuforums.org/showthread.php?t=2192471)
1) The command:
for i in /sys/class/backlight/*; do echo $i;cat $i/brigh
On my Fujitsu Lifebook A512 I should be able to adjust the brightness
pressing Fn+F6 or Fn+F7. The brightness-indicator pop-up works but the
brightness doesn't change. This should be related to the cpi_video0 /
intel_backlight issue.
I found a workaround here
http://ubuntuforums.org/showthread.php
At this stage a backport would make sense only to Ubuntu 12.04 LTS which is
going to be supported till 2017. I don't use it but of course a backport could
be useful for other people who are using the 12.04 and planned to use it til
the EOL.
I think it's up to the developers to take a decision. I
Just to let you know that the touchpad is now working properly on
Lifebook A512 with Ubuntu 14.04 and linux 3.13.0-20-generic.
I hope it will be the same on Lifebook AH532.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Touchpad works "out of the box" on Ubuntu 14.04 with linux
3.13.0-20-generic
This was the xinput output with the old kernel 3.13.0-19-generic:
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)
@Christopher M. Penalver (penalvch)
Here we are: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1294027
Hope it's OK.
Now I can describe the workaround, which might be helpful for other
users:
1- Downloaded drivers here
http://www.dahetral.com/public-download/alps-psmouse-dlkm-for-3-2-and-
Public bug reported:
As suggested here:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1041916/comments/45
I run the "ubuntu-bug xorg" in orderd to get more infos related to bug Bug
#1041916 about touchpad not working (scrolling and middle click "left and right
boutt
Had same problem on Lifebook A512 - Ubuntu 13.10 64bit and 14.04 Live version.
The touchpad's scroll and mid-click (Left+Right button) were not working.
I tried the commands suggested on #14 and this similar workaround
http://nwoki.wordpress.com/2012/10/02/multitouch-fix-for-alps-touchpad
Sorry,
The Dash has got filters again. (Unity 7.1.2+14.04.20140225)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283159
Title:
Dash: no filters
To manage notifications about this bug go to:
https://bugs
As previously reported on Bug #1282264, the middle click on the title
bar still works when windows are maximised.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283849
Title:
LIM breaks middle click
Same story in Ubuntu 14.04
(Unity 7.1.2, Compiz 0.9.11, Intel card, RAM 2G)
Opening the Dash will increase the memory usage of Compiz from 30 MiB to
90~100 MiB.
The system and the applications are working fine.
I didn't experienced any particular problem. just noticed compiz increasing
the r
Public bug reported:
Middle-click on title bar should put a window behind all the others, but this
happens only if a window is maximized.
The mid-click on the title bar of a resized window, just doesn’t work.
In dconf-editor the option "Org → gnome → Desktop → wm → action-middle-
click-titlebar"
** Tags added: verification-done-raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1223928
Title:
replace medibuntu with videolan archive for install-css
To manage notifications about this bug g
Just upgraded compiz from quantal-proposed.
Gedit is now working propperly with compiz grid plugin.
Thanks, well done!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067812
Title:
Gedit, blocked wi
I have seen that the title and the description have been changed and now
they includ Nautilus, but I didn't have any problem with Nautilus. On my
installation it works fine with the grid plugin.
I got this kind of problem only with Gedit. Talking about other programs
I can only say that some appli
Public bug reported:
After that Gedit has been resized to one of the corners (shortcuts compiz grid
plugin: Ctrl+Alt+Num_1/3/7/9) it's not possible to drag the window.
Workaround: it's possible to move/drag the window again resizing the window
half screen (combination "Ctrl+Super+Left/Right Arro
Public bug reported:
The grid plugin is working with Gedit only using shortcuts. Trying to drag the
top bar against the edges (like this
http://www.youtube.com/watch?v=5w5OapWK2Xo) doesn't work.
And also, after the window have been resized to the top or bottom corners
(shortcuts Ctrl + Alt + Nu
I have noticed the same situation on a installed and up to date version
of Ubuntu 12.04 (32bit).
Clicking the NetworkManager icon only four items were available. But
after deactivating and then activating the "Enable Wireless" option, all
the items were again available.
I tried to log out and sta
I agree with #3 too.
That could be the best solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/841847
Title:
Dash - unable to select multiple search filters within the same filter
category s
I have noticed this new behaviour and I was wondering whether this could
be a bug or a new feature. Finally I found this page.
I think this setup might be useful to search files, but it tends to be annoying
with the Application lens. For instance if I'm watching the "System" category,
then selec
@pitti
Ctrl-Alt-KP_9 works now properly with the oneiric-proposed package on
11.10x86. Thanks!
Still problems with the Ctrl-Alt-KP_4 and Ctrl-Alt-KP_6. The windows can
be resized only half screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I confirm the bug on 10.04 and 11.04 with the old iPod Shuffle 512MB.
Also, both the workarounds (removing libgpod-common or editing
90-libgpod.rules) are working.
Has anyone experienced problems with iPod nano 5g after the
90-libgpod.rules workaround?
--
You received this bug notification beca
91 matches
Mail list logo
