I'm going to guess that there was some odd dependency thing going on,
because after the post-upgrade reboot:
# aptitude full-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states
Same thing for me on 3.10.4 on Mint 17 (more-or-less Ubuntu 14.04).
Started in 2008, I'm up to 2010 after 20-30 mins...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480446
Title:
Old notifications
Me too, me too!!! Added comment and subscribed too the new
bug, 3.10.4 on Mint 17 (more-or-less Ubuntu 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/848968
Title:
Google Calendar reminders
My use case is a Mint 17.x VM using a VirtualBox vboxsf to a Win8.1
host. I had this same problem in Geany and it was driving me insane
until I found
http://wiki.geany.org/config/all_you_never_wanted_to_know_about_file_saving
and then "Edit > Prefs > Various > use_atomic_file_saving: checked"
fixe
My use case is a Mint 17.x VM using a VirtualBox vboxsf to a Win8.1
host. I had this same problem in Geany and it was driving me insane
until I found
http://wiki.geany.org/config/all_you_never_wanted_to_know_about_file_saving
and then "Edit > Prefs > Various > use_atomic_file_saving: checked"
fixe
2015 and still not fixed... Not too good.
Ugly work-around, hack at '~/.local/share/vinagre/vinagre-bookmarks.xml'
with your favorite editor, but it's XML and all 1 line so it's extremely
ugly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug looks like a dup of Bug #916295.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002267
Title:
[tuxcmd] failed to start, AccessViolation at startup
To manage notifications about this bug go
I can confirm this in 12.04 also. The "export LIBOVERLAY_SCROLLBAR=0"
hack worked for me. And see also Bug #1002267.
You'd think you could do something like "Exec=LIBOVERLAY_SCROLLBAR=0
tuxcmd" but that won't work for me. There's probably way to wrap it in
a tiny shell script... Yup, that wor
I had 4 machines affected by this problem, 3x on Ubuntu 10.04 and 1 on
12.04, all with FF 13.0.1. It also seemed like Thunderbird was a
problem, though not as bad as FF. Reboots "fixed" them all, but that's
very disappointing. Ubuntu/ntp/GNU/Linux should handle time and leap-
seconds more gracef
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964044
Title:
Ubuntu 11.11 to 12.04 upgrade leaves blank or empty desktop on first
reboot
To manage notifications about this bug go to:
https://bugs.l
Public bug reported:
I did an 'update-manager -d' upgrade of a pretty stock Ubuntu 11.11 to
12.04. It asked 2-3 questions about overwriting changed config files,
which I allowed, otherwise the upgrade was very smooth. But when I
rebooted and logged in, the desktop is empty. The display is worki
Thanks assassini! I did think of that, but how to do it wasn't obvious
& I got distracted and never really followed up. 2d worked for me two,
and now that we talk about it, I vaugly recall having to go out of my
way to specially install and use 2d on the previous release, so I should
have seen th
unity --reset and logging back in seems to have fixed it for me as well,
though the process did "scary" things to the desktop and on the terminal
where I ran it which adds a bit more newbie unfriendlyness to the whole
issue.
Having said that, I don't think 3d ever worked on this machine before
and
Public bug reported:
Description:Ubuntu precise (development branch)
Release:12.04
Package: fcheck-2.7.59-17
I upgraded a pretty stock Ubuntu 11.11 to 12.04, and now I'm getting
cron emails complaining:
Use of assignment to $[ is deprecated at /usr/sbin/fcheck line 1366.
This is du
Public bug reported:
Description:Ubuntu precise (development branch)
Release:12.04
openssh-server-1:5.9p1-4ubuntu1
Not really sure that OpenSSH is the real culprit, but it's what has been
reporting the log spam since I upgraded from 10.10 to 12.04 a day or two
ago:
$ sudo grep 'Conn
Public bug reported:
Binary package hint: unity-2d
Testing Natty in VMware, host has old graphics and can't run "unity" so
running unity-2d. But I wanted the launcher on-screen all the time so I
set '/desktop/unity-2d/launcher/hide_mode= 0' That worked, but full-
screen apps still assume that i
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/737359
Title:
unity-2d in hide_mode 0 covers left side of full-screen windows
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
Yup, that works, thanks.
OTOH, I think the fact that I had to discover all of this via Google
(i.e., the initial '/desktop/unity-2d/launcher/hide_mode= 0') and this
bug report to be a bug itself. "/desktop/unity-2d/launcher/use_strut
true" could mean anything, is non-intuitive and not-discoverabl
"Whenever the autohide settings will be made available to end users, a
GUI will be introduced." There it is, that's what I was hoping for...
Perfect.
As far as using Unity-2d, I was forced due to an old graphics card, but
I *like* it. The first thing I do on my other systems is turn off
Compiz;
UPDATE: I added the work-around in comment 3, and it seemed to have no
effect. Then I had to reboot for other reasons, and since that reboot
I've had the messages only once, as follows, which is a great
improvement.
I did *not* mess with /sbin/hdparm as I mentioned I might in comment 25.
Jun 23
@Jarige, I thought the work-around I applied from comment 3 *was* the
"disabling udisks-probe-ata-smart in /lib/udev/rules.d/80-udisks.rules"
one in comment 7. I didn't read the file-names carefully enough.
Having said that, '/lib/udev/rules.d/80-udisks.rules' says right at the
top "# Do not edit
Dell Mini9 running clean Lucid install. Fully up-to-date but no work-
arounds attempted. Upgraded RAM and 16G SSD I see messages like this
several times a day:
Jun 17 10:37:02 mini9 kernel: [541557.000145] ata1: lost interrupt (Status 0x58)
Jun 17 10:37:02 mini9 kernel: [541557.004104] ata1: dra
I should have noted in my comment 18 that I noticed this issue via
logcheck, and that I was previously running Ubuntu 9.04 LPIA, with
logcheck and did NOT see this problem. I made 2 attempts to upgrade to
9.10 and both failed utterly, presumably due to the terrible LPIA ports.
So as noted this is
@Jarige in comment 21, what work-around, the one in comment 3?
@Tommy Trussell in comment 20, interesting point. I will "grep '^... ..
..:3[567]:' /var/log/*" and take a good look at the results, when I have
some time to spare.
--
udisks-probe-ata-smart causes HSM violations
https://bugs.launch
I tried the one in #3 and it does not seem to have worked either, though
I didn't restart anything or reboot so I'm not 100% sure it took effect.
Different idea: I'm hazy on just what hdparm is needed for. What if I
just rename it, and create a symlink to true in its place. Will that
cause any B
Ran into this bug on a clean install of Lucid i386 on a Mini9, while
attempting to present at a LUG. Not good. We had literally a room full
of Linux experts and it took us 20 mins to figure out what it was doing
and work around it. (Not online so I didn't find this bug until hours
later.)
We fo
It doesn't work in 10.04 either. :-( I get one initial screen paint,
and then nothing updates no matter what I do.
I am running a clean and up-to-date install of Lucid 64-bit on a Dell
Latitude D630 laptop, using the "NVIDIA accelerated graphics driver
(version current) [Recommended]" restricted
Drat, I meant to add this too:
Search keywords: linux mint switch user wrong resolution
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757202
Title:
xubuntu / bionic / nvidia-driver-390 can only be
I just had this problem on a Mint-19.3 XFCE upgraded from 18.3. For me,
the fix was:
* `sudo nvidia-xconfig`
* `sudo vi /etc/X11/xorg.conf`
The 'Section "Files"..EndSection' block already existed but was empty. I added
this:
Section "Files"
ModulePath "/usr/lib/nvidia-340/xo
101 - 129 of 129 matches
Mail list logo
