Nice one - i'll test it out now :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263317
Title:
Not working on GTK 3 windows
To manage notifications about this bug go to:
patching file Ambiance/gtk-3.0/apps/unity.css
Hunk #1 FAILED at 6.
Hunk #2 FAILED at 19.
2 out of 2 hunks FAILED -- saving rejects to file
Ambiance/gtk-3.0/apps/unity.css.rej
patching file Ambiance/gtk-3.0/gtk-main.css
Hunk #1 succeeded at 34 (offset -1 lines).
patching file
The package I have installed is:
light gtk3-theme 13.10-0.3.20131014bzr324.fc20
What's the repo again so I can just check out the version in there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok I updated to the latest revision, and applied the patch, which
applied successfully, but there are still major problems with it. It
doesn't apply smoothly so the title bars display some striped bar, and
the window title is smaller than the window borders.
I also tried the script ambiance to
Here's a screenshot:
http://i.imgur.com/HNStrnF.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263317
Title:
Not working on GTK 3 windows
To manage notifications about this bug go to:
Public bug reported:
This affects Gnome-Shell 3.8 up to the latest build from Gnome3-Staging
Gnome-Shell 3.10 on Ubuntu 13.10 and Ubuntu Gnome 13.10 daily builds, as
of today!
1. Start gnome-terminal (has to be gnome-terminal - other term apps don't
appear to produce this bug).
2. run sudo su
the problem is that /run/user/1000/dconf/user owner is being changed to
root.
Setting the owner back to the user and restarting gnome gets the system
back up and running without rebooting
** Package changed: gnome-shell (Ubuntu) = dconf (Ubuntu)
--
You received this bug notification because
Public bug reported:
Description:Ubuntu 12.04 LTS
Release:12.04
The following errors on applying latest updates to Precise:
Processing triggers for man-db ...
Processing triggers for bamfdaemon ...
Rebuilding /usr/share/applications/bamf.index...
Processing triggers for
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1030760
Title:
package mono-gac 2.10.8.1-1ubuntu2.2 failed to install/upgrade:
subprocess installed post-installation script returned error exit
*** This bug is a duplicate of bug 1030760 ***
https://bugs.launchpad.net/bugs/1030760
Public bug reported:
Description: Ubuntu 12.04 LTS
Release: 12.04
The following errors on applying latest updates to Precise:
Processing triggers for man-db ...
Processing triggers for bamfdaemon ...
*** This bug is a duplicate of bug 1030760 ***
https://bugs.launchpad.net/bugs/1030760
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1030762
Title:
package initscripts 2.88dsf-13.10ubuntu11.1
*** This bug is a duplicate of bug 1030760 ***
https://bugs.launchpad.net/bugs/1030760
Please delete this duplicate - it was due to missing ondemand from
/etc/init.d I have since moved that back in and is no longer giving an
error
Thanks
** Also affects: mono
Importance: Undecided
This is also an issue for me in Precise 12.04.
The panel time is up to 1 second behind the system time. I have
confirmed the system time is within .316 of a second by comparing
with my stratum 2 ntp router.
The panel time however is slower up to about one second or less when
compared with
Public bug reported:
Hi I am running a clean install of Precise 12.04
When shutting down I get a delay of anywhere between 3 to 5 seconds at
Requesting remaining processes to terminate [OK]
Then a quick succession of:
Killing all remaining processes [fail]
and the rest of the shutdown
If anyone can let me know how I can debug shutdown messages it would certainly
help me provide more information.
Uninstalling network-manager is not an option as it creates an
excessivly long bootup process and it doesn't leave me confident with
the time for shutdown with it removed.
Even if I
This looks like an xrandr issue.
Output from xrandr shows that the highest and default resolution it
detects is 1920x1080 @ 50hz. But my native resolution for my monitor is
1920x1080 @ 60hz, so it makes sense why it keeps resetting to what
xrandr lists as the default, but it's a pain having to
This appears to be fixed with NVidia 302.07 beta drivers
** Changed in: nvidia-settings (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/634648
Title:
Same issue with me
Xorg.0.log shows:
[ 3455.129] (II) NVIDIA(0): Assigned Display Device: DFP-1
[ 3455.129] (II) NVIDIA(0): Validated modes:
[ 3455.129] (II) NVIDIA(0): 1920x1080_60
[ 3455.129] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 3455.168] (--) NVIDIA(0):
Public bug reported:
Firstly I would have thought the device would be automatically mounted
like it does in windows... but it doesn't so on following the
advice\suggestions from here:
http://411technology.wordpress.com/2011/05/14/howto-setup-the-galaxy-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936165
Title:
Seg fault when connecting Android 4 MTP file system on Samsung Galaxy
Tab 10.1
To manage notifications about this bug go to:
I have the same problem - removing the multiarch file then breaks
aptitude and requires to remove the 2 packages mentioned above.
I didn't do that because of the Joachim Durchholz's problems
reinstalling and getting flash working again. But it is annoying having
2 packages listed and it is also
Public bug reported:
Binary package hint: hal
Description:Ubuntu jaunty (development branch)
Release:9.04
There are four parts to this bug, part 1 is against HAL, part 2 is a
kernel bug and Parts 3 4 are Gnome Config Key mapping/layout issues:
1. FN + F4, F6, F7 symbolic names are
** Attachment added: lshal input, lshal hardware, dmesg, lsinput, xkbcomp,
setxkbmap
http://launchpadlibrarian.net/25245761/logs.tar.gz
--
Logitech DiNovo Notebook Keyboard - Keymap not correct and some keys not
detected
https://bugs.launchpad.net/bugs/359569
You received this bug
Public bug reported:
Binary package hint: hal
There are four parts to this bug, part 1 is against HAL, part 2 is a
kernel bug and Parts 3 4 are Gnome Config Key mapping/layout issues:
1. FN + F4, F6, F7 symbolic names are mapped in input.h to above 255
they are:
FN + F4 0x1ae KEY_MESSENGER
** Attachment added: lshal input, lshal hardware, dmesg, lsinput, xkbcomp,
setxkbmap
http://launchpadlibrarian.net/25245731/logs.tar.gz
--
Logitech DiNovo Notebook Keyboard - Keymap not correct and some keys not
detected
https://bugs.launchpad.net/bugs/359566
You received this bug
*** This bug is a duplicate of bug 359569 ***
https://bugs.launchpad.net/bugs/359569
** This bug has been marked a duplicate of bug 359569
Logitech DiNovo Notebook Keyboard - Keymap not correct and some keys not
detected
--
Logitech DiNovo Notebook Keyboard - Keymap not correct and some
Hi Lost,
ummm how did you sort this one out? I've just sent through a bug for
keyboard mappings perhaps you can have a look through that and see if
you are having the same woes as I am with keyboard mappings and hotkeys
not working. Numlock is mentioned in there as well.
Bug #359569
I ended up
Public bug reported:
Binary package hint: hal-info
Hi there,
My MX revolution thumb wheel is not getting any Symbolic names assigned
to it as below when running input-events:
Wheel forward
19:15:52.893909: EV_SYN code=0 value=0
19:15:55.104970: EV_MSC code=4 value=589833
19:15:55.104975:
** Attachment added: logs.tar.gz
http://launchpadlibrarian.net/25249137/logs.tar.gz
--
MX Revolution Thumb wheel not working
https://bugs.launchpad.net/bugs/359615
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Ubunto Jaunty 9.04 is my release
--
MX Revolution Thumb wheel not working
https://bugs.launchpad.net/bugs/359615
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Same error here - rebooting to see if that sorts it out as I just
installed it - but not looking hopeful at this point considering all the
people with the same problem above
--
Firefox flash problems (npviewer.bin crashed with SIGSEGV [with attached
backtrace])
31 matches
Mail list logo
