I have this problem in Xubuntu 16.04 with HWE kernel, on my Thinkpad X1
carbon 4th gen (2016).
uname -a:
Linux Godel 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
lspci | grep -i network:
04:00.0 Network controller: Intel Corporation Wireles
Sorry, I forgot to mention above that I selected both "download updates
while installing Ubuntu" and "download third party software for graphics
and Wi-Fi hardware, Flash, Mp3 and other media."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
This is an infuriating bug, but I've found a workaround, more or less
described in a comment in a duplicate bug here:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1547286/comments/11
I'm installing Xubuntu 16.04 amd64 on a completely blank SSD on a brand
new UEFI-enabled HP system. If
"there is plenty of similar reports around and forums discussions about
that."
Why not post them here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/562005
Title:
Backlight controls of laptops with
What version is no longer supported? Really? We need to open up a new
bug report for a bug that's 5 years old and counting? This has never
been fixed, and likely never will be by nvidia. I'm currently on the
last supported version, 340.76, in Xubuntu 14.04. Still doesn't work.
But we *should* keep
@dino99
This is not fixed with nvidia-340. I have Xubuntu 14.04 with nvidia-340
and nvidia-304-uvm installed from the xorg-edgers PPA. It seems nvidia-
libopencl1-340 depends on nvidia-340-uvm. I just installed the 3.19.3
vivid kernel from here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19
Just thought I'd mention that this problem does seem to have gone away
for me in trusty. Not sure when that happened, but I'm glad it's
(apparently) fixed. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
I would say release the package as an update, close bug 1307251, and
then see if anyone continues to complain about icon positions. My guess
is there will be fewer reports, and they'll be trickier to diagnose. It
probably deserves a new bug report.
I haven't had any other problems with 4.11.8 on t
Public bug reported:
Apport popped up a message that the nvidia driver installation failed
during today's kernel update on my Xubuntu 14.04 installation.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.113-0ubuntu0.0.4
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.1
Also, note that I have "Save session for future logins" disabled in the
log out dialog. Not sure if that should matter. I imagine it shouldn't.
Icon positions should always be saved between reboots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I just had icon positions reset on me on reboot, so it seems this bug is
not fixed after all in xfdesktop 4.11.8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307251
Title:
xfdesktop doesn't save
Also, note that I have "Save session for future logins" disabled in the
log out dialog. Not sure if that should matter. I imagine it shouldn't.
Icon positions should always be saved between reboots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I just had icon positions reset on me on reboot, so it seems bug 1307251
is not fixed after all in xfdesktop 4.11.8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365965
Title:
[MRE] Please update
This seems to work for me after updating to xfdesktop 4.11.8 in the
proposed update in bug 1365965
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315716
Title:
No confirmation prompt when force-dele
I'm trying out this 4.11.8 proposed release because I was affected by
bug 1307251 and bug 1315716. So far, both seem to have been fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365965
Title:
I just tried installing the proposed xfdesktop 4.11.8 package from bug
1365965, and so far, it seems to work. I'm not exactly sure what
triggered the icon rearrangement on reboot (it wasn't necessarily a
screen resolution change), so I'll report back if I have any further
problems.
--
You receive
I get this "Could not send object info" error from libmtp on seemingly
random files while copying a large number of files to a subfolder of
"Internal storage" on my Moto X running CyanogenMod 11 2014-11-28
(ghost), using Thunar in Xubuntu 14.04. On second glance, I think this
is due to the full pat
I'm seeing something similar, but noticeably different on my Thinkpad
W510 (Quadro FX 880M), Nvidia 331.38, Xubuntu 14.04 amd64. Maybe once a
week, while using the synaptics touchpad in firefox, the entire screen
turns a solid colour, either green or grey. Switcing virtual terminals
doesn't seem to
Never mind. The latest version in git does indeed work. met.no changed
their API from 1.1 to 1.2:
http://api.yr.no/weatherapi/locationforecastlts/1.2/documentation
1.2 was implemented in git in xfce4-weather-plugin this summer, and
met.no deprecated 1.1 about a week ago. My problem was that I was
Actually, from the timestamps of the cache files in
$HOME/.cache/xfce4/weather, it looks like the last successful data
retrieval was Oct 12.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244629
Title
@luca, not still, this is a new issue, started showing "No data" around
last weekend, maybe October 11, 2014 . This is on Xubuntu 14.04 amd64.
This bug report refers to an old old version of this issue. xfce4
-weather-plugin has been using met.no for its data for a while now. I
suppose something's
Just to clarify, it seems the "hard resetting link" and "SError: {
CommWake DevExch }" errors I was seeing had to do with me
connecting/disconnecting an external bus-powered portable eSATA drive
(ata6) that sometimes isn't correctly detected for some reason. The
sudden, random remounting of my main
I seem to be having the same problem with a Microsoft Sculpt Mobile
Mouse I just bought.
http://www.microsoft.com/hardware/en-ca/p/sculpt-mobile-mouse
This is in Xubuntu 14.04 amd64 on a Thinkpad W510. In the xfce "Mouse
and Touchpad" settings I get two entries for "Microsoft Microsoft (R)
Nano T
I'm getting these errors in Xubuntu 14.04 amd64 with nvidia binaries on
a Lenovo Thinkpad W510. I only noticed them because several times over
the past couple of months since installing Xubuntu 14.04, the machine
has suddenly, and quite randomly, remounted the filesystem to read only.
When that hap
I was getting the same error message while installing skype on Xubuntu
14.04 amd64. sni-qt:i386 wouldn't install as a result. Jean-Pierre's
solution worked for me (although I renamed sni-qt.conf instead of
deleting it outright).
--
You received this bug notification because you are a member of Ub
Damian, you probably shouldn't go marking the original bug #1303736
(marked resolved) as a duplicate of this one. The whole point of
starting this bug was to differentiate it from the previous one, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** This bug is no longer a duplicate of bug 1357090
Black screen on resume Xubuntu 14.04.1 #1303736 NOT fixed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303736
Title:
[SRU] Black screen after
As Elfy said, this may be becoming a catch-all bug for similar problems.
But, since I don't know where else to report this, and since it seems
similar enough:
I was having the original black screen problem with the default light-
locker installed. After the updates rolled out and after toggling th
Is this perhaps a duplicate of bug #1347272 (Several XFCE applications
appear unresponsive after communicating with a daemon)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222356
Title:
** (apport
Should bug #1222356 (** (apport-gtk:3020): WARNING **: Couldn't register
with accessibility bus: Did not receive a reply.) perhaps be marked as a
duplicate?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I've had this problem for years. Currently, I'm using Xubuntu 14.04 with
my panel located at the bottom edge of the screen. I see this most often
with nm-applet, skype, and sometimes the sound applet. Really annoying!
Thanks Lannoxx for opening a bug at GTK+'s bugzilla, and submitting the
patch.
-
@ Alistair,
I don't explicitly have Unity installed (I'm on Xubuntu 14.04), but a
search via synaptic shows that I do have these Unity-related packages
installed, possibly as dependencies for some piece of software I was
compiling:
gir1.2-unity-5.0 7.1.4+14.04.20140210-0ubuntu1
libunity-proto
It seems to me that bug #1254881 (
xfce session starts multiple instances of xfce4-power-manager and
xfce4-volumed) is another duplicate, so I've marked it as such. I might be
wrong though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
*** This bug is a duplicate of bug 1347272 ***
https://bugs.launchpad.net/bugs/1347272
** This bug has been marked a duplicate of bug 1347272
Several XFCE applications appear irresponsible after communicating with a
daemon
--
You received this bug notification because you are a member of
@Jeffrey, I don't know for sure, but I'd say it's likely that two drives
from the same manufacturer using the same controller will at the very
least be both derived from the same firmware code base, and their
firmware will therefore likely have a lot of bugs (and features) in
common. Since your dri
@Jeffrey
AFAIK, the Crucial M500 uses the Marvell 88SS9187 controller, while the
M550 and MX100 both use the Marvell 88SS9189 controller, and therefore
probably share the same firmware (or maybe the MX100 firmware was forked
off of the M550 firmware):
"These new Crucial MX100 SSD series features
Thanks Alberto! OK, I've submitted a new bug report against dbus:
Bug #1347272 (DBus communication problems affecting multiple packages)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1193236
Title:
On the advice of AlbertoSalvia Novella , I've submitted a new bug report
against dbus with links to all the bugs (in my install of Xubuntu 14.04)
that I vaguely suspect are related to one another:
Bug #1347272 (DBus communication problems affecting multiple packages)
--
You received this bug not
On the advice of AlbertoSalvia Novella , I've submitted a new bug report
against dbus with links to all the bugs (in my install of Xubuntu 14.04)
that I vaguely suspect are related to one another:
Bug #1347272 (DBus communication problems affecting multiple packages)
--
You received this bug not
On the advice of AlbertoSalvia Novella , I've submitted a new bug report
against dbus with links to all the bugs (in my install of Xubuntu 14.04)
that I vaguely suspect are related to one another:
Bug #1347272 (DBus communication problems affecting multiple packages)
--
You received this bug not
On the advice of AlbertoSalvia Novella , I've submitted a new bug report
against dbus with links to all the bugs (in my install of Xubuntu 14.04)
that I vaguely suspect are related to one another:
Bug #1347272 (DBus communication problems affecting multiple packages)
--
You received this bug not
Public bug reported:
I seem to be hitting transient DBus communication problems after a fresh
install of Xubuntu 14.04 amd64 on my Thinkpad W510 with the latest
nvidia binaries from the Ubuntu repos. Here are the related bugs.
Sometimes rebooting fixes things for a while. If I understand correctly
By the way, I find this is a transient issue. It went away after a
reboot, but perhaps it'll come back after enough suspend/resume cycles,
or on some subsequent reboot. Again, smells like a race condition.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
*** This bug is a duplicate of bug 976638 ***
https://bugs.launchpad.net/bugs/976638
** This bug has been marked a duplicate of bug 976638
pkexec does not find any authentication agent
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
The slowness in that bug may simply be some kind of timeout being hit
due to a dbus connection problem. After the timeout, maybe it retries
and succeeds, or tries some other method.
I also have unsubstantiated hunches that:
Bug #976638 (pkexec does not find any authentication agent)
and
Bug #1193
The slowness in that bug may simply be some kind of timeout being hit
due to a dbus connection problem. After the timeout, maybe it retries
and succeeds, or tries some other method.
I also have unsubstantiated hunches that:
Bug #976638 (pkexec does not find any authentication agent)
and
Bug #1193
I still get this error in Xubuntu 14.04 when I run "sudo gnome-disks",
and possibly other commands that I can't recall at the moment:
$ sudo gnome-disks
[sudo] password for mspacek:
** (gnome-disks:474): WARNING **: Couldn't connect to accessibility bus:
Failed to connect to socket /tmp/dbus-xW
I have an unsubstantiated hunch that Bug #1314782 (multimedia keys don't
work when xfce4-volumed is run in daemon mode) is related. Something to
do with a dbus race condition.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
The slowness in that bug may simply be some kind of timeout being hit
due to a dbus connection problem. After the timeout, maybe it retries
and succeeds, or tries some other method.
I also have an unsubstantiated hunch that Bug #976638 (pkexec does not
find any authentication agent) is also affect
*** This bug is a duplicate of bug 976638 ***
https://bugs.launchpad.net/bugs/976638
** This bug is no longer a duplicate of bug 1068988
Synaptic runs without administrative privileges when run from the launcher
** This bug has been marked a duplicate of bug 976638
pkexec does not find a
*** This bug is a duplicate of bug 976638 ***
https://bugs.launchpad.net/bugs/976638
** This bug has been marked a duplicate of bug 976638
pkexec does not find any authentication agent
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I'm seeing the same thing in Xubuntu 14.04: pkexec works in text mode,
but not GUI mode. If I run it with the --disable-internal-agent flag, it
raises "Error executing command as another user: No authentication agent
found." polkitd is running, as is polkit-gnome-authentication-agent-1.
This is a
*** This bug is a duplicate of bug 1068988 ***
https://bugs.launchpad.net/bugs/1068988
** This bug has been marked a duplicate of bug 1068988
Synaptic runs without administrative privileges when run from the launcher
--
You received this bug notification because you are a member of Ubuntu
In Xubuntu 14.04, I found I had to replace the exec line in my
synaptic.desktop file from "synaptic-pkexec" to "gksu synaptic". Not
sure if it's related, but I seem to be having lots of DBus-related
issues in Xubuntu 14.04. Argh.
--
You received this bug notification because you are a member of U
** Also affects: libxkbcommon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224732
Title:
Custom & default keyboard shortcuts don't work
To man
"Martin, the bug as described in the bug description is not random and
does not affect default shortcuts."
Then perhaps the bug description should be ammended, given the slightly
wider set of reports here from a variety of people. See my comment above
on race conditions. Just because the original
"Notice that I reported this bug against Unity/GNOME 3 not against
Xfce4. Unless you can prove that the bugs are coming from the same
/common/ code (shared by both projects), it would be nicer if you
reported a new bug against Xfce4."
@Edwin, yes, I noticed. You filed this bug against gnome-contro
FYI, suspending and resuming didn't fix the issue for me, but logging
out and back in did.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224732
Title:
Custom & default keyboard shortcuts don't work
Colin, #17 and #22 imply that default shortcuts also did not work, at
least at some point. Since no one here seems to know exactly where this
bug is occurring, and since it seems to be random (and therefore perhpas
a race condition), it's not much of a stretch to assume that the same
bug manifests
Nuts. xfce4-keyboard-settings isn't registered in launchpad for some
reason, so I can't add it as an affected package. I've added libxfce4ui
instead, although it needs to have a bug opened for it upstream for
anyone to be notified. I couldn't find any relevant existing ones here:
https://bugzilla.
** Also affects: libxfce4ui
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/1224732
Title:
Custom & default keyboard shortcuts don't work
To manage notific
I just hit this issue for the first time after a fresh install of
Xubuntu 14.04 amd64 on a Thinkpad W510 with nvidia binaries about a week
ago. At the moment, none of the shortcuts in
Settings->Keyboard->Application Shortcuts work, including the few that I
left at their defaults. This is after a su
I have this issue for both xfce4-appfinder and xfrun4 on a fresh install
of Xubuntu 14.04 amd64 on a Thinkpad W510 with nvidia binaries. Running
them with --disable-server makes start times instantaneous. Otherwise,
there's an unbearable 10-20 sec delay, and sometimes multiple zombie
instances runn
Bug #1048805 is also related (xfce4-appfinder launches very slowly).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314782
Title:
multimedia keys don't work when xfce4-volumed is run in daemon mode
@Allard, OK, that's good to know that a message shows up in dmseg saying
the queued trim is disabled. I don't have that message for my MX100, so
it seems trim isn't disabled in the kernel for the MX100:
$ dmesg | grep ata1
[1.995490] ata1: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf262710
Note that Darko's Bug #1254881 (xfce session starts multiple instances
of xfce4-power-manager and xfce4-volumed) is useful, while Bug #1314782
(multimedia keys don't work when xfce4-volumed is run in daemon mode)
might be the ultimate fix for all of this, assuming that patch can be
applied to more
Oops. That should've been "hitting Ctrl+Alt+Del to lock the screen, *OR*
attempting to log back out again".
By the way, the workspace applet labels are incorrectly displayed only
once in a while on login, maybe a 50% probability.
--
You received this bug notification because you are a member of
I think I've noticed the same in Xubuntu 14.04 amd64. Immediately after
login, hitting Ctrl+Alt+Del to lock the screen, and attempting to log
back out again, doesn't do anything until after about a 10 sec delay. I
think killing xfsettingsd and running "xfsettingsd --no-daemon &"
instead might fix i
I was suffering from multiple processes of both xfce4-power-manager and
xfce4-volumed as well. Thanks Darko for the workaround in the bug
description. However, that wasn't enough to make my volume controls work
reliably. Note that Bug #1314782 is very related. The workaround posted
there (add --no-
Hallelujah! Thanks for the workaround Alistair. I was going somewhat
crazy, finding that rather randomly, volume keys and notifications and
screen brightness notifications would work, sometimes only one would
work, and sometimes neither would work. That smells like some kind of a
race condition. Th
@ochosi:
"it's actually not due to something that light-locker is doing. It's due
to the VT switch that happens when locking. "
Um, isn't it light-locker that's executing the VT switch? Doesn't that
make light-locker responsible for all the downsides that come with VT
switching, including audio i
** Summary changed:
- Does not fail gracefully when lighdm isn't running
+ Does not fail gracefully when lightdm isn't running
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336065
Title:
Does not
Public bug reported:
I know this is, strangely, by design (http://xubuntu.org/news/screen-
locking-in-xubuntu-14-04/), but compared to gnome-screensaver or
xscreensaver, it's a regression as far as I'm concerned. I couldn't find
any placeholder bug for this. If there is one already, then please ma
I've seen the same thing regarding the "power manager is not running, do
you wish to run it now" message in Xubuntu 14.04 on my Thinkpad W510.
Clicking "run" does nothing. Trying to run xfce4-power-manager in
terminal didn't help either. If I recally correctly, the process
wouldn't show up in gnome
@njj: I'm not so sure. According to a post from hmh just a few minutes
ago on the above posted Crucial forum thread, the MX100 is not
blacklisted in the kernel. Also, when I run "fstrim -v /", I get a
response that bytes were trimmed. When I run it again, I get 0 bytes
trimmed (see #53). Is this ex
Note that there are reports on the Crucial forum that the Crucial M550
has the same problem, and therefore because it uses the same controller
(and firmware?), the MX100 does too:
http://forum.crucial.com/t5/Solid-State-Drives-SSD/M500-M5x0-QUEUED-
TRIM-data-corruption-alert-mostly-for-Linux/m-p/1
@penalvch,
Huh? I'm not currently having this problem. Just reporting that my
Crucial CT512MX100SSD1 currently doesn't seem to exhibit the problem,
and therefore should maybe be added to the whitelist.
If you still want me to file a separate bug report (to get more hardware
details?), please let
I've installed Xubuntu 14.04 on a brand new Crucial MX100 SSD
(CT512MX100SSD1, original MU01 firmware, no newer firmware available) on
a Thinkpad W510, and saw the note in the cron.weekly/fstrim file. After
running fstrim manually the first two times, I got this:
$ sudo fstrim -v /
/: 498557419520
** Summary changed:
- htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad
entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412,
rec_len=45654, name_len=39
+ fstrim corrpution on some SSDs
** Summary changed:
- fstrim corrpution on some SSDs
+ fstrim corr
For my future reference, and possibly others:
After installing Xubuntu 14.04 on my Thinkpad W510, generating
/etc/X11/xorg.conf with nvidia-settings and adding the
EnableBrightnessControl line to the Devices section and rebooting did
not work (it worked in Xubuntu 12.10). Instead, I had to create
I just tried messing with nvidiabl for my Thinkpad W510, without
success. I've opened a bug report here:
https://github.com/guillaumezin/nvidiabl/issues/89
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Ingo Gerth, is this a new problem that occurs only in the more recent
nvidia blobs, or does it also occur with older ones (say 304)? If the
latter, since you have a Quadro 2000M, this bug should probably be
marked as a duplicate of Bug #562005:
Backlight controls of laptops with NVIDIA NVS and Qua
seems to apply to all versions since 319
** Package changed: nvidia-settings-319-updates (Ubuntu) => nvidia-
settings (Ubuntu)
** Also affects: nvidia-drivers-ubuntu
Importance: Undecided
Status: New
** No longer affects: nvidia-drivers-ubuntu
** Also affects: gdk-pixbuf
Importance
*** This bug is a duplicate of bug 1214508 ***
https://bugs.launchpad.net/bugs/1214508
** This bug has been marked a duplicate of bug 1214508
nvidia-settings >=319 segfaults on close
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I just marked a few other bugs as duplicates of this. As I wrote in one
of them, I see this in nvidia-settings 331.20 on my Thinkpad W510
(Nvidia Quadro FX 880M) on Xubuntu 12.10, using the xorg-edgers PPA,
which brings in Linux 3.7.0.7-generic. I'm pretty sure I don't see this
on Xubuntu 13.10, wi
*** This bug is a duplicate of bug 1214508 ***
https://bugs.launchpad.net/bugs/1214508
I just marked this as a duplicate of Bug #1214508. Alberto Milone, could
you assign yourself to that bug?
** This bug has been marked a duplicate of bug 1214508
nvidia-settings >=319 segfaults on close
*** This bug is a duplicate of bug 1214508 ***
https://bugs.launchpad.net/bugs/1214508
** This bug is no longer a duplicate of bug 1211035
nvidia-settings crashes on exit
** This bug has been marked a duplicate of bug 1214508
nvidia-settings segfaults on close after official update of dr
** Summary changed:
- nvidia-settings segfaults on close after official update of drivers from 310
to 319
+ nvidia-settings >=319 segfaults on close
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1214
*** This bug is a duplicate of bug 1214508 ***
https://bugs.launchpad.net/bugs/1214508
Still seeing this in nvidia-settings version 331.20 from the xorg-edgers
PPA on Xubuntu 12.10. I updated the title to make it less version
specific.
** Summary changed:
- nvidia-settings-325 crashes on exi
** Changed in: xorg (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/1281019
Title:
10de:0dda [HP EliteBook 8560w] Brightness controls are not working
*** This bug is a duplicate of bug 1011073 ***
https://bugs.launchpad.net/bugs/1011073
David, I would hazard it's marked as low importance because fixing it
wouldn't be as sexy and controversial as, say, Ubuntu Edge, or Mir, or
Unity. It would, however, be damned well useful.
--
You received
Oops, never mind. I get the same crash whether I hit Quit or simply
close the window. Seems apport stopped bothering to report the crashes
after the first few times. Running nvidia-setttings from the command
line gives this on exit:
Illegal instruction (core dumped)Illegal instruction (core dumped
I have the same on my Thinkpad W510 (Nvidia Quadro FX 880M) on Xubuntu
12.10, using the xorg-edgers PPA, which brings in Linux 3.7.0.7-generic.
I installed nvidia-325 via synaptic. I get this in /var/log/syslog after
two crashes:
Sep 3 18:30:57 Escher kernel: [ 990.669702] traps: nvidia-settings
Note that hitting the close button doesn't cause a crash, just hitting
the Quit button. Other than the crash, both do the same thing.
** Summary changed:
- nvidia-settings-325 crash with pressing exit button
+ nvidia-settings-325 crashes on Quit button press
--
You received this bug notificatio
@mdeslaur, will Quantal get fixed too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1011073
Title:
NetworkManager submenus sometimes unpopulated
To manage notifications about this bug go to:
https
Xubuntu 12.10 updated to nvidia 304.88 a day or so ago, and now
brightness controls are even more uneven than before. I've tried
regenerating xorg.conf using nvidia-settings, and re-adding [Option
"RegistryDwords" "EnableBrightnessControl=1"] to the Device section, but
that hasn't helped. I also tr
*** This bug is a duplicate of bug 780602 ***
https://bugs.launchpad.net/bugs/780602
** This bug has been marked a duplicate of bug 780602
nm-applet leaks memory and stops functioning after a while
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Summary changed:
- nm-applet becomes unresponsive to interactions and submenus such as 'VPN
Connections' show completly empty
+ nm-applet becomes unresponsive to interactions and submenus such as 'VPN
Connections' show completely empty
** Changed in: oem-priority/quantal
Status: New =
@hadware, #27:
"Apparently this problem only appears after an upgrade.It seems I never
got this kind of problem with fresh installs, and people here appear to
be in the same situation..."
Not true. I have this bug, with the very same dbus-monitor reports as in
#8, on my fresh Xubuntu 12.10 instal
What's the status of this bug for quantal? Surely if there's a fix for
precise, there should be one for quantal, no? In Xubuntu 12.10, after a
day of running on WiFi, my submenus still show up as empty and the
network shows as disconnected, even though I'm still connected to the
same access point a
1 - 100 of 257 matches
Mail list logo
