@arighi Yes it's working with 6.8.0-22.22. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055805
Title:
touchpad not working with kernel 6.8
To manage notifications about this bug go to:
Somehow I can't get 6.8.0-20 after adding the ppa and updating. But in
some way I got the 6.8.0-19 kernel now (from proposed?) and that's
working fine with the touchpad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Latest mainline build of kernel 6.8.1 is working. Touchpad on MacbookPro
2012 is working now. Thanks! This kernel is coming to Ubuntu 24.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055805
** Summary changed:
- tochpad do not working with kernel 6.8
+ touchpad do not working with kernel 6.8
** Summary changed:
- touchpad do not working with kernel 6.8
+ touchpad not working with kernel 6.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Same problem (and solution) for MacBook Pro 2012
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055805
Title:
tochpad do not working with kernel 6.8
To manage notifications about this bug go to:
Public bug reported:
This is an upstream bug that prevents using stlink devices with openocd
entirely with the jammy versions of openocd and libusb. This is a bug in
openocd that was exposed by a change in libusb-1.0.24.
Upstream has committed a fix for this already (intentionally small to
Public bug reported:
This is really an upstream bug, but I found no upstream bug tracker or
contact address, so I'm hoping the upstream maintainer might be reading
along here (and it's a bug in the Ubuntu version as well, so not
entirely off here).
The problem is that when I set a debounce time
Also, the bug that is described here is about things breaking on
*non*-nvidia systems. If you have problems on nvidia systems, please do
not add comments here, you are seeing another problem. See also
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/comments/37,
and if the bug
@Jack, I'm not sure about nvidia support, but I do think that it is
really unrelated to *this* particular bug (which is about a mistake in
the rules file that caused the nvidia-specific rules to be applied to
other systems, breaking wayland on non-nvidia systems, and which should
be fixed now).
Jeremy, I'm not sure the fix is complete yet, did you test this? I
believe our added patch still removes the nvidia-only guard block
(leaving only the gdm_nvidia_end label, but no jump to it), so the
nvidia suspend checks are still applied to other machines (which will
not have e.g.
> I have no session menu at all after upgrading to Jammy today. Is this
the right bug report for it, or should I open a new one? It wasn't
entirely clear to me from the description.
Sounds like the same bug - if only one session is available, gdm hides
the menu entirely I believe (I also have no
I just reported
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969250 which was
marked as duplicate of this bug (which it is), but do check that bug for
a bit more analysis on where the bug is. TL;DR: there are nvidia-
specific checks in 61-gdm.rules that are no longer guarded by a check
for
Public bug reported:
I was happily using wayland so far on an Intel Tiger Lake laptop. Then I
did an upgrade, including upgrading gdm3 42.0-1ubuntu2 to 42.0-1ubuntu4,
rebooted, and got logged into an Xorg session.
Investigating, it seems this was caused by this patch, reverting in
manually
Looks good, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820586
Title:
Should document keys are not trusted by default
To manage notifications about this bug go to:
Hm, that patch is indeed old, that is not consistent with what I thought
was going on. So I looked a little closer.
> Looking at the sources, I think this can be traced to:
- Switching from a custom Xsession file to the upstream Xsession file in
3.38.0-1ubuntu1, combined with
- An oversight in
Just tested, the above test solves the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955850
Title:
/etc/X11/Xresources no longer loaded, error in patch
To manage notifications
Public bug reported:
After upgrading from 21.04 to 21.10, my /etc/X11/Xresources/ directory
no longer loads on login.
Looking at the sources, I think this can be traced to:
- Switching from a custom Xsession file to the upstream Xsession file in
3.38.0-1ubuntu1, combined with
- An oversight
Hi Sebastien (seb128),
I do not know which log file you mean. Where in my system can I locate
this file?
Matthijs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901192
Title:
package tex-common
Public bug reported:
Description:Ubuntu 20.04.1 LTS
Release:20.04
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: tex-common 6.13
ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
Uname: Linux 4.15.0-122-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
I just tried installing gdb-multiarch as a replacement for gdb-arm-none-
eabi for an Atmel SAMD target and an STM32 target, and that worked out
of the box. Maybe this issue can be closed?
A transitional package depending on gdb-multiarch might have been
useful, but since this package has been
This is still a problem: I wanted to upgrade from eoan to focal and
forgot about this bug, so the upgrade failed again (I think it actually
crashed this time, the GUI window disappeared, but I accidentally
dismissed the "send report" prompt, so I'm not sure how exactly).
It seems the pattern is
This is fixed in version (0.5.1-1), which is included in the Groovy
20.10 release. Only Focal 20.04 is still affected, since earlier
versions had older versions of Python that did not remove the deprecated
module yet.
Considering this bug completely prevents this package from working and
20.04 is
Public bug reported:
I'm running Ubuntu 19.10 and got a message prompting me to upgrade to
20.04. I clicked the "Upgrade now" (or something similar) button and
then nothing happens at all.
Looking in the journal, I see:
jun 22 08:19:00 grubby check-new-release-gtk[27508]: Checking for a new
This bug is reported and fixed upstream at
https://github.com/SpamExperts/pyzor/issues/74
Looks like the attached patch is essentially the upstream fix.
** Bug watch added: Debian Bug tracker #923077
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923077
** Also affects: pyzor (Debian) via
I experience the same problem with python 3.5 on Xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832215
Title:
If python package is installed under
get_python_lib(prefix='/usr/local') it
I have tested the following versions:
Xenial: amd64 4.17+dfsg-1ubuntu0.1
Bionic: amd64 4.19.7+dfsg-1ubuntu0.1
Both distributions are now fixed.
For reference, my CI setup:
Xenial fixed:
https://travis-ci.com/github/MatthijsBurgh/orocos_kinematics_dynamics/jobs/308050115
Bionic fixed:
Hi Dmitry,
I have tested the updated Xenial package. Still works!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861601
Title:
Memory leak and incorrect behaviour of generated bindings
To manage
Hi Dmitry,
Please check the attached patch compared to the 4.17 tag. This should
provide the solution for 16.04. The diff is in the original mercurial
sip repo, https://www.riverbankcomputing.com/hg/sip. But is should be
applicable to the git repo.
The previous patch missed 2 lines. Therefore
Hi Dmitry,
Also the provided test package for 18.04 does fix the problems for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861601
Title:
Memory leak and incorrect behaviour of generated
Hi Dmitry,
Please check the attached patch compared to the 4.17 tag. This should
provide the solution for 16.04. The diff is in the original mercurial
sip repo, https://www.riverbankcomputing.com/hg/sip. But is should be
applicable to the git repo.
** Attachment added: "sip_patch2.txt"
Public bug reported:
Happening on all release of sip from 4.16.8 until 4.19.20, so Xenial and
newer are all affected.
I have tested this on both Xenial(sip 4.17) and Bionic(4.19.7).
My request is to update all affected releases to 4.19.21.
[Impact]
Since the release of sip 4.16.8, but
Just finished the upgrade without problems, so just disabling the
default-release temporarily seems to be sufficient. Would be nicer if
the upgrade somehow handled this, even if just detecting that it was set
and bailing out before rather than during the upgrade and allow the user
to unset it
This is still an issue: Just started the disco -> eoan upgrade through
the GUI prompt I got, which broke on, I think, the second step (setting
up software sources IIRC). A systray icon showed up saying there was a
problem with the package manager (saying 'disco', which I have now
configured as the
I'm also running into this bug (or at least something that looks like
it). Typically what happens for me is that I resume from suspend, get an
unlock prompt (the system is locked on suspend) and when I log in, the
unlock prompt stays visible (the password dots disappear, but I cannot
type anything
Public bug reported:
I just tried to upgrade my Ubuntu system from cosmic to disco, but it
seems the presence of the Default-Release configuration value breaks the
upgrade.
I have some Debian sources in my sources.list so I can occasionally
cherry-pick packages from there. To make sure these are
After this error, removing the Default-Release config and starting
`update-manager -c` again shows a popup "Failed to load the package
list". Clicking "ok" shows a spinner that takes some time and then
offers a partial upgrade, which looks reasonable (but has not finished
yet).
--
You received
Public bug reported:
I'm trying to upgrade from 18.10 to 19.04 by running `update-manager -c`
as instructed by https://wiki.ubuntu.com/DiscoDingo/ReleaseNotes. After
running it earlier to install pending package updates, I now get a
message saying there is a distribution upgrade available (see
Seems upstream diagnosed and fixed this bug in their master branch two
weeks ago, and the fix indeed got included in 3.32 (first in 3.31.92,
though it seems to have been omitted from their changelog/NEWS file).
Any chance of getting this fix backported into the Ubuntu cosmic
package?
--
You
Public bug reported:
Since version 2017.7ubuntu1, the keys installed by the Ubuntu version of
debian-archive-keyring are no longer trusted by default. Coming from
Debian, this surprised me, but now I've found the changelog entry, I
understand the reasoning.
Initially, though, I had expected
AFAICS this is fixed in 2017.7.ubuntu1:
debian-archive-keyring (2017.7ubuntu1) bionic; urgency=medium
* Do not trust debian archive keys by default, and instead ship those
keys in usr/share/keyrings. On Ubuntu, this package is mostly used for
validating chroots when debootstrapping
I tried to deinstall liggs9 and install libgs9-common as was suggested
by Synaptic. I got these errors:
(Database wordt ingelezen ... 438138 bestanden en mappen momenteel
geïnstalleerd.)
Uitpakken van .../libgs9-common_9.25~dfsg+1-0ubuntu0.18.04.2_all.deb wordt
voorbereid...
Public bug reported:
A week ago I had a problem with viewing EPS-files. (Now again). I posted the
following bug-description:
https://tex.stackexchange.com/questions/457182/problems-after-installing-ubuntu-18-04-and-eps
I tried to reinstall libgs9, without result. There are especially problems
Good call, thanks!
This turns out to be fixed in the latest mainline kernel. Looking at the
git log for the i2c_hid driver, I found this commit which I suspect is
the fix for my problem.
https://github.com/torvalds/linux/commit/52cf93e63ee672a92f349edc6ddad86ec8808fd8
It seems this fix also fixes the touch screen not working (no irq storm)
after a suspend on an Acer Aspire Switch 11 (and possibly also other
modules).
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796580
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I also ran the i2c_hid module with debug enabled (`modprobe i2c_hid
debug=1`), which gives a bit of insight in what commands are sent to the
touch screen. On a suspend, it seems to send a sleep command. On a
resume, it sends a power on command, followed by a reset command (which
is properly
I dug around a bit, and found that the touchscreen can also be fixed by
reloading the ic2_hid module.
It also works to reinitialize just the hid driver for the touchscreen
(rather than reloading the entire module) by running:
echo 0018:06CB:77B2.000C > /sys/bus/hid/drivers/hid-multitouch/unbind
** Description changed:
I'm not entirely sure this bug belongs in package xinput, but I'm
- following the lead of #1275416, which describes the same symptoms (but
- on other hardware, so likely a different underlying problem).
+ following the lead of
+
Public bug reported:
I'm not entirely sure this bug belongs in package xinput, but I'm
following the lead of #1275416, which describes the same symptoms (but
on other hardware, so likely a different underlying problem).
On this notebook, the touchscreen works well out of the box. But as soon
as
** Changed in: openttd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731637
Title:
New upstream Version
To manage notifications about this bug go to:
Have the exact same issue on 4.13.0-25-generic since today
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722745
Title:
Virtualbox service fails to start due to hanging plymouth --ping
response
I just uploaded 1.7.1-1 to Debian unstable, so this should migrate to
Ubuntu at some point.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731637
Title:
New upstream Version
To manage
W00ps, seems I (Debian maintainer) missed that release. I'll try to
upload a package to Debian somewhere this or the next month.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731637
Title:
New
Public bug reported:
I just tried installing the Artful version (0.10.3-1) on a Xenial
install, and had some problems making it work. It seems that I needed
`Defaults env_keep+=SSH_AUTH_SOCK` (or, actually, I used `Defaults
env_keep+=SSH_*`) to let pam-ssh-agent-auth see the SSH agent and
connect
Even with the script a shutdown/reboot takes a very long time. Any
expectations when a fix will be ready? I hit this all the time on 2
installed servers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Have you tried Nextcloud? Working flawlessly here on several machines.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572321
Title:
owncloud network access is disabled
To manage notifications
** Description changed:
After resuming from a suspend, almost all text on screen is not visible.
This includes menu items, text in all three boxes (list of folders, list
of e-mails, e-mail body) in Thunderbird (with the curious exception of
"ffl" in the File menu), top menu in Chromium
Is there any browser available on Ubuntu which does not have this issue?
I experienced this with Chrome and tried Firefox, only to find out it's
just as bad (FF 51.01 64bit on Ubuntu 16.04.2).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Rolf - thanks for mentioning iptraf-ng. It's working fine here on
Xenial 64 bit. IMHO in scenarios such as these where a 'mother' package
becomes obsolete and is replaced by an '-ng' version, the old package
should be shipping with a warning upon installation that it's deprecated
and should be
Correct, solved after upgrading again
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1627970
Title:
package smbclient 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to
install/upgrade: package smbclient is
Public bug reported:
matje@desktop:~$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
matje@desktop:~$ apt-cache policy smbclient
smbclient:
Installed: 2:4.3.9+dfsg-0ubuntu0.16.04.2
Candidate: 2:4.3.9+dfsg-0ubuntu0.16.04.3
Version table:
Never mind, the 'fix' is in line with the bug description.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558712
Title:
Remove morituri from archive or switch to gst1.0
To manage notifications
So removing a package from the 16.04 repo renders a status 'fix
released'? Sounds a little odd to me. Besides, the package from 15.10
(https://launchpad.net/ubuntu/wily/amd64/morituri/0.2.3-1) installs just
fine on 16.04.
--
You received this bug notification because you are a member of Ubuntu
I can confirm #9 as it just happened on my 16.04 system as well.
However, mine was a fresh install instead of an update from 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/1447099
Title:
Yup, problem seems to be solved now. Closing the bug.
** Changed in: network-manager-applet (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560896
+1 Working again with proposed package. And great tip, Diego / #19.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573639
Title:
ownCloud Client system tray icon integration broken
To
@Chris Cowan - thanks for pointing this out, added it to the
description.
** Summary changed:
- [16.04 beta] nm-applet does not show all connections
+ [16.04 beta] REGRESSION - nm-applet does not show all connections
** Description changed:
In version 1.0.10 of network-manager-gnome shipping
Public bug reported:
In version 1.0.10 of network-manager-gnome shipping with the 16.04 beta,
the nm-applet only shows limited info of the currently used network
connection, instead of all connections which are defined / available. As
such, it's impossible to switch connections manually,
Public bug reported:
error happened while upgrading from 14.10 to 15.04 using do-release-
upgrade
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: systemd 208-8ubuntu8.2 [modified:
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
ProcVersionSignature: Ubuntu
It seemed that by freak behaviour of systemd my /var/run shm partition
was 100% full.. the /var/run/systemd/sessions folder was 1.2Gb and
filled /var/run to 100%
after a reboot all was ok
Matthijs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
*** This bug is a duplicate of bug 1368094 ***
https://bugs.launchpad.net/bugs/1368094
+1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1341628
Title:
[needs-packaging]openjdk-8 in 14.04
To
I concur with Armindo, this is a bug (in the installer?) which has been
around for many, many years. Apparently the system fails to do a proper
locale-gen at the end of the installation.
When installing Ubuntu, I always choose US English as language, time
zone The Netherlands, keyboard layout US
Similar observation at my end: It works through pulse to my intel_hda
sound card, but fails through pulse to my Terratec Aureon 5.1MKII USB
audio device. Perhaps a bug in the USB audio driver?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can reproduce this on a Debian Jessie system. Bypassing pulseaudio
makes playback work normally:
pasuspender -- timidity up_on_the_housetop.mid -o hw:0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
An ignore should probably be added for Arduino.org devices too (there's
two competing Arduino companies now, don't ask):
ATTRS{idVendor}==2a03, ENV{ID_MM_DEVICE_IGNORE}=1
And, while we are here, perhaps also ignore the Pinoccio Scout (arduino-
like device):
ATTRS{idVendor}==1d50,
So, any updates on this issue now that it has become clear it can be
severely abused?
See:
https://www.blackhat.com/docs/eu-14/materials/eu-14-Selvi-Bypassing-HTTP-Strict-Transport-Security-wp.pdf
At least crank up the importance a bit...
--
You received this bug notification because you are a
So, any updates on this issue now that it has become clear it can be
severely abused?
See:
https://www.blackhat.com/docs/eu-14/materials/eu-14-Selvi-Bypassing-HTTP-Strict-Transport-Security-wp.pdf
At least crank up the importance a bit...
--
You received this bug notification because you are a
This was fixed upstream, by allowing opening the shield on any printable
character keypress, and entering that character into the password field,
so you can just type your password while the shield is still shown /
moving away.
https://bugzilla.gnome.org/show_bug.cgi?id=686740
According to git,
The changes to the freshclam AppArmor profile does do the trick.
Now freshclam reports (as it should be);
Clamd successfully notified about the update.
Thanks for the quick fix,
Matthijs
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
The changes to the freshclam AppArmor profile does do the trick.
Now freshclam reports (as it should be);
Clamd successfully notified about the update.
Thanks for the quick fix,
Matthijs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Not sure if this is a bug, or by design (but I would like some
clarification)
I recently upgraded my Ubuntu server to 14.04 LTS and notice some error
messages regarding Apparmor and Freshclam.
So far I know I didn't had these error message with the previous version
Public bug reported:
Not sure if this is a bug, or by design (but I would like some
clarification)
I recently upgraded my Ubuntu server to 14.04 LTS and notice some error
messages regarding Apparmor and Freshclam.
So far I know I didn't had these error message with the previous version
Public bug reported:
Using the daily 64 bit image from Feb. 27, 2014, I tried installing
Ubuntu today from a USB stick to the secondary partition of my laptop's
SSD.
Since I needed to install it to the secondary partition, I chose 'custom
install'. I selected sda2 as the root partition, chose
Public bug reported:
My secondary attempt to install Ubuntu Trusty, after the failed first
attempt (see bug #1286077) results in the same crash.
This time, I did everything the same way, but did not select 'Download
updates while installing' and 'Download 3rd party software'. So I guess
that
I can confirm this problem and wonder if there is any 'real' solution ?
After upgrading to 13.10 there was no problem, until log rotate.
Previous files had 644 for root:adm, now 640 for root:adm
The cron-job for awstats runs as www-data as mention above.
This cause error message when job runs:
Problem seems a change in new dist logrotate for Apache2
(/etc/logrotate.d/apache2):
I change this line:
create 640 root adm
Into:
create 644 root adm
As this was the default in my previous version of
/etc/logrotate.d/apache2
--
You received this bug notification because you are a member of
I can confirm this problem and wonder if there is any 'real' solution ?
After upgrading to 13.10 there was no problem, until log rotate.
Previous files had 644 for root:adm, now 640 for root:adm
The cron-job for awstats runs as www-data as mention above.
This cause error message when job runs:
Problem seems a change in new dist logrotate for Apache2
(/etc/logrotate.d/apache2):
I change this line:
create 640 root adm
Into:
create 644 root adm
As this was the default in my previous version of
/etc/logrotate.d/apache2
--
You received this bug notification because you are a member of
In case any one else comes across this problem: I had exactly the same
symptoms and found out they were caused by xbindkeys that was started in
the background. Removing my .xbindkeysrc solved the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
So I understand this bug has been fixed upstream over 5 months ago. Now
how long will it take for this fix to trickle down into Precise?
Anything I can do to speed it up?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I asked the following as a question and was suggested to report it as a
bug, so here it goes:
I am using ubuntu touch on my galaxy nexus, together with the 'official'
samsung HDMI dock. However, when docked, the screen is not mirrored to
my hdmi display.
My research got me
I'm confused. I just got this error while trying to installing linux-
generic-lts-saucy on my 12.04.3 machine. The build for both nvidia-304
and nvidia-319 failed:
nvidia-304 304.88-0ubuntu0.0.3: nvidia-304 kernel module failed to build
nvidia-319 319.32-0ubuntu0.0.1: nvidia-319 kernel module
Screenshot 3 - Dash active
** Attachment added: Screenshot from 2013-10-13 09:01:47.png
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239299/+attachment/3876477/+files/Screenshot%20from%202013-10-13%2009%3A01%3A47.png
--
You received this bug notification because you are a member of
screenshot 4
** Attachment added: Screenshot from 2013-10-13 09:03:49.png
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239299/+attachment/3876478/+files/Screenshot%20from%202013-10-13%2009%3A03%3A49.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Screenshot 2
** Attachment added: Screenshot from 2013-10-13 09:01:31.png
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239299/+attachment/3876472/+files/Screenshot%20from%202013-10-13%2009%3A01%3A31.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
When running Saucy final beta from a USB stick, the Launcher, Dash and top menu
bar are covered with 'gradients'.
See the attached screenshots.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: unity 7.1.0+13.10.20130920-0ubuntu1
ProcVersionSignature: Ubuntu
Public bug reported:
When running saucy final beta from a USB stick (option Try Ubuntu before
installing), ubiquity does not show an interface when started. As a result,
Ubuntu cannot be installed.
- Double-clicking the icon on the desktop seems to produce no result (nothing
happens)
-
Given that raring has been released without 1.3.0, but that 1.3.0 has
been (automatically) imported into saucy, I think this bug can be
closed.
** Changed in: openttd (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Given the age of the original report, I'm not sure if it's still worth
investigating this. It's likely that this bug has been fixed already in
newer OpenTTD versions.
If the bug still occurs for you, please reopen this bug or leave a
comment.
** Changed in: openttd (Ubuntu)
Status: New =
** Changed in: nautilus (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170976
Title:
Desktop icons changed by user, display white border around
On 05/30/2013 12:17 PM, Stefan Skotte wrote:
What the heck ? I used the three finger move windows all the time - and
I dont really plan to have a touchscreen...
Jz... Get this feature back !
LIKE
--
Matthijs Lambooy
CrossmarX BV, Amsterdam
http://www.crossmarx.com
+31654771926
skype
1 - 100 of 514 matches
Mail list logo
