Public bug reported:
Woud it please be possible to upgrade Protobuf to 3.19.1 (which is
already in Debian) for upcoming Ubuntu LTS 22.04 ?
All packages that use protobuf as dependency (which are quite some) will
need a rebuild, so it is important to organize a transition on time.
** Affects:
I am receiving a similar error with my Microsoft Surface bluetooth mouse
after upgrading to the latest kernel. You check the details in my
comment on the Kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=204765#c10
** Bug watch added: Linux Kernel Bug Tracker #204765
Even though this bug is marked as fixed, I don't have the impression it
is fixed. These fingerprint sensors are not connected via USB but via
I2C with the touchpad. I don't see any support for that in libfprint.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Here you are
** Attachment added: "lsusb.txt"
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1876502/+attachment/5366118/+files/lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Sebastien Bacher, I filed a new bug at
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1876502 using
ubuntu-bug libfprint-2-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641290
Title:
Public bug reported:
Elan fingerprint reader that is integrated in the touchpad of e.g. Asus
Vivobooks is not recognized. It uses i2c instead of USB.
This bug is filed as replacement bug for
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1641290
ProblemType: Bug
DistroRelease: Ubuntu
That latest Debian bug #953104 should be solved by now, and also 3.20.3
with an upstream fix is now released by HP and available in the Debian
repository (3.20.3+dfsg0-1)
I think it'd be great to have this latest version with more printer
support and bugfixes in the Focal-release, so that indeed
I experience the same issue. Problem is that even the most recent
libfprint does not support i2c devices yet (only USB)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641290
Title:
[04f3:0903] Elan
Can the patch that was applied to the kernel in
https://launchpad.net/ubuntu/+source/linux/5.2.0-8.9 please also be
applied to the daily mainline builds? (possible duplicate bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836373 )
--
You received this bug notification because you are
For those that use Atom, upcoming release should have the fix:
https://github.com/atom/atom/pull/18012
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790966
Title:
Electron apps segfault on glibc
I don't know if the BFD linker or gold would work.
Ofc the fix would be to rebuild all respective Electron apps, but I
doubt all (proprietary) apps will already have a new release by October.
The fix for Electron was only released end of August.
It is a very unexpected regression, because goal
I built my own patched version at https://launchpad.net/~maarten-
fonville/+archive/ubuntu/ppa/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790966
Title:
Electron apps segfault on glibc 2.28
Based on the patch of Arch Linux, to at least temporarily work around
the Electron ldd bug, because the large impact it has.
https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/glibc=f2c68876f6959c62ea09dcdda5d441bf4ff7
** Patch added:
Public bug reported:
Electron apps (like Atom) give a segfault when trying to start them on Ubuntu
Cosmic.
Apparently this is related to a certain commit that is part of glibc 2.28.
Could the workaround as e.g. Arch has implemented also be applied to
Ubuntu, otherwise many pre-compiled
Thanks for the hint, I use their snap-package as workaround, as hinted by their
developer:
https://community.spotify.com/t5/Desktop-Linux/libcurl4/m-p/4411011#M15902
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For spotify this trick doesn't work, it complains about the changed
CURLOPT_SSL_CTX_FUNCTION symbol when starting the application.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754294
Title:
After
Ok, Igor you are right about them being linked to libcurl.so.4 while
assuming abi-3; this is a very unpleasant situation that indeed cannot
even be resolved with adjusting the symlinks :-/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
If they were compiled against libcurl.so.4 I assume they would be compiled
against abi-4 of libcurl, right?
AFAIK the supplying of libcurl.so.4 by libcurl3 was a trick by Debian by
keeping the same exposed symbols, which kept abi-3 and abi-4 the same.
So I'd assume even though those packages
Yes, but, it are symlinks that could trivially be changed:
ls -al /usr/lib/x86_64-linux-gnu/libcurl.so.*
lrwxrwxrwx 1 root root 12 jan 25 10:19
/usr/lib/x86_64-linux-gnu/libcurl.so.3 -> libcurl.so.4
lrwxrwxrwx 1 root root 16 jan 25 10:19
/usr/lib/x86_64-linux-gnu/libcurl.so.4 ->
The reason they conflict, is that both bundle libcurl.so.3 and
libcurl.so.4, which are in fact just symlinks to the actual library.
The best would be to release a new version of libcurl3 that does NOT have a
libcurl.so.4 symlink, ONLY the libcurl.so.3 one.
And then provide a version of libcurl4
This also affects the installation of popular 3rd party application
Spotify: https://community.spotify.com/t5/Desktop-
Linux/libcurl4/m-p/4411011#M15902
I wonder, Debian still has libcurl3 versioned library/symbols in their
'unstable' repo, their libcurl4 is only in experimental yet. I
understand
to
automatically build your latest development efforts in an Ubuntu PPA:
https://launchpad.net/~maarten-fonville/+archive/ubuntu/rust/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676169
Title
I can add that rustc 1.17.0+dfsg2-1 from Debian experimental has this
issue resolved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676169
Title:
rustc (1.16.0+dfsg1-1~exp1ubuntu1) gives an error
It happens when compiling this project:
https://github.com/plietar/librespot
I tried with .cargo purged and such.
Also have tried with full updated dependencies. Always the same problem since
the new rustc.
The command that is executed by cargo is:
`rustc --crate-name serde_derive
The same applies to Debian upstream 1.16.0+dfsg1-1
** Also affects: rustc (Debian)
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/1676169
Title:
rustc
I have the same issue on Ubuntu 16.10 and 17.04, also with Intel
hardware and displayport. Nothing weird in dmesg though :-/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587749
Title:
random 1-2s
Public bug reported:
The 'calculator' hotkey on the keyboard does not start the gnome-calculator
anymore when upgrading to Ubuntu Zesty.
Even though the proper shortcut is still set for "Launch calculator" in the
system settings -> keyboard -> shortcuts it does not work in Unity anymore.
This
Public bug reported:
When updating yakkety to zesty, the upgrade of python3-xapian1.3 to
python3-xapian does not succeed; they have same files in the package and
apt-xapian-index keeps the dependency on python3-xapian1.3 in place
instead of automatically transitioning to python3-xapian.
This
An update: apparently it can be upgraded to zesty's version. But by
default apt and aptitude don't find the correct upgrade path, probably
because it concerns i386 on amd64.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
For steam (1:1.0.0.54+repack-2ubuntu5)
it depends on libtxc-dxtn-s2tc0:i386 but that version is not available in Zesty.
It also results in the situation, that if upgrading Ubuntu, the new
libtxc-dxtn-s2tc from Zesty is thus not installable together with steam,
because it
** Summary changed:
- cargo (0.17.0-0ubuntu1) gives an error when compiling with std
+ rustc (1.16.0+dfsg1-1~exp1ubuntu1) gives an error when compiling with std
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Apparently it is caused by the upgrade from rustc 1.15 to 1.16, not by
cargo
** Package changed: cargo (Ubuntu) => rustc (Ubuntu)
** Description changed:
In the older versions of rust/cargo, I did not have this issue, but
- since upgrading to cargo (0.17.0-0ubuntu1) I get this error for my
-
Public bug reported:
In the older versions of rust/cargo, I did not have this issue, but
since upgrading to cargo (0.17.0-0ubuntu1) I get this error for my
project:
error[E0523]: found two different crates with name `std` that are not
distinguished by differing `-C metadata`. This will result
I recently had the same issue with an accidental removal of the -extra
package.
There are NO safeguards in apt warning about potentially rendering your
system unusable if removed by accident.
And the linux-image package itself lacks many network drivers and
ESPECIALLY LACKS USB HID support!
I added the GNOME bugreport. Though I wonder if they would look into
bugs that are of the 3.20.x series :-/
** Bug watch added: GNOME Bug Tracker #773273
https://bugzilla.gnome.org/show_bug.cgi?id=773273
** Also affects: file-roller via
https://bugzilla.gnome.org/show_bug.cgi?id=773273
Public bug reported:
In Ubuntu Yakkety file-roller 3.22.0
If opening a first archive (e.g. a zip-file) file-roller opens this correctly.
This can be done using nautilus, xdg-open or directly passing the filename
argument to file-roller.
But if you already have one file-roller instance open,
Public bug reported:
Hi,
could you please enable python3 builds for the new protobuf3 version?
A patch for it is already floating around:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836821#10
I tested it in my PPA, just needed to add python3-six as an extra
explicit dependency (for some
I can confirm that the package in proposed fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571295
Title:
pptpd module config loaded at wrong location
To manage notifications about
** Also affects: shellcheck (Debian)
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/1564379
Title:
This package is outdated
To manage notifications about
@Rune there is an official icedtea-8-plugin package in the Xenial
repositories. It probably would be better to backport that version, than
to use mine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What is the status for this bug for upcoming Xenial? Is it resolved or
is the workaround still necessary?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510970
Title:
Intel driver crashes on Ubuntu
Public bug reported:
On Ubuntu Xenial, when update-initramfs is called, you get many lines
with:
libkmod: ERROR ../libkmod/libkmod-config.c:635 kmod_config_parse:
/etc/modprobe.d/pptpd.conf line 1: ignoring bad line starting with
'nf_nat_pptp'
** Affects: pptpd (Ubuntu)
Importance:
The workaround fix is: sudo mv /etc/modprobe.d/pptpd.conf /lib/modules-
load.d/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571295
Title:
pptpd module config loaded at wrong location
To manage
Even Google switches to OpenJDK 8 now for their Android builds
Can't believe that a package that is in "main" is so neglected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1385842
Title:
I also experience this problem, often it is triggered when using Chrome
and opening a new tab or window.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509846
Title:
lightdm crashes on window open
This problem is also applicable to Wily.
Why is the solution not applied in e.g. an Ubuntu-patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261192
Title:
Incorrect conditions in systemd and
*** This bug is a duplicate of bug 1440417 ***
https://bugs.launchpad.net/bugs/1440417
** This bug has been marked a duplicate of bug 1440417
Old package, please move to stable 5.2
** This bug is no longer a duplicate of bug 1440417
Old package, please move to stable 5.2
** This bug
The package in proposed does indeed resolve the problem! :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457369
Title:
kernel 3.19.0-18 breaks HDMI audio for snd_hda_intel
To manage
I tested(to be able to bisect the problem) the mainline kernels, and since
3.19.0-18.18 should be based on the 3.19.6 vanilla kernel, I tried the 3.19.6
(and higher) vanilla kernels, but none of them has this issue.
So the problem is in one of the ubuntu-specific changes. I don't have the time
apport information
** Tags added: apport-collected vivid
** Description changed:
Problem appears on multiple computers with exact same kernel update, so
clearly the problem is within the kernel. 3.19.0-16 did work without any
problems.
Before sound worked great via HDMI, now the HDMI
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1457369/+attachment/4401504/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457369
Title:
kernel
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1457369/+attachment/4401505/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457369
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1457369/+attachment/4401506/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457369
Title:
Apport does not succesfully submit itself, so I will attach manually an
apport-cli output
** Attachment added: apport.linux-image-3.19.0-18-generic.90e9i8sh.apport
apport information
** Attachment added: AlsaInfo.txt
https://bugs.launchpad.net/bugs/1457369/+attachment/4401503/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457369
Title:
Public bug reported:
Problem appears on multiple computers with exact same kernel update, so clearly
the problem is within the kernel. 3.19.0-16 did work without any problems.
Before sound worked great via HDMI, now the HDMI output is not visible in
neither alsamixer nor pulseaudio. Audio via
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1457369/+attachment/4401508/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457369
Title:
apport information
** Attachment added: JournalErrors.txt
https://bugs.launchpad.net/bugs/1457369/+attachment/4401507/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, to workaround the problem I had already installed the
4.0.4-040004-generic kernel (so not the very latest topline), and it
works without any trouble.
** Tags added: kernel-fixed-upstream-4.0.4
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug
For me the package in vivid-proposed works! :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448259
Title:
Systemd does not send SIGTERM first on shutdown
To manage notifications about this bug
I tested the packages, and bash history is now properly retained during
a reboot :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448259
Title:
Systemd does not send SIGTERM first on shutdown
To
A proper systemd configuration file could be done together with the
upstream Transmission project
** Bug watch added: Transmission Trac #5686
https://trac.transmissionbt.com/ticket/5686
** Also affects: transmission via
https://trac.transmissionbt.com/ticket/5686
Importance: Unknown
Hmm, what I had used 'succesfully' was apprently pure chance that it did
work that boot.
Apparently it is still the broken, and the cause has to be found within
the systemd I guess.
With the information of this bug: https://trac.transmissionbt.com/ticket/5421
Everything 'seems to be right' in
I now got a fix.
Problem is that the regular 'network' target in systemd does not define a per
se on-linen working internet connection. The trick is to change the systemd
configuration for transmission-daemon, open:
/etc/systemd/system/multi-user.target.wants/transmission-daemon.service
Under
In Ubuntu Vivid, this problem can't even by fixed by the original editing of
lines, a new start of the script has to be used.
I now succesfully use:
start on (starting network-interface
or starting network-manager
or starting networking)
--
You received this bug
Public bug reported:
In Ubuntu Vivid, using the 'reboot' command directly reboots the system in such
a way that the bash_history is not retained.
This bug has also been reported in Red Hat:
https://bugzilla.redhat.com/show_bug.cgi?id=1170765
There it was found that the cause of this bug is to
Since nothing is happening with this bug, I created my own icedtea
packages for openjdk8, based on the earlier mentioned repository and the
current ubuntu icedtea package.
They can be found here: https://launchpad.net/~maarten-
fonville/+archive/ubuntu/ppa
--
You received this bug notification
** Bug watch added: Debian Bug tracker #751173
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751173
** Also affects: icedtea-web (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751173
Importance: Unknown
Status: Unknown
--
You received this bug notification
But what is now the path to enable compatability with openjdk-8?
For the users using (or depending on) openjdk-8 we now don't have any icedtea
support :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Today icedtea-web was updated, making the intermediate icedtea-8-plugin and
icedtea-netx icedtea-netx-common packages from the temporary repository
(http://87.98.165.193/debian/repo/) out of date.
It would be really nice if at least vivid development could update the control
file for this
At the moment I cannot boot in a live environment on this machine, I
will try to do so later this week. Meanwhile I wonder if it might be
related to this bug (?):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397553
--
You received this bug notification because you are a member of Ubuntu
I see btw more people reporting problems with the Trusty stable kernel
update combined with their Radeon:
http://forum.kodi.tv/showthread.php?tid=174854page=225
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I did try to run apport-collect 1402172 with a stock (non mainline
kernel PPA) kernel, and did check out the wiki on how to resolve the
error by installing the launchpadlib package, but as I said earlier: the
package is (already) installed but I get the very same error nonetheless
:(
is the dmesg
Public bug reported:
When applying the updates on my Ubuntu Utopic installation I received the new
3.16.0-28 kernel.
The computer had no problems with the Utopic kernels before ( up to 3.16.0-26),
but now it suddenly won't give any output (via HDMI) when booting. I don't get
X, I don't get a
I cannot run the apport command locally, since I never get any terminal
window or console to run it.
** 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.
I am currently running a kernel PPA mainline, but I get:
ERROR: The python-launchpadlib package is not installed. This
functionality is not available.
even though this package is installed... :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thank you, indeed removing the local desktop file resolves the problem.
It is indeed a bit problematic how Unity handles this, because there is
no feedback, and the local desktop file was created I think, when I
added virt-manager to the unity panel. But the file is not removed when
the shortcut
No, I don't use any other menu editor, and I also don't have a locally build
virt-manager here (and also no other DE than Unity).
So it must have been created by something like virt-manager itself or Unity. Is
it maybe created through the systray settings of virt-manager?
--
You received this
Of course, here you are:
cat $HOME/.local/share/applications/virt-manager.desktop
[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Name=Virtual Machine Manager
Icon=virt-manager
Path=/home/maarten
Exec=python /usr/share/virt-manager/virt-manager.py
StartupNotify=false
Public bug reported:
OpenJDK 8 is available in the Utopic repositories, but icedtea-8-plugin does
not exist.
I did see that in Debian this 'bug' is known and the new control files etc are
already made available in this repository:
https://code.launchpad.net/~openjdk/openjdk/icedtea-web
Can the
Public bug reported:
When trying to start virt-manager from the Unity Menu or Unity Launcher, it
doesn't start. No feedback is given by the system, just nothing happens.
Starting virt-manager from the commandline gives no problems though.
This problem has appeared since the upgrade from Trusty
When will this be backported to trusty? It is a quite relevant and
important fix for those using the new radeon vdpau acceleration for
XBMC. I don't think many people would expect the source of their tearing
to be in libsdl1.2 and find this fix on their own.
--
You received this bug notification
When will this be backported to trusty? It is a quite relevant and
important fix for those using the new radeon vdpau acceleration for
XBMC. I don't think many people would expect the source of their tearing
to be in libsdl1.2 and find this fix on their own.
--
You received this bug notification
Public bug reported:
Libguestfs had broken java bindings, and in general the project is fixing a lot
of bugs and (security) issues in each of their new stable releases.
Debian is picking up these changes relatively quickly (in Debian Package
Trackign System is some activity almost every other
** Changed in: libguestfs (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157665
Title:
update-guestfs-appliance ligbuestfs-test-tool should be included in
I also was confronted with this bug. Please fix it, because it is for
users quite hard to figure out *what* is going wrong, and it takes a lot
of debugging time before arriving at the source of the problem
The fix is trivial and should therefor be (in my opinion) be applied as
soon as possible
I also have this problem, removing and re-adding my google account
doesn't fix it. Oleksandr's workaround helped for me.
The problem only appears for me if my Google account is set up.
I found on the internet that other people had problems with gnome-
online-accounts using 2-factor
@Mio, H.-Dirk Schmitt
Please test the latest version of libmtp and gvfs from Philips PPA.
https://launchpad.net/~langdalepl/+archive/gvfs-mtp
Also on my Galaxy S3 and Nexus 7 these (Natty packages) work great!
I would really suggest to get these packages to Natty-backports since
the amount of
@Myself #149, dumb me. Not Natty, but Quantal packages... :P don't know
what I was thinking...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903422
Title:
Ubuntu does not work with Samsung Galaxy
Today I tried do upgrade a machine from Precise to Quantal, and this bug
still appears. Shouldn't this updated package also be applied to Precise
to solve it properly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The new version is now also available in Debian:
http://packages.debian.org/sid/xserver-xorg-video-nvidia-legacy-173xx
Can Alberto Milone please also put this driver in the Ubuntu
repositories, so that Precise will finally become usable for those of us
with older hardware? nVidia did their bit,
@Till;
I used your package to be able to use my Samsung CLX-3815FN Network printer
(connected via Ethernet LAN) to be able to print again using IPP(14) with the
proprietary Samsung printing driver that was packaged by
http://www.bchemnet.com/suldr/
--
You received this bug notification
I've build for now a trivially changed xvba-va-driver package in my
repository at https://launchpad.net/~maarten-
fonville/+archive/ppa/+packages which has its dependencies changed to
also allow fglrx-updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Because of the wrong parsing Apache will give an error like:
NT_STATUS_OBJECT_NAME_INVALID opening remote file \\Foldername/Filename.txt
while the actual URL that should be retrieved is:
\\hostname\Sharename\TopFolder\Foldername\Filename.txt
The error can be resolved by
I am having this problem at my girlfriends' laptop in combination with
Google Chrome :S
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/698121
Title:
xf86OpenConsole: VT_WAITACTIVE failed:
Maybe that (re)setting the gconf keys can be included in the Unity
binary or session manager (where 'Unity 2D' is chosen) in some way?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/705035
Title:
I upgraded to this latest version.
The problem is partly fixed. Unity-2d-launcher seems to be starting correctly
at login. But the unity-2d-panel is still not appearing, and gnome-panel does
appear instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hmm, I just restarted and this time unity-2d-launcher did not come up.
So the situation as before report #20.
Can you tell me how I can clean maybe my unity settings in a way that I can
test an as-new Unity-2D installation?
(I have experience with gconf-editor and so, thus if you can just
That's a bit too radical for me. Since I have a lot of other specific
settings for lots of applications which would take a lot of time to copy
back. Most easy would be to delete the relevant files in the
userprofile.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I was able to fix my problem by making a kind of clean unity 2d session:
system-startup applications-options- removed the check for
'automatically remember applications when logging out'
removed everything from ~/.config/gnome-session/saved-session/
now unity 2d does start, and gnome-panel does
1 - 100 of 199 matches
Mail list logo
