Removing libimobiledevice1 kills gdm

Bug #700195 reported by Brad Johnson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux Mint
Triaged
Undecided
Unassigned

Bug Description

1)
$ mintwelcome
/usr/lib/linuxmint/mintWelcome/mintWelcome.py:166: GtkWarning: gtk_container_add: assertion `GTK_IS_CONTAINER (container)' failed
  gtk.main()

Something must be wrong there. Maybe that's another victim to this weird bug. I'm using Linux Mint Debian Edition. I think version 10. Here's my uname -a if you want that:
$ uname -a
Linux rockstar 2.6.32-5-amd64 #1 SMP Fri Dec 10 15:35:08 UTC 2010 x86_64 GNU/Linux

2-3)

Trying to solve a problem I asked in this thread,
http://www.linuxquestions.org/questions/showthread.php?p=4216905 ,
I tried removing libimobiledevice1 and the desktop disappeared. In tty1 I checked whether libimobiledevice1 was installed AND IT WAS! After trying to remove it again several times using apt-get remove, it still seemed to be installed. I used the startx command to bring back the desktop, which brought up GNOME (my panel icons were rearranged though, which seems to be a common bug in GNOME that keeps happening to me) so it was just gdm that was removed. After apt-get installing gdm, a weird blue login screen came up (the default gdm theme, I assume).

I think the bug here is, libimobiledevice1 != gdm but something seems to think otherwise. Could this be a problem in the Debian repository?

4) I expected iPod/iPhone support to be removed so I could install a later version of the library I removed.

5) My friend had the problem first so I removed libimobiledevice1 like he did to see if I could solve the problem. He's using 32-bit, I'm using 64-bit. So it's a problem with both architectures.

Ikey Doherty (ikey)
Changed in linuxmint:
status: New → Triaged
Revision history for this message
Max (archerseven+mlp) wrote :

This issue is upstream, the dependencies in the Debian repository cause it to remove gnome-core and gdm3 upon the removal of libimobiledevice1.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.