** Changed in: systemd (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891394
Title:
systemd breaks upgrade with useless error if /var is not owned by root
To
Even though that last output said a few different ways that it failed,
it appears it did install and is usable.
So, just the problem with failing to install when newer unrecognized
kernels are installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
BTW, the kernel I've been running through all this is the default ubuntu 20.04
version:
$ uname -a
Linux dancer.chaosreigns.com 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
With kernel 5.8.0 removed, it looks like I'm hitting a new bug:
$ sudo apt
Same error for 5.8.0-25-generic.
$ sudo apt remove linux-headers-5.9.1-050901-generic
linux-modules-5.9.1-050901-generic
[sudo] password for darxus:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
linux
Public bug reported:
$ sudo apt install virtualbox
[sudo] password for darxus:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
dkms libgsoap-2.8.91 libvncserver1 virtualbox-dkms virtualbox-qt
** Description changed:
I created this PPA: https://code.launchpad.net/~darxus/+archive/ubuntu
/linux-firmware-daily/
It contains a linux-firmware package. This package
Provides/Conflicts/Replaces amd64-microcode. Because the upstream
source for this package also contains
Public bug reported:
I created this PPA: https://code.launchpad.net/~darxus/+archive/ubuntu
/linux-firmware-daily/
It contains a linux-firmware package. This package
Provides/Conflicts/Replaces amd64-microcode. Because the upstream
source for this package also contains the contents
Upstream bug, which would fix this: https://github.com/lm-sensors/lm-
sensors/issues/227
** Bug watch added: github.com/lm-sensors/lm-sensors/issues #227
https://github.com/lm-sensors/lm-sensors/issues/227
** Also affects: lmsensors via
https://github.com/lm-sensors/lm-sensors/issues/227
This problem still exists in ubuntu 20.04.
It looks like a good solution to this problem would be to use the
contents of /sys/class/hwmon/hwmon*/name instead of the hwmon device
number. fancontrol uses these name files to do the verification that
results in the errors in this bug report.
I used
Workarounds I have found are to switch to the cinnamon desktop, or the
(default ubuntu) gnome shell desktop with the dash to panel extension,
which has finally made me not hate gnome shell:
https://extensions.gnome.org/extension/1160/dash-to-panel/
Both of these have an extremely similar thing
Var was owned by the user I usually log in as. I don't know why, yes
it's weird, I fixed it. I don't think that justifies this package's
upgrade braking behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When I hover my mouse over it, on the panel, it doesn't show me how much
cpu / ram / etc. is being used, like it used to. Like the mate sensors
applet does.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: mate-system-monitor 1.24.0-1
ProcVersionSignature: Ubuntu
** Description changed:
I noticed last night that package install fails. Then I noticed
- processes running from an automatic upgrade that ran on September 9th.
+ processes running from an automatic upgrade that ran on September first.
Whenever I run "dpkg --configure -a", it gets stuck on
Public bug reported:
I noticed last night that package install fails. Then I noticed
processes running from an automatic upgrade that ran on September first.
Whenever I run "dpkg --configure -a", it gets stuck on blkid hanging.
When I run the same command manually through strace, it seems to get
** Attachment added: "Full output of that strace"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1895686/+attachment/5411074/+files/blkid.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think I had the same problem. I think it was fixed with "chown
root:root /var".
Related to this:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891394
I think it also caused screen to be unusable until it was run by root.
--
You received this bug notification because you are a
Public bug reported:
I just upgraded from 16.04 to 18.04. The upgrade broke. The error,
from systemd, was:
"Unsafe symlinks encountered in /var/log/journal, refusing."
That directory was empty. The fix was "chmod root:root /var". Yes,
it's weird that my /var wasn't owned by root, but
My fault, had ancient stuff in my install directory.
** Changed in: libgudev (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594003
Title:
undefined reference
Public bug reported:
//usr/lib/x86_64-linux-gnu/libgudev-1.0.so.0: undefined reference to
`g_type_class_adjust_private_offset'
Darxus: no, that means your system is broken really
Darxus: somehow you've ended up with your compiled gudev referencing
parts of glib which are no longer / not yet
I tried the steps for reproducing bug #1050610 - not the same bug. Wns
does go back down.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590136
Title:
gtk-window-decorator using 6.3gb resident
seems high too - Xorg, compiz, mate-session,
dbus-daemon)
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2081 darxus20 0 8392144 6.339g 18828 S 2.0 81.3 28:39.54
gtk-window-deco
It's from
I'm not certain I had the same problem, but the workaround I used was:
dpkg --force-depends -r purge libldap-2.4-2:amd64 libldap-2.4-2:i386
apt-get -f install
Because apt-get purge refuses due to dependencies.
--
You received this bug notification because you are a member of Ubuntu
Server
I'm not certain I had the same problem, but the workaround I used was:
dpkg --force-depends -r purge libldap-2.4-2:amd64 libldap-2.4-2:i386
apt-get -f install
Because apt-get purge refuses due to dependencies.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This bug is still present.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.2 LTS
Release:14.04
Codename: trusty
$ apt-cache policy xscreensaver
xscreensaver:
Installed: 5.15-3ubuntu1
...
--
You received this bug notification
Possibly relevant from the xscreensaver faq:
https://www.jwz.org/xscreensaver/faq.html#popup-windows
The window manager I'm using is metacity 1:2.34.13-0ubuntu4.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
Nice, that (debian) bug is 10 years old.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/565364
Title:
pinning a specific package does not work
To manage notifications about this bug go to:
To be a little clearer, the thing that was done wrong in the initial
report was here:
Select fan output to configure, or other action:
1) hwmon0/device/pwm3 3) Change INTERVAL 5) Save and quit
2) hwmon0/device/pwm2 4) Just quit 6) Show configuration
select (1-n): 5
Instead of hitting 5 to
To be a little clearer, the thing that was done wrong in the initial
report was here:
Select fan output to configure, or other action:
1) hwmon0/device/pwm3 3) Change INTERVAL 5) Save and quit
2) hwmon0/device/pwm2 4) Just quit 6) Show configuration
select (1-n): 5
Instead of hitting 5 to
I posted to the lm-sensors mailing list about it: http://lists.lm-
sensors.org/pipermail/lm-sensors/2015-January/043356.html
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/485899
I posted to the lm-sensors mailing list about it: http://lists.lm-
sensors.org/pipermail/lm-sensors/2015-January/043356.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/485899
Title:
pwmconfig
Ugh, the bug here is that this program is amazingly misleading, even
with step by step instructions. I went through the pwmconfig script
probably for hours trying to figure out how these values are supposed to
be set before I figured this out.
At the end, it says:
Do you want to set up its
Ugh, the bug here is that this program is amazingly misleading, even
with step by step instructions. I went through the pwmconfig script
probably for hours trying to figure out how these values are supposed to
be set before I figured this out.
At the end, it says:
Do you want to set up its
I also found it useful to give my fain 10 seconds between each speed
change, to get a more accurate reading:
$ diff pwmconfig.0 pwmconfig
64c64
DELAY=5 # 3 seconds delay is too short for large fans, thus I increased it to
5
---
DELAY=10 # 3 seconds delay is too short for large fans, thus I
I also found it useful to give my fain 10 seconds between each speed
change, to get a more accurate reading:
$ diff pwmconfig.0 pwmconfig
64c64
DELAY=5 # 3 seconds delay is too short for large fans, thus I increased it to
5
---
DELAY=10 # 3 seconds delay is too short for large fans, thus I
I tried a couple things that didn't work.
I'm running Precise.
I downloaded the tarball of the latest version of lm_sensors -
http://dl.lm-sensors.org/lm-sensors/releases/lm_sensors-3.3.5.tar.bz2
and ran pwmconfig directly from there (sudo bash prog/pwm/pwmconfig). No same
results.
Then I
I tried a couple things that didn't work.
I'm running Precise.
I downloaded the tarball of the latest version of lm_sensors -
http://dl.lm-sensors.org/lm-sensors/releases/lm_sensors-3.3.5.tar.bz2
and ran pwmconfig directly from there (sudo bash prog/pwm/pwmconfig). No same
results.
Then I
It would be even nicer if I could pick between mixing to mono, or
listening to only the right or left channel in both sides of my
headphones (sometimes one channel is garbage and the other is decent),.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
What was the cause / solution?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad.net/bugs/1346999
Title:
spamassassin 3.4.0 post installation script error ubuntu server 14.04
LTS
To
Nice. Maybe open a bug because it didn't throw a more useful error on
not being able to create /var/lib/spamassassin? I'm not sure if that
would be against aptitude or spamassassin.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
What was the cause / solution?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1346999
Title:
spamassassin 3.4.0 post installation script error ubuntu server 14.04
LTS
To manage notifications
Nice. Maybe open a bug because it didn't throw a more useful error on
not being able to create /var/lib/spamassassin? I'm not sure if that
would be against aptitude or spamassassin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
bluez package fails to install via apt-get, which prevents me from
installing ia32-libs, on precise. Running over ssh, not sure if that
could be relevant. I'm not interested in using the bluez package at
all, this is a server.
# apt-get install bluez
Reading package
This workaround seems to have worked:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1032915/comments/5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311368
Title:
Won't install on precise
I had a very similar looking problem, not under chroot, but running over
ssh, on a server. Is this expected to work in that situation? Bug
#1311368
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: ipv6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1260855
Title:
http://start.ubuntu.com/connectivity-check.html and other ubiquity
services are not accessible over IPv6 (no
Public bug reported:
I just succeed in building
http://sourceforge.net/projects/kxstitch/files/kxstitch/0.9.2/kxstitch-0.9.2-KDE4.tar.gz/download
after just installing these packages (and their dependencies) kdelibs-bin
kdelibs5-dev libmagick++-dev
on Precise. I imagine you'd want to package
How did 4 more people see and click this bug affects them in the 6 hours
since it was created? Are you all actually subscribed to new bugs
against the wayland package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Colin: Comment #167 says nothing about it defaulting to off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054776
Title:
Don't include remote searches in the home lens
To manage notifications
** Also affects: nvidia-drivers-ubuntu
Importance: Undecided
Status: New
** Bug watch added: www.eglibc.org/issues/ #23
http://www.eglibc.org/issues/issue23
** Also affects: eglibc via
http://www.eglibc.org/issues/issue23
Importance: Unknown
Status: Unknown
--
You
Yup, not much to add here, that is the reason for how things work. -
krh
Closing wontfix. Let us know if you have better, specific ideas.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058211
Why is this being discussed on ubuntu's bug tracker, instead of
wayland's, or the wayland mailing list. Or even the wayland IRC
channel. You're both often in there.
min2: Using scalable vector graphics just implies using a non-raster
graphics format. It does not require dealing with pointer
*** This bug is a duplicate of bug 1054776 ***
https://bugs.launchpad.net/bugs/1054776
unimatrix9: That's great, but it sounds like the default is still to
have Amazon ads enabled, which I am not okay with.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1054776 ***
https://bugs.launchpad.net/bugs/1054776
Vistaus: Again, I'm not interested in workarounds. I find the default
behavior offensive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks like this has been fixed upstream, in gtk:
Darxus gedit segfault under wayland was reportd to ubuntu, seb128 says
it's a wayland bug, segfault happened in wl_proxy_get_user_data:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1113424
jpetersen Darxus, should be fixed by
https
It's probably better to run weston-launch via dbus-launch (dbus-launch
install/bin/weston-launch) instead of the application.
And I think this only shows up when running weston outside of X (on
DRM), because when you run it under X, you already have dbus launched.
Also, I'm not convinced there
I'm not sure it make sense for this to be an ubuntu bug yet. I'm
guessing you're talking about communicating the keyboard layout from
gnome-control-center to weston. I think it would make more sense to
first discuss on the wayland list how that should even happen.
I believe the only way to set
If there's a relevant environment variable, it seems like it should be
pretty easy and reasonable to get weston to use it for the keymap, but I
still think this is a conversation that would be more appropriate on the
wayland mailing list.
--
You received this bug notification because you are a
Great, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
The libwayland0 MIR has been closed fix committed. So everything
should be ready to enable the wayland backend in the gtk package? Iain
/ Benjamin?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is the result of a packaging decision from about a year ago, in the
0.85 changelog:
* Build without setuid for weston; it's very young and experimental, so
let's be cautious.
I am curious when this is likely to change. I believe weston-launch
tries to handle permissions cleanly, and
Looks like Timo did the libxkbcommon v0.2.0 package. So next step is a
MIR for it? Benjamin?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage
Public bug reported:
libwayland is at v1.0.2: http://packages.ubuntu.com/raring/libwayland0
weston is at v0.95: http://packages.ubuntu.com/raring/weston
These won't work together. I believe the last API break was at v0.99.
(I have not actually tested this myself, but got verification that
I think that libxkbcommon0 description is out of date, probably written
before there was a release, when the package was built from a git repo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Not particularly, thanks :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
Iain, are you aware the mesa packages already depend on libwayland0?
Shouldn't that make it okay for gtk to depend on libwayland0?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable
Yay.
In case anybody else was trying to look up how libwayland0 ended up in main:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/810217
(MIR = Main Inclusion Request)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Somebody want to un-close this bug for raring? Won't let me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland backend
To manage notifications about this bug go to:
Iain, could you say what exactly the reasons are for not wanting the gtk
package to depend on a wayland package?
I posted about this problem here:
http://lists.freedesktop.org/archives/wayland-devel/2013-January/006888.html
A couple people have said what they think the reasons are in replies.
The GTK+ folks closed the above bug, to split the wayland backend into a
dynamically loadable library, wontfix saying No.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954352
Title:
Enable wayland
Fred: I think you misunderstand.
I don't think Iain is saying this can't be fixed. Somebody please
correct me if I'm wrong, but it sounds to me like the solution which
would make Iain happy, and not cause any problems for anybody else,
would be if GTK+ built its Wayland backend into a separate
Thanks. GTK+ bug opened:
https://bugzilla.gnome.org/show_bug.cgi?id=690381
** Bug watch added: GNOME Bug Tracker #690381
https://bugzilla.gnome.org/show_bug.cgi?id=690381
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
'What EFF Wants From Ubuntu ... Disable Include online search results by
default. '
-
https://www.eff.org/deeplinks/2012/10/privacy-ubuntu-1210-amazon-ads-and-data-leaks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
CSRedRat: Are you saying this bug has been fixed upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022424
Title:
Can pick wrong DRM device
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1054776 ***
https://bugs.launchpad.net/bugs/1054776
Piet: No, the problem is not that Software Center does not declare
packages (although I suppose that would also be worth adding). The
problem is that Ubuntu is displaying ads by default.
I see this got
This is a screenshot of what you get when you type something with no
local hits. I was trying to get to a package manager in a fresh install
of Quantal beta 2 yesterday, typed packages, and got this. A screen
full of 24 ads.
I did not click more suggestion. You get fewer ads if you actually
Public bug reported:
I'm so furious that I've been mentioning to people for years that I
prefer Ubuntu, and that they might, as a result, think that I condone
this
I just installed Quantal in a virtual machine, ran Unity just long
enough to switch back to the Gnome Classic UI. As I was
** Attachment added: Screenshot
https://bugs.launchpad.net/ubuntu/+source/unity-lens-shopping/+bug/1065720/+attachment/3395472/+files/unity.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Default behavior of Ubuntu's primary interface is to try to sell me thiings
+ Default behavior of Ubuntu's primary interface is to try to sell me things
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This was fixed upstream, as mentioned in the upstream bug this is linked
to. What might not be obvious from that bug is that you get the fix by
running sa-update, to get an updated set of rules, which you should be
doing daily from cron anyway. So there is nothing that needs to be done
to the
I didn't see your comment about updating the base package before my
comment / status change. I have no objection to you re-opening it for
that. Just seems like it would be pretty low priority. Are there
people running spamassassin without running sa-update? If so, why?
--
You received this
I keep lagging behind on comments just enough to be maximally annoying,
sorry.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad.net/bugs/1064541
Title:
rfc-ignorant.org will stop working
This was fixed upstream, as mentioned in the upstream bug this is linked
to. What might not be obvious from that bug is that you get the fix by
running sa-update, to get an updated set of rules, which you should be
doing daily from cron anyway. So there is nothing that needs to be done
to the
I didn't see your comment about updating the base package before my
comment / status change. I have no objection to you re-opening it for
that. Just seems like it would be pretty low priority. Are there
people running spamassassin without running sa-update? If so, why?
--
You received this
I keep lagging behind on comments just enough to be maximally annoying,
sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064541
Title:
rfc-ignorant.org will stop working soon
To manage
Woo, it made it into quantal: http://packages.ubuntu.com/quantal
/sensors-applet
If anybody else was curious what happens after something gets uploaded to
New:
https://launchpad.net/ubuntu/quantal/+queue
https://wiki.ubuntu.com/ArchiveAdministration
Norbert: Must is some pretty strong
The ubuntu-desktop package in quantal now has a dependency on libpam-
xdg-support, so everyone will get this by default.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894391
Title:
[FFe, MIR]
My interest in this bug is resolved with ubuntu-desktop now having a
dependency on libpam-xdg-support.
Is there any real chance anybody here is going to do anything on what
the summary was changed to, the lack of fallback if $XDG_RUNTIME_DIR is
not set, especially now that it will be set by
It's been a few days, and this package still doesn't appear to be in the
archives. What needs to be done?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1049343
Title:
FFe: Un-blacklist and merge
Imported from Debian for Quantal:
http://packages.ubuntu.com/quantal/libgtk3-perl
** Changed in: 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/969646
Thanks Fabrice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1049343
Title:
FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from
Debian testing (main)
To manage notifications
weston --help and --version both work with the latest weston commit:
1428b8ccf749233908436b4b480ceca5eafd18e7
** Changed in: weston (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ubuntu Sponsors? Anybody (with a Quantal key) out there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1049343
Title:
FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from
Debian
Fabrice, thanks.
Changed version to 3.0.0-0.2ubuntu1 (that's what you meant, right?)
Ran update-maintainer, which changed the maintainer to Ubuntu Developers.
Debdiff attached.
** Patch added: debdiff
Daniel: I have done nothing with locales at any point in this process.
Is it an upstream problem?
I'm not even sure how locales are relevant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1049343
Daniel: Do you have any reason to believe this locale issue is not an
upstream problem?
It seems likely that it is upstream. And 39 days after feature freeze,
17 days before release, seems like a really bad time to worry about it
here.
--
You received this bug notification because you are a
I don't suppose anybody has any idea if a diff is actually currently
required from Debian's version? The patches in the last Ubuntu package,
for Natty, look pretty minor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Created a ppa, without the previous differences applied:
https://launchpad.net/~darxus/+archive/sensors-applet/
List of all the commands I executed to do it are in the description.
Daniel, looks like the changes you're talking about are:
1) Add build-depends (in debian/control):
nvidia
There's also this, in sensors-applet/Makefile.am:
-LIBS = $(GLIB_LIBS) $(GTK_LIBS) $(GNOME_LIBS) $(CAIRO_LIBS) $(LIBNOTIFY_LIBS)
+LIBS = -ldl $(GLIB_LIBS) $(GTK_LIBS) $(GNOME_LIBS) $(CAIRO_LIBS)
$(LIBNOTIFY_LIBS)
Not sure how / if that's related. But looking over a debdiff from
No, I meant v2.2.7-2, because that's what the latest released ubuntu
package I see is based on. But that's closer than 3.0.0-0, thanks.
The -ldl was not a delta from Debian. There are a few other chunks that
are, I believe, just changes in the location of line breaks in pop-up
messages. I'm
Debdiff attached. Contains, I believe, all the differences from Debian
in the last package, minus some whitespace changes in pop-ups. Not
tested. Uploaded to PPA, still building:
https://launchpad.net/~darxus/+archive/sensors-applet/
** Patch added: debdiff
https://bugs.launchpad.net
1 - 100 of 608 matches
Mail list logo
